Files
evolution/modules/plugin-python/example/org-gnome-hello-python.eplug.xml
Matthew Barnes 32f545cdf0 Simplify EPlugin loading at startup.
- Require all EPlugin and EPluginHook subtypes be registered before
  loading plugins.  This drastically simplifies the EPlugin/EPluginHook
  negotiation.

- Turn most EPluginHook subtypes into GTypeModules and register their
  types from an e_module_load() function (does not include shell hooks).

- Convert EPluginLib and the Mono and Python bindings to GTypeModules
  and register their types from an e_module_load() function, and kill
  EPluginTypeHook.
2009-08-29 17:23:20 -04:00

21 lines
790 B
XML

<?xml version="1.0"?>
<e-plugin-list>
<e-plugin id="org.gnome.evolution.hello_python" type="python" _name="Python Test Plugin" location="@PLUGINDIR@" module_name="hello_python">
<author name="Johnny Jacob" email="jjohnny@novell.com"/>
<_description>
Test Plugin for Python EPlugin loader.
</_description>
<hook class="org.gnome.evolution.mail.bonobomenu:1.0">
<menu id="org.gnome.evolution.mail.browser" target="select">
<!-- the path to the bonobo menu description. Any UI items on Evolution should come here -->
<ui file="@PLUGINDIR@/org-gnome-hello-python-ui.xml"/>
<item type="item" verb="HelloPy" path="/commands/HelloPy" enable="one" activate="say_hello"/>
</menu>
</hook>
</e-plugin>
</e-plugin-list>