Quote:
Originally Posted by davidfor
And while I said I am not interested in doing this, for a while I have had in my mind to do something to check reading status between calibre and the device. I've been thinking about this more since getting the Aura ONE and populating it (and yes, I'm one of those strange people who like to keep a lot of books on their devices). If I do that, extending it to compare some other attribute would be "a breeze".
Note: "a breeze" is used here as a programmers term to describe a small feature we think will be easy to add, but will probably end up taking more time than the rest of the project.
|
As someone who has been doing something similar "manually" for my sideloaded kepubs to return the reading status after the last firmware update, the OCD in me would appreciate it for when my Aura HD suffers a fatal accident and I have an excuse to replace it with an Aura One (although it seems the HD is not as fragile as people here complain eReaders are, it has survived some accidental falls)
Note: By manual I mean that some steps are manual, I don't know anything about python, but I'm good with databases, so working with a backup database and creating excel batches of updates I've been able to return that information to my two working Kobos.