| Trees | Indices | Help |
|
|---|
|
|
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from |
|||
|
|||
| unicode |
name = u''Name of plugin. |
||
| unicode |
short_name = u''Short name of plugin. |
||
| unicode |
version = u''Version of plugin. |
||
| unicode |
description = u''Plugin description. |
||
| [] of unicode |
authors = []Plugin authors. |
||
| unicode |
homepage = u''URL to plug-in's homepage. |
||
gui_extension_points = {}Extension points that plugin wants to connect with and handlers to be used. |
|||
| {} of 2-element tuples |
config_default_values = {}Default values for keys that should be stored in plug-in config. |
||
| {} with 2-element tuples |
events_handlers = {}Dictionary with events handlers. |
||
| [] of nec.NetworkIncomingEvent or nec.NetworkOutgoingEvent |
events = []New network event classes to be registered in Network Events Controller. |
||
|
|||
| plugins.plugin.GajimPluginConfig |
config Plug-in configuration dictionary. |
||
|
|||
|
Inherited from |
|||
|
|||
|
|
|
|
|
|
|
|
|
|
|||
nameName of plugin. Will be shown in plugins management GUI.
|
short_nameShort name of plugin. Used for quick indentification of plugin.
To Do: decide whether we really need this one, because class name (with module name) can act as such short name
|
versionVersion of plugin.
To Do: 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?
|
descriptionPlugin description.
To Do: should be allow rich text here (like HTML or reStructuredText)?
|
authorsPlugin authors.
To Do: should we decide on any particular format of author strings? Especially: should we force format of giving author's e-mail?
|
homepageURL to plug-in's homepage. using 'property')
To Do: should we check whether provided string is valid URI? (Maybe
|
gui_extension_pointsExtension points that plugin wants to connect with and handlers to be used. Keys of this string should be strings with name of GUI extension point to handles. Values should be 2-element tuples with references to handling functions. First function will be used to connect plugin with extpoint, the second one to successfuly disconnect from it. Connecting takes places when plugin is activated and extpoint already exists, or when plugin is already activated but extpoint is being created (eg. chat window opens). Disconnecting takes place when plugin is deactivated and extpoint exists or when extpoint is destroyed and plugin is activate (eg. chat window closed).
|
config_default_valuesDefault values for keys that should be stored in plug-in config. This dict is used when when someone calls for config option but it has not been set yet. Values are tuples: (default_value, option_description). The first one can be anything (this is the advantage of using shelve/pickle instead of custom-made config I/O handling); the second one should be unicode (gettext can be used if need and/or translation is planned).
|
events_handlersDictionary with events handlers. Keys are event names. Values should be 2-element tuples with handler
priority as first element and reference to handler function as second
element. Priority is integer. See
|
eventsNew network event classes to be registered in Network Events Controller. subclasses.
|
|
|||
configPlug-in configuration dictionary. Automatically saved and loaded and plug-in (un)load. |
| Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Thu Aug 12 02:07:14 2010 | http://epydoc.sourceforge.net |