Rather than having all methods/modifiers as black-boxed functionality, instead, it might be worthwhile breaking out all methods/modifiers into individual script files that can be edited by anyone?
This would mean the scripts could be made available in this repo and pull requests could be accepted should anyone wish to make their changes publically available.
A question would be: how would they expose their user-editable settings? I really don't want the UX to become worse, and I especially don't want to regress back to the property grid-style settings editor in FileSieve 3.xx.
Rather than having all methods/modifiers as black-boxed functionality, instead, it might be worthwhile breaking out all methods/modifiers into individual script files that can be edited by anyone?
This would mean the scripts could be made available in this repo and pull requests could be accepted should anyone wish to make their changes publically available.
A question would be: how would they expose their user-editable settings? I really don't want the UX to become worse, and I especially don't want to regress back to the property grid-style settings editor in FileSieve 3.xx.