Just thinking ahead...
Multiple instantiations of a single plugin seem to be very confusing for
people. Most of the time it'll be by accident, such as when when
sticking an 'addPlugin' into config.php when the plugin's already in the
defaults array.
Things like OpenID will double up links, tabs, and explanatory text when
loaded twice; others might process things twice or otherwise act very...
unexpectedly.
Unfortunately we currently use multiple instantiations for things like
the URL shorteners, where LilUrlPlugin needs to be set up several times
in a row to support multiple services.
My strong inclination is to ban multi-instantiated plugins, in favor of
letting those plugins which can actually benefit from multiple sets of
configuration options o deal with them themselves. A smarter plugin can
easily take multiple items in its config array, or present a config
interface via the administrator panels, saving its settings to the database.
Having a plugin either be *on* or *off* for a given site will greatly
simplify plugin management, especially as we move from 'addPlugins in
config.php' to 'addPlugins plus what's in $config["plugins"]["default"]'
to 'any of those things, plus what's been configured through the admin
interface'...
Any objections or thoughts for improvement?
-- brion vibber (brion @ status.net)
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
