View Single Post
Old 06-11-2013, 02:25 AM   #122
guma
Connoisseur
guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.
 
Posts: 93
Karma: 473808
Join Date: Jul 2012
Device: kobo touch
It seems to me that the discussion here confuses two issues: (a) The ability to exclusively access content via a (real) file browser system (i.e. without reading it into a database structure first) vs. (b) the possibility to offer the user a browser-like GUI experience (after having imported everything into a database).

(a) Would get rid of the time it takes the device to build/refresh the data base after adding or changing content. (b) Would just offer a the user an alternative GUI paradigm.

While I can understand that KOBO would never consider (a), since this would basically require a complete firmware re-write from scratch, I can't see any technical reason not to implement (b). At least from a programming point of view this should be trivial.

P.S.
There is no good reason that it takes that long for the device to build/update this rather small and not overly complex sqlite data base in the first place. This lack of speed is just the result of bad/sloppy programming.
guma is offline   Reply With Quote