Quote:
Originally Posted by KevinH
Just have the plugin always return -1 to indicate an error so that you get the full debug output.
You could write an equivalent to plugin runner to unzip an epub, parse its opf and set up the plugin environment and run the wrapper/launcher.
But as I said, just return -1 so any debug output is copied to Sigil's Plugin Runner console.
|
It turns out it is easy to adapt the Sigil python plugin launcher to run standalone. There is probably a better way, but what I did was put the plugin launcher files and all my plugin files into a directory, added a copy of Sigil.cfg, created a directory and unzipped an eBook into it, commented out the redirection of sys.stdout and sys.stderr, and created an argv string to point to the right places, and it works!
I much prefer not going through a build cycle to find a syntax error, or stepping through my code rather than putting in print statements to find a logic error.