Not that anyone is paying that close attention, but if you have you'd note that I'm managing a LOT of plugins. They're growing like fungus around here. Now, I'm not trying to offload them but my time lately has been very tight and testing has been a pain since my typical build installation includes all of them, such that I'm never sure of interactions. Lately I've been getting ping'd on a number of different plugin packages that have been bundled in the large CeryleWiki plugins jar file. I should probably break that thing into much smaller jars. Time willing...
It occurs to me to create a very simple "Controllable" API and add a minor callout in the PluginManager to disable the function of a plugin based on it occurring in an excluded list, or enable it based on an included list (either? both?). A disabled plugin would either be entirely ignored by the parser/PluginManager, return an empty string, or some kind of error message (this might be defined by the API). I'm thinking of writing some kind of UI or JSP to permit an administrator to individually set a flag for each plugin. Any thoughts on this? Bad idea? Good idea? Not an interesting idea? When might this might make sense, JSPWiki-version-wise? Thanks, Murray ........................................................................... Murray Altheim <murray07 at altheim.com> === = = http://www.altheim.com/murray/ = = === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = = Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record
