Define a Plugin Interface
We should implement a plugin interface that every plugin should extend. This will normalize the way the plugins are made and we will be able to use the full functionalities of the plugins in the main code.
This will also be useful to detect if a class is a plugin thus to load it.
This blueprint should define that interface : list of methods to implements.
Blueprint information
- Status:
- Complete
- Approver:
- Gladex Developers
- Priority:
- Undefined
- Drafter:
- Oumar Aziz OUATTARA
- Direction:
- Needs approval
- Assignee:
- Oumar Aziz OUATTARA
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
0.5
- Started by
- Oumar Aziz OUATTARA
- Completed by
- Oumar Aziz OUATTARA
Whiteboard
2008.02.
<snip!>
2008-02-25: pax: I set up a wiki page for this specification
2008-02-26: paxmanchris: The class detailed on the wiki-page looks like a good idea. I think this way it will be simpler to validate if a plugin has the necessary functions and return values this way.
2008-02-27: wattazoum: I have updated the interface to add a non mandatory getInfos() method. The python plugin has been migrated to the new way of doing (still to be validated). I'll try to migrate the perl and ruby plugins too. See the attached bzr branch for more info
2008-02-27: wattazoum: I have migrated all the plugins to the new interface.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
