|
Thanks — that is very helpful. A small per-publication storage facility is exactly the scope I had in mind, rather than access to calibre’s general preferences.
For this use case, the minimum semantics would be:
namespace bound by the reader to the current publication;
small key/value storage;
survives a normal viewer restart;
isolated from other publications;
clear/delete operation;
read/write failure detectable by the EPUB script.
I would not need filesystem access or access to calibre’s general settings.
Would you prefer such a facility to be exposed to scripted EPUB content as a dedicated API — something conceptually like bookStorage.get/set/remove — or should it be built on an existing calibre/Qt abstraction?
If a dedicated API is the appropriate direction, I can prepare a minimal proposed interface and corresponding tests based on the reproducer attached above.
|