Quote:
Originally Posted by Robert22
I also noticed that you do not have to worry about thumbnails when creating a driver. What happens is that the Books.db is populated, along with a thumbnail being created by the Sony reader itself. This happens on the fly when viewing a book list by thumbnail on the reader for the first time. If you do not view the whole list, only the ones you view get generated and are available from then on whenever you view a book list.
|
Sony's readers have done this since supporting thumbnails. But, not all books have covers we like (especially DRM'd ones where we haven't stripped the DRM from). Calibre being able to copy over thumbnails that don't match the first page is a feature for some (including me), not a necessity.
My own investigations are really to see how close to parity to the 3/6/9xx driver it can be, before coding. And focus on the important stuff first. I'll probably be able to get started on something tonight.
Quote:
Originally Posted by Robert22
I'll try to find out how collections are created next and let you know if I discover anything useful.
|
You can save yourself a bit of time. Books.db has two tables of interest: collection and collections (descriptive, I know).
Collection has the list of actual collections in it. Names and so on. Collections is a series of reference Ids that link books from the 'book' table to collections in the 'collection' table.
The catch is that to make the link, the book has to be in the book table. So any driver needs to add the book to the book table, before it can add it to any collections. So the driver will have to be somewhat integrated with the database. This actually a good thing, as it will make the loading of books faster from unplugging, MUCH faster.