View Single Post
Old 06-05-2013, 11:58 AM   #69
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
Quote:
Originally Posted by PeterT View Post
Sigh.. when will people accept that ALL the Kobo supplied reading software on ANY Kobo eReader is tightly tied into the database and NOT into the file structure of the device.
Why should people (= customers) have to accept KOBO's decision on how to technically manage the firmware on their device? Why should customers even care about this?


P.S.
Using a database as a backend for the firmware does not prevent the implementation of library management functionality that - to the user - would appear to be file based. Mirroring file structures in a database is rather trivial from a programming point of view. Even KOBO's firmware programmers should be able to implement something like this ...
guma is offline   Reply With Quote