Home | Trees | Indices | Help |
---|
|
The PluginRegistry is responsible to find all the Plugins. Plugins enabled in the Application config file will be loaded by instantiating their class.
The registry can create components by first searching them by name in Plugins component registries and instantiating them directly. Component instances are not handled by the PluginRegistry.
|
|||
__metaclass__ |
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
elisa.core.plugin.Plugin |
|
||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
elisa.core.component.Component |
|
||
(elisa.core.component.Component, elisa.core.plugin.Plugin, tuple) |
|
||
|
|||
elisa.core.component.Component class |
|
||
|
|||
Inherited from Inherited from |
|
|||
|
|
|||
name =
|
|||
Inherited from |
|
|||
elisa.core.config.Config |
_app_config Application's config |
||
dict mapping Plugin names to Plugin classes |
_plugin_classes Plugin classes found by the Registry |
||
elisa.core.plugin.Plugin list |
_plugin_instances Plugins currently instantiated |
|
|||
plugin_classes | |||
plugins | |||
Inherited from |
|
|
|
|
|
|
plugin_class
depends on are loaded.
|
|
Use the PluginRegistry to to create a Component. component_path format should be like this:plugin_name:component_name[:instance_id] The plugin_name is the name of the plugin sub-class to load. See elisa.core.plugin.Plugin.name. The component_name is the name of the Component sub-class to load. See elisa.core.component.Component.name.
|
|
|
split the component path: plugin_name:component_name[:instance_id] add default instance_id (0) if missing @param component_path: information to locate the Component to load @type component_path: string @returns: tuple of 4 elements : (plugin_name, component_name, instance_id, adjusted_component_path) return empty tuple if the intance is not valid @rtype: tuple |
|
plugin_classes
|
plugins
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0beta1 on Wed Jan 16 19:08:58 2008 | http://epydoc.sourceforge.net |