Quote:
Originally Posted by KevinH
Please provide some justification for this? Plugins must be shutdown when exiting Sigil otherwise their output is lost (by design) and if Sigil is crashing, that should not happen.
What potential use is this? How would this help the majority of Sigil users?
|
I'm not sure what you mean by, "Plugins must be shutdown when exiting Sigil otherwise their output is lost". In any case, I wrote a plugin that does a significant amount of work, some of which could be cached for use the next time the plugin is run, if it is run from the same Sigil session. I guess it would be useful to plugin authors and follow-on plugin users.
Suppose a plugin creates a parse tree the first time it is run. If it is cached then the same plugin can continue to modify it every time the plugin runs, until Sigil exits. Would need a session id to make this work.