This page collects possibilities for the 3.2 version of GRAMPS
For 3.1 we have: Python 2.5 or greater, PyGTK2 2.10 or greater, Python Glade bindings, librsvg2 (svg icon view), xdg-utils
Recommended or optional: GraphViz, gtkspell, ttf-freefont
* change to PyGTK 2.12. Reason: Move away from libglade to GtkBuilder. Info: [http://www.micahcarrick.com/05-30-2008/gtk-builder-libglade-faq.html], example: [http://www.micahcarrick.com/01-01-2008/gtk-glade-tutorial-part-3.html]. ''Developers'': ?
==Database backend changes==
Are there features that require database change
. This should happen in the beginning of the development cycle.
* '''event subtype''': bug tracker:[http://www.gramps-project.org/bugs/view.php?id=1302]. There is partial support for this in GEDCOM that is not present in Gramps. This addition would mean a rework of the event type system to make it more user friendly to the user, instead of the copy of GEDCOM it is now: selection of most used events, main events with subtypes, addition of iternaries as subtype to use for map display, .... ''Developers'': bmcage
This section lists main goals developers want to achieve with GRAMPS 3.2
* '''File Organization (GEPS 008)''': bug tracker:[http://www. gramps-project. org/bugs/view.php?id=2622]. ''Developers'': ?* ''' Import Export Merge (GEPS 009)''': bug tracker: [http://www. gramps-project.org/bugs/view.php?id=2623]. ''Developers'': ?* ''' Beter API documentation''' : bug tracker:[http://www.gramps-project.org/bugs/view.php?id= 2691] . ''Developers'': ?