<<
>A wizard ProcessorModule class could be a way to implement this (as it can
> be read from the bridge, and allows customization through the admin
pages).
-1 for that . we now have the config/utils directory with the
corresponding xml reader. creating a "processor" module won't make thing easyer or nicer
INHO >>
Reasons for using ProcessorModule:
- you can then configure the wizards using the admin pages, which is pretty elegant (well, IMO). Utils cannot be administered
- module utils are automatically read in memory, and kept there. I'm not sure how this works for utility xmls
- ProcessorModules have means to get and set the configuration values through the bridge (the Module interface). The utility xmls do not.
- I feel the editwizards are more akin to a 'module' than a 'utility' (but that's just a feeling)
I think modules have a bit of a bad rep. I think they can be very useful for the configuration (and maintenance) of tools and plug-ins in MMBase.
Pierre
