Thread: Nested Collections?
View Single Post
Old 06-30-2015, 01:19 AM   #14
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by compurandom View Post
> 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)
I'm with you on this, I'm surprised at how slow this is. But, without seeing the code, I can't guess why. Of course, the number of people with that number of books and collections is probably very small. My bet would be that most users have less than two screens worth of collections. And unless you use calibre putting the books into collections takes a lot of work.
Quote:
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.)
Of course they could do this. But, it is their decision whether to. And they will mainly do things that will benefit a lot of users (or make more money for Kobo). How many people do you think would actually use multiple levels of collections? Personally, I wouldn't and I suspect very few would. If that is Kobo's opinion, they will spend their development time in other areas. I can rattle of a list of things that I would want to see a long time before this.
davidfor is offline   Reply With Quote