[wold]

I thought you had a pretty nice base setup, and would want to expand it by (1) reading the sql databases to manage collections and backup (2) export data (esp annotations and highlights) from koreader, in an easy and practical way. Generally prefer to join projects for the consolidation of efforts + collab. Thought I could contribute some when my current work engagements end in a few months

Thanks. Both #1 and #2 would be welcome. If it is still some months off, I could further prep the code for open sourcing.

#1 (managing collections) gravitates towards book collection management, but while I don't see a use for duplicating such tools, it can be useful to edit a database directly. And not everyone wants to use collections managers either. (But above all, don't let me dictate what you can and can't do ).

Note there exists a webbased PB collection manager tool discussed here: https://www.mobileread.com/forums/sh...ection+manager
It does ship with a browser included. I might throw a message out if I/we can integrate parts of it into AVATeR.

---

Re #2 KOReader support, that can be done easily now. I could even do it if you ship example note files for koreader. IIRC there were some floating around here on MR.

Performance wise, AVATeR could be limited by the device storage speeds. But the local mirror might help there. Let me do some tests on that and get back with you.

The way it would work, is on first user selection of the KOReader database source, a function is called to load the annotations. That needs to iterate through the directories to find the individual ('sidecar') note files. Now v0.14 has a new directory iterator (net 20 lines or so, nothing fancy, but prevents there being 3+ iterators) that can apply a function to files with a specified extension. IIRC, KOReader (Lua?) uses JSON for these files. Qt can handle that.

Again, here too there exists a KOReader note reading app somewhere out there, released years back. Here too it might be worth it to contact the author for re-using parts. (It also offers a select-by-book annotations list, which I then kinda couldn't implement in good faith.)

>You're welcome to contribute. The source is C++/Qt though (just to be sure)

Not my primary but with your existing code and some searching it should be doable

Nice. While C++ is/can get complex, it also has come a long way, and you can indeed work from existing work (do at first avoid older WIN32 API code ).
Installing the compiler/buildchain may be the most cumbersome part, on Windows at least, and easiest on Linux. What platform do you use BTW?

It might also be doable to integrate, say, Python code. Only for Windows I suspect that will pull in a lot of additional libraries and cruft - might just disable it there (using a compilation ON/OFF flag). Might be worth a look. Let's keep in touch.