Quote:
Originally Posted by varia
I'm no expert but that seems to make sense, storing a plugin database out of the calibre confic directory, just to be on the safe side.
This did cross my mind so it's good to see that validation.
|
Safe from what? Maybe Comfy.n can tell us.
Why should a sqlite file used by a calibre plugin be regarded as being any more precious than the sqlite files used by the Azardi epub viewer, the FDM download manager, the Firefox web browser, or the calibre server etc.
And, why would it be safer to store the sqlite file in let's say
c:/users/<userid>/someplugin-data directory rather than
c:/users/<userid>/appdata/roaming/calibre/plugins/someplugin-data/ directory. If the Backup Configuration Folder plugin is installed it'll get backed up when calibre is closed.
Quote:
Originally Posted by varia
Do you mean packaged in such a way so as to install the plugin with all user data/settings etc already in place? Like a personal single-file backup being installed to a new computer?
Or just for the zip and all data/settings to be located in a single folder?
|
The latter.
One roadblock to my ideal, is that some plugins (e.g. View Manager, Count Pages, Quality Check etc) have library specific settings that are stored in the preferences table of the library metadata.db files.
Another is that some plugin settings are stored in calibre wide json files, e.g. window sizes and positions in gui.json, I have entries in there for plugins that I removed 10+ years ago
BR