Quote:
Originally Posted by zoran
Of course. Few more functions should be written to handle the thing.
More I read, less I want to go further. If you ask why, the answer would
be: no need for db of that kind. Simply follow directory tree, pick the
book, load the book, read the book. Bookmark could be tricky, but it
is not unsolvable.
|
One of the reasons for the existence of the database is to save parsing / loading time. Extracting metadata from a filesystem entry becomes a lengthy process, especially when you have to repeat it a few thousand times. Another issue is the table of contents. It becomes painful to extract and parse a compressed file (toc.ncx) every time you need it, and storing an uncompressed copy would seem redundant when you can store the information you need in a database.
Why implement a database as a filesystem when you can implement it as a database?
These are of course all assumptions based on what little I know about the design of the system.
Quote:
Originally Posted by zoran
Yep. The only place where function like that should live on. From time
to time I ask myself why things become complicated without any
reason. People need "go-to-page" more than cover on power down.
|
Indeed. As I'm not a Kobo developer, however, there's little more I can do than wait until the next release.