> - Renamed PluginRegistry.startPlugin method as addPlugin. > Modified the behaviour > of this method to mostly adding the plugin to the registry. > (More comments to follow)
I'm not sure of the change of the name, and functionality here Ceki, could you describe what you mean here? I liked the 'startPlugin' name because it gave the connotation that the method would initialise the Plugin (by calling activateOptions), but now the method really does just add, and does not activate the options. Has the contract changed such that clients that want to add a Plugin to the registry must activate the options first? Along those lines, it might be nice to add an "isActivated" read only property, which is set by the Plugin on activateOptions call. What do you think? cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
