Quote:
Originally Posted by stanking
It IS a good point. The strange thing is that it could be used to argue either direction. If the lure of additional functionality encourages the current user base to upgrade to the current version, that would be good for future developers. Those stats you pointed out only list 25% of the installs, but if we extrapolate, that's 40% who are still using a pre-1.x version, which is sad.
Personally, I'll code for the current version, and if the code works for earlier versions, that's a bonus. And if it doesn't and users upgrade to get the plugins, that's a bonus too. If there were a significant percentage who COULDN'T upgrade, that would affect my thinking, but I suspect it's more a matter of the users not bothering than an inability.
When my code is ready, I'll test it for compatibility, but I'm not going to lose sleep over it if it doesn't run on Calibre 0.1.5.  |
1.48 (forty-eight) is the last Qt4 version. 1.5 (five) is a much earlier version.
You have to specifically code for Qt4. It doesn't just work with Qt4 when coded for Qt5. You have to put in the installs to handle if it's running under Qt4 vs Qt5. I don't know the specifics, but if you code for just the latest version, then your plugin will not work for 1.48.
The point is, if your plugin can run under Qt4 & Qt5 with just a little extra coding, do so and make it compatible to more people.