Quote:
But its not a full automation. Plugins still require manual interaction due to two reasons:
a) The are not build for that (being fed from another source than the user)
b) there is no communication from sigil to the plugin
I'm dreaming of a list of key/value pairs an automated list can send to a plugin. And of course the plugin needs to able to recognize this and than is interpreting the key value pairs instead of displaying a gui.
|
Sigil was not designed to be fully "automated" and never will be. Specific tasks were designed to be done by users or via plugins. That said ... there is communication both ways from Sigil to plugins in the form of environmental info, paths, settings, language, etc and of course what files are selected in BookBrowser and from plugins back to Sigil in the form of a result XML file that tells Sigil exactly what to files to update and how.
There is no requirement for a plugin to use a gui and a plugin does support its own preferences to "remember" things. The plugin console and the plugin iself can autostart and auto close as determined by the plugin xml file.
And since plugins are open source, you can easily adapt or change any existing plugin to remove its GUI and hard code its functionality or change it to be based on a settings file you write or control.
Exactly what would your list of key value pairs entail and how specifically (with examples) would this be helpful given the above?