To Do List

To Do in integration.test_xmpp_client_nb.TestNonBlockingClient.client_auth to check and be more specific about when it returns (bind, session..)

To Do in plugins.plugin.GajimPlugin.authors should we decide on any particular format of author strings? Especially: should we force format of giving author's e-mail?

To Do in plugins.plugin.GajimPlugin.description should be allow rich text here (like HTML or reStructuredText)?

To Do in plugins.plugin.GajimPlugin.homepage should we check whether provided string is valid URI? (Maybe

To Do in plugins.plugin.GajimPlugin.short_name decide whether we really need this one, because class name (with module name) can act as such short name

To Do in plugins.plugin.GajimPlugin.version decide how to compare version between each other (which one is higher). Also rethink: do we really need to compare versions of plugins between each other? This would be only useful if we detect same plugin class but with different version and we want only the newest one to be active - is such policy good?

To Do in plugins.pluginmanager.PluginManager add more info about how GUI extension points work add list of available GUI extension points implement mechanism to dynamically load plugins where GUI extension points have been already called (i.e. when plugin is activated after GUI object creation). [DONE?] implement mechanism to dynamically deactive plugins (call plugin's deactivation handler) [DONE?] when plug-in is deactivated all GUI extension points are removed from PluginManager.gui_extension_points_handlers. But when object that invoked GUI extension point is abandoned by Gajim, eg. closed ChatControl object, the reference to called GUI extension points is still in PluginManager.gui_extension_points These should be removed, so that object can be destroyed by Python. Possible solution: add call to clean up method in classes 'destructors' (classes that register GUI extension points)

To Do in plugins.pluginmanager.PluginManager.add_plugin what about adding plug-ins that are already added? Module reload

To Do in plugins.pluginmanager.PluginManager.gui_extension_point GUI extension points must be documented well - names with parameters that will be passed to handlers (in plugins). Such documentation must be obeyed both in core and in plugins. This is a loosely coupled approach and is pretty natural in Python.

To Do in plugins.pluginmanager.PluginManager.remove_gui_extension_point instead of using argument to identify which extpoint should be removed, maybe add additional 'id' argument - this would work similar hash in Python objects. 'id' would be calculated based on arguments passed or on anything else (even could be constant) This would give core developers (that add new extpoints) more freedom, but is this necessary?

To Do in plugins.pluginmanager.PluginManager.scan_dir_for_plugins add scanning packages add scanning zipped modules