Quote:
Originally Posted by Binchen
TagMechanic is my most used plugin. But mostly I use it to do the same things over and over again. Would it be possible to save the settings for each task? So something like Saved Searches?
And as the icing on the cake could then save in the new Automated Lists, that not only the Pluigin TagMechanic is to be called, but also immediately which saved setting I want to execute?
And yes, unfortunately, this also brings with it the vexed question of which files to run TagMechanic on.
You can still dream, can't you?
|
I can look into a "Saved Searches" features, but as for using them in an automation list: I know of no current way to pass custom parameters from Sigil's interface to a plugin. Thus "pre-selecting" the saved search would always be a gui choice AFTER the plugin has already launched.
Sigil's plugin framework only accepts a very specific (and finite) set of parameters that plugins can then utilize. Unless that changes, I don't really foresee any (easy) way to run the TagMechanic plugin without utilizing the gui to select the run parameters (regardless of whether that's individually or in the aggregate).
The files TagMechanic runs on will continue to be determined solely by which xhtml files are selected in the Book Browser.
@KevinH: if you see this, what do you think about passing an optional parameter to the plugin launcher system that is populated from the parameter field of the automation lists? If feasible, it might be an "easy" way for plugin devs to alter the behavior of their plugins when they're bein run as part of an automation list.