Quote:
Originally Posted by nairbv
I wonder how re-usable the code in libprs500 is.... even for someone does want to make a custom exactly-what-they-want ebook app, ... if libprs is written in a way that it has a bunch of reusable libraries, it's still a big argument for working on python book management code. I mean, he's already got convert-damn-near-anything-to-lrf built right? Even if you don't care about lrf in particular, that at least means that he has a way of extracting data from damn near every file type, which is a big piece to be able to borrow, even if writing a new program.
Of course I'm assuming all this software is licensed in ways that the code reusable too...
|
I come from the Unix world, which means libprs500 is architected in little pieces each with its own command line interface which means that each piece of functionality is reusabe not just in python programs but in any software. THe only exception to that being the database access, and that's only because I haven't had the time to write the actual command line tool, the underlying library design is completely modular.
In fact adding complete support for converting any new ebook format to libprs500 requires the writing of only two converters format->html and html->format as well as a metadata reading/writing tool. All the other features of libprs500 will work automatically with these three converters in place.