|
> The collections are virtual and defined using the database.
If the collections are defined in the database, then why does it take so long to open the list of collections? Don't they have the collection table indexed or something?
(~2500 books, maybe 150 collections)
And I don't see why they couldn't implement nested collections in a directory hierarchy structure, as long as you can still put one book in multiple collections. Calibre and sony both do it that way, just put a separator character in the collection name, and then collapse similar prefixes in the collection list.
Another alternative that would make me even happier than nested collections would be multiple collection searches -- search for books in all of two or more categories. And that would be trivial to implement -- just more items in the sqlite query. Heck, I'd even be happy if I was limited to exactly one or two categories, as long as it didn't take twice as long as now to build the list and it saved a home tile with the combo.
But, then, the collection list is already abysmally slow to come up, and they don't do hierarchical TOC's in pdf's or epubs anyway. (I blame half of that on adobe, of course. Amazing adobe can't follow their own standards.)
|