GNOME Bugzilla – Bug 459522
Plugins should be configurable
Last modified: 2007-07-26 15:18:33 UTC
Up until Evo 2.11.5, the settings/preferences for each plugin has to sit somewhere in the general plugin preferences page. This clutters the UI, is less intuitive etc. One should be able to configure the plugin within the plugin manager.
Created attachment 92201 [details] [review] Fix Patch to Evo that brings in support to configure plugins individually within the plugin-manager. Any plugin that wants to have its own configure option can do so by implementing e_plugin_lib_configure. The way in which the plugin's preferences are stored are up to the plugin (as of now). I don't want to restrict it atm. Confused as if it will be good to have a standard style. The plugin-writing-doc needs to be updated. I will be committing the patch once I do some testing and cleanup.
Sankar, this fine. You break abi, but in evolution. So not a problem. But remove debug statements and make them with d(x). And avoid hard coding '1' for response. Also remove your style of warnings on the console and make them meaningful. If you feel, you can do it for a few plugins directly and commit it with the patch.
It was just a temporary patch as jony wanted to try. Before committing I will remove all hard-coded values and debug statements.
Anybody who wants to write a plugin with configure support just have to implement e_plugin_lib_configure function.
Created attachment 92466 [details] [review] Fix
Patch committed : http://svn.gnome.org/viewcvs/evolution?view=revision&revision=33847 A Sample plugin implementation: http://svn.gnome.org/viewcvs/evolution?view=revision&revision=33854