24 Mar 2005 12:29:55 UTC
- Distribution: PXP
- Source (raw)
- Browse (raw)
- How to Contribute
- Testers (0 / 19 / 12)
- KwaliteeBus factor: 0
- License: unknown
- Activity24 month
- Download (14.65KB)
- MetaCPAN Explorer
- Subscribe to distribution
- This version
- Latest versionDBARTH David Barth
PXP::Plugin - Plugin class definition (used only in the internal registry)
<plugin id="IMC::WebApp::TestPlugin" name="Test plugin" version="0.1" provider-name='IDEALX'>
A plugin groups together a set of extensions and/or extension-points.
PXP::Pluginrepresents such a container as it is read and its content loaded into the system. A common interface is provided to access the configuration descriptors and the actual implementation that has been loaded into the system.
PXP::Pluginobject is NOT a plugin.
A real plugin, is just a set of Perl modules loaded according to the 'plugin.xml' descriptor file.
Plugin dependencies are supported with the <require> tag.
We support only a subset of the Eclipse plugin model.
- instantiateExtension($class, @args)
Load a perl class ($class) and instantiate a new object of this class, with optional arguments for the object initializer (@args)
Return the new instance or undef if the class could not be loaded
- name, id, version, providerName
Basic accessors for plugin properties.
Accessor for the 'resourceDir' attribute. 'resourceDir' points to the directory containing the resources bundled with the plugin, such as config files, templates, etc.
This method is called by the PluginRegistry as it loads the plugin.
See the article on eclipse.org describing the plugin architecture : http://www.eclipse.org/articles/Article-Plug-in-architecture/plugin_architecture.html
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 476:
You forgot a '=back' before '=head1'