Quote:
Originally Posted by DiapDealer
Well that's something completely different than what Jon was referring to. What sort of plugin architecture is going to accommodate automatically updating only portions of a plugin's (any number of plugins, actually) code? Perhaps you're referring to the launcher code itself? Hell, even that wouldn't be that difficult to implement an update feature, or install package to update that code without a full Sigil release. It's early days yet--and the architecture is flexible. After functionality gets rolling, the bells and whistles can be added.
|
In my opinion, if the plugin uses independently developed piece of software, it should be written as a wrapper around this software - thus making a library of it. Than it is possible to update only library, only wrapper or both of them.
As the library alone wouldn't be a proper Sigil plugin, the architecture should be able to provide extra functionality for it - in this case somehow adding it, in Sigil-plugin context, to normal python libraries.
Quote:
|
If you're using v0.1.1beta, the differences in the filenames you're experiencing are probably dependent on whether or not the file is a mobi-only ebook or a KF8 ebook. I had worked on getting the Updated Title from the OPF metadata (the makeEpub method in quickepub.py) and returning a sanitized version of that for the epub name before I lost interest (and Sigil's codebase made the file name pointless). A KF8 book was returning a name based on the ebook's original file name (unpackEPUB in mobi_stuff.py).
|
Thanks.