MobileRead Forums - View Single Post - Possible To-Do List for Future Sigil Releases Post Sigil 1.8

KevinH · 10-28-2021, 11:42 AM

We could create an automate list command to write a parameter to a pluginname.cfg type file stored inside an automate folder in the Sigil Preferences folder. It would of course be up to the plugin to look there for a cfg file and to remove it once done.

But wouldn't it be easier to duplicate the plugin under a new name and each would then get their own prefs file which could be set up for specific actions.

We could also add a in-automate boolean flag to Sigil's plugin sigil.cfg and then make its value available to plugins via new wrapper.py interface call. That would probably be the easiest as in-automate is a Window level var that can be grabbed from the PluginRunner.

Similarly we could create an automate-param variable at the Windows level that Plugin runner could also write to the sigil.cfg and create an plugin interface call in wrapper.py to get that value.

So all of these things are doable but I would love to know how these parameters (outside of in-automate) would be useful.

10-28-2021, 11:42 AM	#17
KevinH Sigil Developer Posts: 8,893 Karma: 6120478 Join Date: Nov 2009 Device: many	We could create an automate list command to write a parameter to a pluginname.cfg type file stored inside an automate folder in the Sigil Preferences folder. It would of course be up to the plugin to look there for a cfg file and to remove it once done. But wouldn't it be easier to duplicate the plugin under a new name and each would then get their own prefs file which could be set up for specific actions. We could also add a in-automate boolean flag to Sigil's plugin sigil.cfg and then make its value available to plugins via new wrapper.py interface call. That would probably be the easiest as in-automate is a Window level var that can be grabbed from the PluginRunner. Similarly we could create an automate-param variable at the Windows level that Plugin runner could also write to the sigil.cfg and create an plugin interface call in wrapper.py to get that value. So all of these things are doable but I would love to know how these parameters (outside of in-automate) would be useful.