|
As best as can be determined, Reading Ttracker version 1.1.1 works as is, hardcoded, within the parameters it establishes.
For the rest of us with the vast array of Calibre setups, tracking preferences, etc, I have a road map in the works for this overhaul.
Hardcoding appears to be the core reason for inflexibility so the next plugin iteration will attempt some major changes:
Global hardcode
Decoupling hardcode and moving to an event-based model which should eliminate reliance on most if not all custom columns creation, unwanted persistence behaviour, and book selection inflexibility. Theoretically this should seamlessly support tracking of rereads, reading multiple formats of the same books, and similar reading events.
Translations
Establishing parameters needed for expanded translation support such as flexible layout, proper date parsing, etc.
Book inclusion
api.search('#tracked:true') becomes:
Manual → tracker_data["books"].keys()
Search → api.search(search_expression)
All → api.all_book_ids()
Eliminates the need for a custom column to track books, but still uses fast database access protocols.
Dashboard
The intent has always been to show analytics and reading wrap-ups. (Think Storygraph, Hardcover app, etc), charts, graphs, and so on. Ideally the dashboard should be fully modular and user-configurable. This would allow a user to track by words if they preferred instead of pages, ¼ star ratings, etc.
Export
Expanding the current formats (previous plans included use of templates) and multi-year compilations. Improving CSV exports.
Supporting readers who like and want detailed tracking is the goal, keeping flexibility at the forefront.
As I mentioned in the intro, I am not a coder/developer. I have three days left to work on this. Thanks for all the input, suggestions, explanations and requests. Any additions that would further this project is welcomed. Meanwhile, I will do my best.
|