Quote:
Originally Posted by guma
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.
|
Exactly, on all points.
Although the parts of the firmware that would need addressing for (a) are the same parts/modules that they need to do extensive work on to get their database working properly.
Another issue might be how they are doing maintenance on the database. It appears that they do try and deal with the database all in one go. When they could just do a minimal catalog data acquisition on the file structure, at the start, and there after build data on a file as it is accessed. (Not that they should need that much from the files.)
Luck;
Ken