GEPS 005: Enhanced Plugin Interface

From Gramps
Revision as of 18:43, 21 October 2007 by Pez4brian (talk | contribs) (Details)
Jump to: navigation, search

Proposed changes for enhancing GRAMPS by updating the plugin interface to:

  1. be more flexible for future changes
  2. be more consistent across different types of plugins
  3. be more abstract


The current plugin architecture is quite nice, and allows many different types of features to be added by users, or by developers. However, it needs to be updated so that it can support all of the different types of current and future plugins.


There are a fixed number of parameters that one can use in defining each plugin type. Some plugins have had to be adapted to handle additional needs (like user interactions via a GUI). There is a middle layer of code that connects the plugin code with the plugin type. In this code there are places where the args get passed around like (item[0], item[1], item[3], item[10]) depending on the plugin type. In addition, some plugins have to go all the way down to the graphics interface (gtk).


  1. Update all of the reports to use abstract options ("menu" options) (see discussion here
  2. Generalize the report dialogs and remove the need for a report plugin to ever need to define or customize a dialog.
  3. Move each plugin registration and handler from its current specific register_TYPE() to generic register(type=TYPE)
  4. Rethink each plugin to be a well-defined API


This proposal is discussed here:

If you have ideas, comments, or questions, please note them here.