Wow
.
I'm trying to warp my mind around your wrapper... It will take some time.
Just a few first thoughts.
1. I differentiate between
menu bar script and
context menu script and am somehow fond of it. Context script operates "only" on selected items. Either tell me why not or edit_launcher should be able to take selected items as arguments.
2. I have assumed that all script input data will be referenced to/copied from Sigil temporary work folder. When you know Sigil(!) epub root directory, you know the path to opf (./OEBPS/content.opf). Do we need to pass the path to it nevertheless?
3. Doing tests with test_target I got Manifest ID error: I think it's because Sigil doesn't write
mimetype file in its tmp book folder - which I used for test at first. I think we don't really want to make epub from Sigil temporary files and then unpack it somewhere else?
Just to clarify:
"input" means Sigil will be reading in epub produced by script,
"output" means script will transform data from Sigil and write it somewhere outside Sigils jurisdiction.
"edit" means script will change Sigil data and Sigil will have to accommodate it.
"meta" is actually "edit" but only for metadata.
is this correct? Why do we need "meta"?
Quote:
|
Since this is an external python interpreter, we don't know if they will have external python packages like lxml, Qt, html5lib, etc, so we are limited in what we can do.
|
The script should be able to use all generally available libraries or provide its own libraries. I would be unscrupulously self-indulgent here
. Some information about it will be due, i guess.
thx