Quote:
Originally Posted by Rellwood
Hi,
I noticed that a few updates ago the plugin required the newest version of Calibre, however I still run a Windows 7 machine and apparently they stopped supporting Windows 7. I plan on keeping Windows 7, but if I end up having to stay with an older version of Calibre, will your plugin be available?
|
I don't really understand the "I plan on keeping Windows 7, but if I end up having to stay with an older version of Calibre".
I upgraded to Windows 10 as soon as it first came out, and was immediately rewarded with a noticeably snappier machine since Microsoft modularized its functions to optimize its active memory footprint viz a viz Windows 7.
If you are concerned with running old versions of Calibre with old versions of your plugins, "best practices" would say that you should periodically be backing up your "C:\Users\Rellowood\AppData\Roaming\calibre\plugin s" directory into a date-stamped directory name (to avoid overwriting) on an external drive so that you will have all of your old plugins (and their associated preferences .JSON files) in discrete locations for future use if you have to install old versions that are all guaranteed compatible with the version of Calibre in-use at the time of the back up. You might want to download the Calibre version in use at that same time, and move it to the same external drive.
Calibre, its plugins, and the plugins' .JSON files are matched sets that work properly together at any point in time.
I assume that you already know that you can install old versions of Calibre Portable directly onto your hard-drive in specifically named directories, and run each version independently of the others. Just make sure the \calibre\config\ directory is properly seeded for each. Keeping your plugin preferences .JSON files across Calibre versions synchronized could be an issue unless you standardize on a single "old version" to use consistently.
Just my personal opinion, but the above sounds like a lot of needless aggravation just to keep Windows 7.
To finally answer your original question, JS uses Calibre's own application-specific libraries for many purposes, so as Calibre changes, JS has to change with it or one or more of its 62 tools (or even all of JS) will fail and die. Hence, as Calibre changes, the minimum JS version likely will have to increase as well. If you do not upgrade Calibre, then you would be "stuck" on the JS version active at that time. Just be sure to keep a discretely-named backup of the "stuck on" JS .zip file since it could easily be overwritten by a newer file with the identical name. Hence, the advice given previously.
DaltonST