Completely different beast. When I designed the Sigil plugin interface it had PluginRunner as a Modal dialog, thereby suspending further Sigil actions. Basically we suspend Sigil while the plugin runs. We also designed the result xml that is passed back from the plugin so that Sigil itself could make the actual changes and not the plugin (for safety). None of this required any redesign of how Sigil works.
This is also true for the automation lists. It was designed to work that way to prevent the need for a Sigil redesign and prevent the need to develop a scripting language.
Full automation is simply not our goal nor is developing our own scripting language to replace python. As DiapDealer said Sigil is not a command line tool and library for working with epubs. It requires decisions be made, inputs provided, etc.
And as DiapDealer said, this decision is not negotiable.
KevinH
Quote:
Originally Posted by Binchen
I can't accept that argument, because there was a period in the past when Sigil was never designed to run plugins. And now it can.
|