Exporting "ebook-viewer.exe" read list

[kovidgoyal]

You dont need to do any thing. Just update and last read positions should be automatically used. Although given this particular update was a long time ago, I cant remember the details. If you are concerned make a backup of your calibre config directory before updating and if it doesnt work, downgrade and restore.

[BetterRed]

I refuse to believe the list is in viewer.json for version 2.85.1



and version 3.48



but it's not there for version 3.36.

EDIT: ↑ ↑ ↑ ✔ - gazumped by the boss.

BR

[LostHisMarbles]

Originally Posted by kovidgoyal

I cant remember the details

Could hardly blame you after all these years; will do as you advise.

And thank you very much! For Calibre most of all

[Comfy.n]

I've just checked this on a portable 3.36 install and:

Is there a way to find and export the list of read documents/books saved inside the ebook-viewer.exe file?
* i presume they're internally saved, if not, by all means enlighten me.

The opened files history is in viewer.json

I've got thousands of documents that it remembers, will open them to where i had them last.

I found that the history seems to be replicated with last read positions in this file: iterator.pickle

However what's puzzling is that I decided to delete both files to see what would happen and, AFTER deleting them and reopening the books, viewer still remembered the last read position!!!

Metadata.db has a last_read_positions table but it's empty.

Mystery goes unsolved.

[ownedbycats]

The table in metadata.db is used by the content server, I think.

[LostHisMarbles]

Originally Posted by Comfy.n

Mystery goes unsolved.

Much obliged, must have taken you some time

Regarding that elusive viewer.json, i know what happened and i couldn't find it. My bad on that one.
I mean if you've got two different people telling you it's there, even if you can't see it yourself.. it was hidden; don't ask me how or why, but, yeah, now we know.

The funny part is, i was about to come and post that weirdly it doesn't list the actual pages, ergo how can the viewer know exactly where i was, but you'd posted in the meantime. Will open the pickle and have a look myself (curiosity), though given your deleting experiment, i'd wager they're additionally saved internally as well?

Really doesn't matter though, if .pickle lists pages, i'm sure to find a way to import afterwards.
So, again, many, many thanks for your time (i mean who bothers with a file named pickle!) :P

[ownedbycats]

I remember Kovid mentioning that annotations are stored in a few separate ways in case of a failure in one. I wouldn't be surprised if the reading positions were the same. In any case, unless something goes wrong with the updating I think it would transfer to the new version.

[DNSB]

Originally Posted by LostHisMarbles

So, again, many, many thanks for your time (i mean who bothers with a file named pickle!) :P

Hmmm... considering Kobo's main UI is from a file called nickel but there are also files called pickel, sickel and strickel, someone must like those names.

[thiago.eec]

Originally Posted by Comfy.n

I've tried NP ++ json plugin and it looked promising at first, however for some reason it doesn't jump to the section clicked in the outline panel:

Attachment 212097

may be something conflicting in my settings

Originally Posted by ownedbycats

I never got that plugin to work right either, lol.

Try this one: JSON Tools
You can click any key in the Tree Viewer and it will jump to the key. It also has a complete set of tools for JSON.

[Comfy.n]

Originally Posted by LostHisMarbles

Much obliged, must have taken you some time

You're welcome

Originally Posted by thiago.eec

Try this one: JSON Tools
You can click any key in the Tree Viewer and it will jump to the key. It also has a complete set of tools for JSON.

Yay, this one is good, thanks! Thankfully it has an option to disable checking for updates on every NP++ start.