|
An ebook reading device is more than just a filesystem with book files in it. There's metadata as well.
I'm architecting the library so that device interaction is via a plugin. The plugin needs to only provide functions to get the list of books, delete a book and add a book. It takes care of metadata handling internally. If I were to migrate to a filesystem based way of doing it, there'd still be non-trivial code needed for updating the XML databases on the reader. Now that SONY has basically locked out the rest of the filesystem anyway, the justification, imho, for a filesystem view doesn't really exist.
You are correct in that a filesystem interface is the easiest to use for other developers, provided it contains metadata handling as well, however, a command line interface like prs500 is not that much harder.
On a side note, how do you manage your ebook collection?
EDIT: I have no programming language related hangups, though I do find python to be the most efficient (for the developer) language over long term use, so if you ever need help I'll be happy to contribute C code.
|