Thread: Normal for kobo to take forever on "processing content" ?
View Single Post
Old 06-18-2015, 07:48 PM   #89
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 chrisridd View Post
Well that's true. It is a trade off between generating it on demand, or when you open the book, or when you add the book to the reader - and it seems like Kobo's chosen the latter. Perhaps because it is so slow? ;-)
I think it's tradition. The way they handled books in the early readers was different to now. My understanding is they unpacked them all. Extracting the ToC while doing that wouldn't be much work. Plus, my memory has the ToC available from outside the book in at least one firmware version. As things have changed, this hasn't as there has been no real reason to, and as any good programmer knows, you do not touch working code.
Quote:
I wonder if we can figure out some tests to see what about the ToC extraction is so slow. Does nesting make a difference - as Kobo doesn't support multiple levels?
I think it's just size. My test the other day had flat ToCs. Most of my books have either one or two levels. There doesn't seem to be any difference with those two.
davidfor is offline   Reply With Quote