Difference between revisions of "Addons development"

From Gramps
Jump to: navigation, search
m (Develop your addon)
(Test your addon as you develop: remove space)
 
(83 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{man warn|Warning:|This page documents the API, methods, and best practices for developing a 3rd-party addon for GRAMPS 3.2 / 3.3 / 3.4.}}
+
{{man warn|Warning:|This page documents the API, methods, and best practices for developing a [[Third-party Addons|Third-party Addon]] for Gramps 4.2 and later. For 4.2 and earlier, see [[Addons_development_old]]. }}
  
Addons for GRAMPS can extend the program in many different ways. You can add any of the following types of addons:
+
Addons for Gramps can extend the program in many different ways. You can add any of the following [https://github.com/gramps-project/gramps/blob/master/gramps/gen/plug/_pluginreg.py types] of addons:
  
# Doc creator
+
#Report
# Exporter
+
#Quickreport
# Gramplet
+
#Tool
# Importer
+
#Importer
# Map service
+
#Exporter
# Plugin lib
+
#Doc creator
# Quickreport
+
#Plugin lib
# Relationships
+
#Map service
# Report
+
#Gramps View
# Tool
+
#Relationships
# View
+
#Gramplet
 +
#Sidebar
  
 
Writing an addon is fairly straightforward if you have just a little bit of Python experience. And sharing your addon is the right thing to do. The general steps to writing an addon and sharing your own addons are:
 
Writing an addon is fairly straightforward if you have just a little bit of Python experience. And sharing your addon is the right thing to do. The general steps to writing an addon and sharing your own addons are:
Line 22: Line 23:
 
# Package your addon
 
# Package your addon
 
# List and document your addon
 
# List and document your addon
# Support it through issue tracker
+
# Support it through the issue tracker
# Maintain the code as GRAMPS continues to evolve
+
# Maintain the code as Gramps continues to evolve
  
 
We'll now look at each of these steps in detail.
 
We'll now look at each of these steps in detail.
 +
Note that this wiki expects that addons are developed under Linux; while it is possible to do so under Windows, some of the steps will vary and the process has not been fully debugged, so user beware.
  
 
== Develop your addon ==
 
== Develop your addon ==
  
gramps-addons subversion repository has the following structure:
+
The [http://github.com/gramps-project/addons-source addons-source] git repository has the following structure:
  
* /gramps-addons
+
* /addons-source
** /trunk
+
** /''IndividualNameOfAddon1''
*** /contrib
+
** /''IndividualNameOfAddon2''
 +
** ...
 +
 
 +
The [http://github.com/gramps-project/addons addons] git repository has the following structure:
 +
 
 +
* /addons
 +
** /gramps42
 +
*** /download
 +
*** /listings
 +
** /gramps50
 
*** /download
 
*** /download
** /branches
+
*** /listings
*** /gramps{{stable_branch}}
+
*** /gramps32
+
**** /contrib
+
**** /download
+
  
The contrib subdirectories hold the source code for the addons for a particular version. If you are working on a addon for gramps{{stable_branch}} then you should be working in gramps-addons/branches/gramps{{stable_branch}}/contrib. If you are working in gramps/trunk then you should use gramps-addons/trunk/contrib.
+
The '''addon-source''' repository holds the source code for the addons with branches holding the version for different gramps. If you are working on an addon for gramps for gramps42, be sure to use the gramps42 git branch, as the default is master branch (currently gramsp 5.x).  Example commands are shown below.
  
These steps show how to download and work with the addon development tools.
+
Once you have your addon working in one branch, (say gramps42), then you will also want to copy it to the other branch (master), after you have tested it to work properly and edited the '.gpr.py' file appropriately.
  
# Checkout the gramps-addons files from the [https://sourceforge.net/projects/gramps-addons/ gramps-addons] project:
+
=== Get a local copy of Gramps and its addons ===
## cd into gramps trunk, for example:
+
### cd ~/gramps/trunk
+
## Checkout gramps-addons:
+
### svn co https://svn.code.sf.net/p/gramps-addons/code gramps-addons
+
## Change to trunk or branches/gramps{{stable_branch}} directory:
+
### cd gramps-addons/branches/gramps{{stable_branch}}/contrib
+
# Make a new project directory in gramps-addon/branches/gramps{{stable_branch}}/contrib:
+
## mkdir NewProjectName
+
# Initialize the addon:
+
## ./make.py init NewProjectName
+
  
NOTE: to use make.py as shown throughout this document, you may have to use:
+
These steps show how to download the addon sources.
  
  GRAMPSPATH=/path/to/gramps python make.py ...
+
# Get an https://github.com/join account if you don't already have one.
 +
# Request GIT write access for the https://github.com/gramps-project/addons-source project by emailing the [[Contact#Mailing_lists|gramps-devel mailing list]]
 +
See also [[Brief_introduction_to_Git|git introduction]] for instructions on installing git and getting basic settings configured. Also https://help.github.com/articles/generating-an-ssh-key/ will help with setting up credentials for GitHub.
 +
To fully build and advertise a new addon will require local copies of the three repositories, the 'addons-source', 'addons' and the main Gramps source 'gramps'.
  
if the default ("../../..") is not correct.
+
This wiki assumes that the three git repositories local locations are all to be put into the users' home directory and named with the repository names.
  
Follow the development API for your tool, [[Report-writing_tutorial|report]], view, or [[Gramplets]]. Place all of your associated .py, .glade, etc. files in this directory. For general information on GRAMPS development see [[Portal:Developers]] and [[Writing a Plugin]] specifically.
+
The three directories '''must''' be named as shown, and in the same base directory in order for the make.py script to work properly, however they don't have to be located directory in the users home directory.
  
To test your addon as you develop it it is suggested that you replace your GRAMPS user plugin directory with a link to your addon development directory, like so:
+
From your home directory;
  
  cd ~/.gramps/gramps{{stable_branch}}/
+
  git clone git@github.com:gramps-project/addons-source.git addons-source
  mv plugins/* /wherever/trunk/gramps-addons/branches/gramps{{stable_branch}}/contrib/
+
  git clone git@github.com:gramps-project/addons.git addons
  rm -rf plugins
+
  git clone git@github.com:gramps-project/gramps.git gramps
ln -s /wherever/trunk/gramps-addons/branches/gramps{{stable_branch}}/contrib plugins
+
  
GRAMPS will search this folder (and subdirectories) for .grp.py files, and add them to the plugin list.
+
or if you do not have a Github account:
  
If you have code that you want to share between addons, you don't need to do anything special. Currently, GRAMPS adds each directory in which a .gpr.py is found onto the PYTHONPATH which is searched when you perform an import. Thus "import NewProjectName" will work from another addon. You should always make sure you name your addons with a name appropriate for Python imports.
+
git clone https://github.com/gramps-project/addons-source.git addons-source
 +
git clone https://github.com/gramps-project/addons.git addons
 +
git clone https://github.com/gramps-project/gramps.git gramps
  
To commit your changes so that others can use your addon, follow these steps:
+
This will create a copy of the addons-source tree in your home directory at "~/addons-source", and the other trees at their respective locations as well.
  
# Get an http://sourceforge.net account if you don't already have one.
+
To switch to a local copy of the gramps42 branch:
# Request SVN write access for the gramps-addon project from https://sourceforge.net/project/memberlist.php?group_id=285429
+
# Remove the files that should not be added to SVN:
+
## ./make.py clean NewProjectName
+
# Add the project to the repository:
+
## svn add NewProjectName
+
## svn commit -m "A message describing what this addon is"
+
  
Before making additional edits to your addon, you should:
+
cd addons-source
 +
git checkout -b gramps42 origin/maintenance/gramps42
  
# svn update
+
or to work in the master branch:
# svn status
+
 
# svn commit -m "A message describing the changes"
+
cd addons-source
 +
git checkout -b gramps42 origin/master
 +
 
 +
=== Other pre-requisites ===
 +
* Gramps uses Python version 3.2 or higher.  You must have at least that version installed.  If you have installed Gramps 4.2 or higher on your Linux system already, then a sufficient version of Python will be present. If you have more than one version of Python installed, then you must use the correct version for these scripts.  On some systems, both Python 2.x and 3.x are installed.  It is possible that the normal invocation of <code>python</code> starts up Python 2.x, and that to start up Python 3.x requires invoking with <code>python3</code> or <code>python3.4</code> etc.  You can test the version by <code>python –version</code> or <code>python3 –version</code>.  If this is so, replace any usage of 'python' in the examples below with the appropriate invocation.
 +
* The make.py used in construction of the addons requires that the LANGUAGE environment variable be set to 'en_US.UTF-8'.
 +
* The make.py used in construction of the addons requires that the GRAMPSPATH environment variable be set to your path to the Gramps source tree.
 +
* intltool must be installed;
 +
: <code>sudo apt-get install intltool</code>
 +
 
 +
For example if your home directory is '/home/name' and you use the suggested path names, use
 +
: <code>GRAMPSPATH=/home/name/gramps LANGUAGE='en_US.UTF-8' python3 make.py ...</code>
 +
to replace the <code>./make.py</code> in the examples below.
 +
 
 +
=== Create your addon subdirectory ===
 +
* Make a new project directory in addons-source:
 +
: <code>mkdir NewProjectName</code>
 +
 
 +
===Follow the development API for your tool===
 +
Create your NewProjectName.py and NewProjectName.gpr.py files.
 +
 
 +
Follow the development API for your tool, [[Report-writing_tutorial|report]], view, or [[Gramplets]]. Place all of your associated .py, .glade, etc. files in this directory. For general information on Gramps development see [[Portal:Developers]] and [[Writing a Plugin]] specifically.
 +
 
 +
=== Test your addon as you develop ===
 +
To test your addon as you develop it is suggested that you insert your NewProjectName plugin into your Gramps user plugin directory with a link to your addon development directory, like so:
 +
 
 +
cd ~/.gramps/gramps42/plugins
 +
ln -s ~/addons-source/NewProjectName NewProjectName
 +
 
 +
Your installed Gramps will search this folder (and subdirectories) for .gpr.py files, and add them to the plugin list.
 +
 
 +
If you have code that you want to share between addons, you don't need to do anything special. Currently, Gramps adds each directory in which a .gpr.py is found onto the PYTHONPATH which is searched when you perform an import. Thus "import NewProjectName" will work from another addon. You should always make sure you name your addons with a name appropriate for Python imports.
 +
 
 +
=== Commit your changes ===
 +
To commit your changes so that others can see your addon source.
 +
 
 +
* Remove the files that should not be added to GitHub:
 +
: <code>./make.py gramps42 clean NewProjectName</code>
 +
* Add the project to the repository:
 +
: <code>git add NewProjectName</code>
 +
* Commit it with an appropriate message
 +
: <code>git commit -m "A message describing what this addon is"</code>
 +
 
 +
Before committing additional edits to your addon, you should:
 +
 
 +
* to make sure that outside changes do not affect your commit
 +
: <code>git pull --rebase</code>
 +
* only the files you changed should be in this list
 +
: <code>git status</code>
 +
* Commit it with an appropriate message
 +
: <code>git commit -m "A message describing the changes"</code>
 +
 
 +
If you have been given 'push' rights to GitHub 'gramps-project/addons-source', and when you are sure you are done and want to publish to the repository:
 +
 
 +
* to make sure that outside changes do not affect your commit
 +
: <code>git pull --rebase</code>
 +
: <code>git push origin gramps42</code>
 +
 
 +
Also you may want to [[Addons_development#Package_your_addon |Package your addon]] so it can be downloaded via the plugin manager.
  
 
=== Config ===
 
=== Config ===
Line 96: Line 150:
 
Some addons may want to have persistent data (data settings that remain between sessions). You can handle this yourself, or you can use Gramps' built-in configure system.  
 
Some addons may want to have persistent data (data settings that remain between sessions). You can handle this yourself, or you can use Gramps' built-in configure system.  
  
In the file that defines the settings, you would do this:
+
At the top of the source file of your addon, you would do this:
  
  from config import config
+
  from config import config as configman
  cm = config.register_manager("view_placetreeview_0")
+
  config = configman.register_manager("grampletname")
  cm.register("section.variable1", value1)
+
  # register the values to save:
  cm.register("section.variable2", value2)
+
config.register("section.option-name1", value1)
 +
  config.register("section.option-name2", value2)
 
  ...
 
  ...
  cm.init()
+
  # load an existing file, if one:
 +
config.load()
 +
# save it, it case it didn't exist:
 +
config.save()
 +
 
 +
This will create the file "grampletname.ini" and put in the same directory as the addon. If the config file already exists, it remains intact.
  
This will create the file "view_placetreeview_0.ini" and put in the same directory as the addon. In the addon, you can then:
+
In the addon, you can then:
  
  x = cm.get("section.variable1")
+
  x = config.get("section.option-name1")
  cm.set("section.variable1", 3)
+
  config.set("section.option-name1", 3)
  
 
and when this code is exiting, you might want to save the config. In a Gramplet that would be:
 
and when this code is exiting, you might want to save the config. In a Gramplet that would be:
  
 
  def on_save(self):
 
  def on_save(self):
     cm.save()
+
     config.save()
  
 
If your code is a system-level file, then you might want to save the config in the Gramps system folder:
 
If your code is a system-level file, then you might want to save the config in the Gramps system folder:
  
  cm = config.register_manager("system", use_config_path=True)
+
  config = configman.register_manager("system", use_config_path=True)
  
 
This, however, would be rare; most .ini files would go into the plugins directory.
 
This, however, would be rare; most .ini files would go into the plugins directory.
Line 123: Line 183:
 
In other code that might use this config file, you would do this:
 
In other code that might use this config file, you would do this:
  
  from config import config
+
  from config import config as configman
  cm = config.get_manager("view_placetreeview_0")
+
  config = configman.get_manager("grampletname")
  x = cm.get("section.variable1")
+
  x = config.get("section.option-name1")
  
 
=== Localization ===
 
=== Localization ===
Line 133: Line 193:
 
For any addon which you have translations into other languages, you will need to add a way to retrieve the translation. You need to add this to the top of your NewProjectName.py file:
 
For any addon which you have translations into other languages, you will need to add a way to retrieve the translation. You need to add this to the top of your NewProjectName.py file:
  
<pre>
+
from gramps.gen.const import GRAMPS_LOCALE as glocale
from TransUtils import get_addon_translator
+
  _ = glocale.get_addon_translator(__file__).gettext
_ = get_addon_translator().gettext
+
</pre>
+
  
Then you can use the standard "_()" function to translate phrases in your addon.
+
 
 +
Then you can use the standard "_()" function to translate phrases in your addon.  
  
 
You can use one of a few different types of translation functions:
 
You can use one of a few different types of translation functions:
  
# gettext  
+
# gettext
 
# lgettext
 
# lgettext
 +
# ngettext
 
# lngettext
 
# lngettext
# ngettext
+
# sgettext
# ugettext
+
# ungettext
+
 
+
NOTE: Currently we don't have a method of using a context in any of these functions.
+
 
+
The translation functions that are supported are defined as follows.
+
 
+
'''gettext(message)'''
+
 
+
If a fallback has been set, forward gettext() to the fallback. Otherwise, return the translated message. Overridden in derived classes.
+
 
+
'''lgettext(message)'''
+
 
+
If a fallback has been set, forward lgettext() to the fallback. Otherwise, return the translated message. Overridden in derived classes.
+
 
+
'''ugettext(message)'''
+
 
+
If a fallback has been set, forward ugettext() to the fallback. Otherwise, return the translated message as a Unicode string. Overridden in derived classes.
+
 
+
'''ngettext(singular, plural, n)'''
+
 
+
If a fallback has been set, forward ngettext() to the fallback. Otherwise, return the translated message. Overridden in derived classes.
+
 
+
'''lngettext(singular, plural, n)'''
+
  
If a fallback has been set, forward ngettext() to the fallback. Otherwise, return the translated message. Overridden in derived classes.
+
These have become obsolete in Gramps 4; gettext, ngettext, and sgettext always return translated strings in unicode for consistent portability between Python 2 and Python3.
  
'''ungettext(singular, plural, n)'''
+
See the [http://docs.python.org/3/library/gettext.html#the-gnutranslations-class python documentation] for documentation of gettext and ngettext. The "l" versions return the string encoded according to the [http://docs.python.org/3/library/locale.html#locale.setlocale currently set locale]; the "u" versions return unicode strings in Python2 and are not available in Python 3.
  
If a fallback has been set, forward ungettext() to the fallback. Otherwise, return the translated message as a Unicode string. Overridden in derived classes.
+
'''sgettext''' is a Gramps extension that filters out clarifying comments for translators, such as
 +
_("Remaining names | rest")
 +
Where "rest" is the English string that we want to present and "Remaining names" is a hint for translators.
  
 
== Create a Gramps Plugin Registration file ==
 
== Create a Gramps Plugin Registration file ==
Line 183: Line 221:
 
<pre>
 
<pre>
 
register(PTYPE,
 
register(PTYPE,
     gramps_target_version = "3.4",
+
     gramps_target_version = "4.2",
 
     version = "1.0.0",
 
     version = "1.0.0",
 
     ATTR = value,
 
     ATTR = value,
Line 189: Line 227:
 
</pre>
 
</pre>
  
PTYPE is TOOL, GRAMPLET, REPORT, QUICKREPORT, IMPORT, EXPORT, DOCGEN, GENERAL, MAPSERVICE, VIEW, or RELCALC.
+
[https://github.com/gramps-project/gramps/blob/master/gramps/gen/plug/_pluginreg.py#L76 PTYPE] is TOOL, GRAMPLET, REPORT, QUICKVIEW, IMPORT, EXPORT, DOCGEN, GENERAL, MAPSERVICE, VIEW, or RELCALC.
  
ATTR depends on the PTYPE. But you must have '''gramps_target_version''' and '''version'''. gramps_target_version should be a string of the form "X.Y" version number matching Gramps X major, Y minor integer. version is a string of the form "X.Y.Z" representing the version of your addon. X, Y, and Z should all be integers.
+
 
 +
ATTR depends on the PTYPE. But you must have '''gramps_target_version''' and '''version'''. '''gramps_target_version''' should be a string of the form "X.Y" version number matching Gramps X major, Y minor integer. '''version''' is a string of the form "X.Y.Z" representing the version of your addon. X, Y, and Z should all be integers.
  
 
Here is a sample Tool GPR file:
 
Here is a sample Tool GPR file:
Line 201: Line 240:
 
         description =  _("Attaches a shared source to multiple objects."),
 
         description =  _("Attaches a shared source to multiple objects."),
 
         version = '1.0.0',
 
         version = '1.0.0',
         gramps_target_version = '3.4',
+
         gramps_target_version = '4.2',
 
         status = STABLE,
 
         status = STABLE,
 
         fname = 'AttachSourceTool.py',
 
         fname = 'AttachSourceTool.py',
Line 213: Line 252:
 
</pre>
 
</pre>
  
You can see examples of the kinds of addons [http://svn.code.sf.net/p/gramps/code/trunk/gramps/plugins/ here] (for example, see [http://svn.code.sf.net/p/gramps/code/trunk/gramps/plugins/drawreport/drawplugins.gpr.py trunk/gramps/plugins/drawreport/drawplugins.gpr.py]) and see the full documentation [http://svn.code.sf.net/p/gramps/code/trunk/gramps/gen/plug/_pluginreg.py here] in the comments and docstrings.
+
You can see examples of the kinds of addons [https://github.com/gramps-project/gramps/plugins here] (for example, see [https://github.com/gramps-project/gramps/plugins/drawreport/drawplugins.gpr.py gramps/plugins/drawreport/drawplugins.gpr.py]) and see the full documentation [https://github.com/gramps-project/gramps/gen/plug/_pluginreg.py here] in the comments and docstrings.
  
 
Note that this .gpr.py will automatically use translations if you have them (see below). That is, the function "_" is predefined to use your locale translations; you only need to mark the text with _("TEXT") and include a translation of "TEXT" in your translation file. For example, in the above example, _("Attach Source") is marked for translation. If you have developed and packaged your addon with translation support, then that phrase will be converted into the user's language.
 
Note that this .gpr.py will automatically use translations if you have them (see below). That is, the function "_" is predefined to use your locale translations; you only need to mark the text with _("TEXT") and include a translation of "TEXT" in your translation file. For example, in the above example, _("Attach Source") is marked for translation. If you have developed and packaged your addon with translation support, then that phrase will be converted into the user's language.
Line 232: Line 271:
  
 
Each report category has a set of standards and interface. The categories CATEGORY_TEXT and CATEGORY_DRAW use the Document interface of Gramps. See also [[Report API]] for a draft view on this.
 
Each report category has a set of standards and interface. The categories CATEGORY_TEXT and CATEGORY_DRAW use the Document interface of Gramps. See also [[Report API]] for a draft view on this.
The application programming interface or API for reports is treated at [[Report-writing_tutorial]]. For general information on GRAMPS development see [[Portal:Developers]] and [[Writing a plugin]] specifically.
+
 
 +
The application programming interface or API for reports is treated at [[Report-writing_tutorial]]. For general information on Gramps development see [[Portal:Developers]] and [[Writing a plugin]] specifically.
  
 
=== General plugins ===
 
=== General plugins ===
Line 250: Line 290:
 
   description =  _("Provides a library for doing something."),
 
   description =  _("Provides a library for doing something."),
 
   version = '1.0',
 
   version = '1.0',
   gramps_target_version = '3.4',
+
   gramps_target_version = '4.2',
 
   status = STABLE,
 
   status = STABLE,
 
   fname = 'library.py',
 
   fname = 'library.py',
Line 307: Line 347:
 
   category = "WEBSTUFF",
 
   category = "WEBSTUFF",
 
   version = '1.0',
 
   version = '1.0',
   gramps_target_version = '3.4',
+
   gramps_target_version = '5.0',
 
   data = ["a", "b", "c"],
 
   data = ["a", "b", "c"],
 
   )
 
   )
Line 340: Line 380:
 
   description =  _("Provides a collection of stylesheets for the web"),
 
   description =  _("Provides a collection of stylesheets for the web"),
 
   version = '1.0',
 
   version = '1.0',
   gramps_target_version = '3.4',
+
   gramps_target_version = '5.0',
 
   fname = "stylesheet.py",
 
   fname = "stylesheet.py",
 
   load_on_reg = True,
 
   load_on_reg = True,
Line 386: Line 426:
 
== Get translators to translate your addon into multiple languages ==
 
== Get translators to translate your addon into multiple languages ==
  
# Initialize and update the template.pot for your addon:
+
* Initialize and update the template.pot for your addon:
## ./make.py init NewProjectName
+
: <code>cd ~/addons-source</code>
# Initialize a language for your addon (say French, fr):
+
: <code>./make.py gramps42 init NewProjectName</code>
## ./make.py init NewProjectName fr
+
* You should edit the header of template.pot with your information, so it gets copied to individual language files.
# Update it from gramps and other addons:
+
* Initialize a language for your addon (say French, fr):
## ./make.py update NewProjectName fr
+
: <code>./make.py gramps42 init NewProjectName fr</code>
# Edit contrib/NewProjectName/po/fr-local.po
+
* Update it from gramps and other addons:
# Compile the language:
+
: <code>./make.py gramps42 update NewProjectName fr</code>
## ./make.py compile NewProjectName
+
* Edit the translations file manually:
# Add or update your local language file, and commit changes:
+
: <code>/NewProjectName/po/fr-local.po</code>
## svn add NewProjectName/po/fr-local.po
+
* Compile the language:
## svn commit NewProjectName/po/fr-local.po -m "Added fr po file"
+
: <code>./make.py gramps42 compile NewProjectName</code>
 +
* Add or update your local language file, and commit changes:
 +
: <code>git add NewProjectName/po/fr-local.po</code>
 +
: <code>git commit NewProjectName/po/fr-local.po -m "Added fr po file"</code>
 +
* If you have been given 'push' rights to GitHub 'gramps-project/addons-source', then;
 +
: <code>git push origin gramps42</code>
  
 
== Package your addon ==
 
== Package your addon ==
Line 403: Line 448:
 
To create a downloadable package:
 
To create a downloadable package:
  
  python make.py build NewProjectName
+
: <code>./make.py gramps42 build NewProjectName</code> or
 +
: <code>./make.py gramps50 build NewProjectName</code>  for the master branch.
  
That will build and copy your addon to ../download
+
Note that the
  
NOTE: Running the '''make.py build''' will increment the third number in your dotted version number of all addons in the gpr.py file. Consider this number to be a "build number".
+
This will automatically include the following files in your build:
  
''New for Gramps 3.4'': You need to then make your addon available in listings of various languages. To do that:
+
* *.py
 +
* *.glade
 +
* *.xml
 +
* *.txt
 +
* locale/*/LC_MESSAGES/*.mo
  
python make.py listing
+
Starting with Gramp 5.0, if you have additional files beyond those listed above, you should create a MANIFEST file in the root of your addon folder listing the files (or pattern) one per line, like this sample MANIFEST file:
  
That will create a series of files in the ../listings/  
+
<pre>
 +
README.md
 +
extra_dir/*
 +
help_files/docs/help.html
 +
</pre>
  
Then add the package to SVN:
+
{{man note|Note:|Running the command '''make.py xxx build''' will increment the third number in your dotted version number of all addons in the gpr.py file. Consider this number to be a "build number".}}
  
  svn add ../download/NewProjectName.addon.tgz ../listings/*
+
This will leave your 'addons-source' with untracked changes according to git. You should delete the 'NewProjectName/locale' directory. The updated 'NewProjectName/NewProjectName.gpr.py ' is ready to add and commit the next time you make other changes.
cd ..
+
: <code>rm –rf –v 'NewProjectName/locale'</code>
svn commit -m "Message describing changes"
+
  
== Miscellaneous commands ==
+
Then add the package to GitHub:
  
To build all projects:
+
<pre> cd '~/addons'
 +
git add gramps42/download/NewProjectName.addon.tgz
 +
git commit -m "Added new plugin: NewProjectName"</pre>
 +
or (for the master branch);
 +
<pre> cd '~/addons'
 +
git add gramps50/download/NewProjectName.addon.tgz
 +
git commit -m " Added new plugin: NewProjectName"</pre>
  
python make.py build all
 
  
To compile all projects to their download/Addon.addon.tgz files:
+
== List your addon in the Gramps Plugin Manager==
  
  python make.py compile all
+
{{man warn|Gramps needs to have been built|Make sure you have already built gramps42 or master. Change to the appropriate git branch in your gramps directory, and run 'python3 setup.py build'  See [[Linux:Build_from_source]]}}
  
== List and document your addon ==
+
To create a listing:
  
Edit [[Plugins3.4]] and describe your addon. You can point to the addon.tgz in SVN as the downloadable file. Document the addon in the wiki using the name "Addon:NewProjectName".
+
: <code>cd '~/gramps-addons'</code> or wherever you have built your addon
 +
: <code>GRAMPSPATH=path/to/your/gramps/install ./make.py gramps42 listing NewProjectName</code>
 +
or (for the master branch);
 +
: <code>cd '~/gramps-addons'</code> or wherever you have built your addon
 +
: <code>GRAMPSPATH=path/to/your/gramps/install ./make.py gramps50 listing NewProjectName</code>
 +
 
 +
That will create a series of files in the <tt>../listings/</tt> directory.
 +
 
 +
Then add the updated listing to GitHub:
 +
 
 +
<pre> cd '~/addons'
 +
git add gramps42/listings/*
 +
git commit -m "Added new plugin to listings: NewProjectName"</pre>
 +
or (for the master branch);
 +
<pre> cd '~/addons'
 +
git add gramps50/listings/*
 +
git commit -m " Added new plugin to listings: NewProjectName"</pre>
 +
 
 +
== List and document your addon on the wiki==
 +
 
 +
Document the addon in the wiki using the name {{man menu|Addon:NewProjectName}}.
 +
 
 +
Edit [[4.2_Addons]] or [[5.0_Addons]] and describe your addon.  
 +
 
 +
You can point to the addon.tgz in GitHub as the downloadable file.
 +
 
 +
== Miscellaneous commands ==
 +
 
 +
To build and compile translations for all projects to their download/Addon.addon.tgz files:
 +
 
 +
: <code>python3 make.py gramps42 build all</code>
 +
 
 +
To compile translations for all projects :
 +
 
 +
: <code>python3 make.py gramps42 compile all</code>
  
 
== Support it through issue tracker ==
 
== Support it through issue tracker ==
  
Visit http://www.gramps-project.org/bugs/view_all_bug_page.php and become a user. Suggest to check it regularly.
+
Visit https://gramps-project.org/bugs/view_all_bug_page.php and become a user. Suggest to check it regularly.
  
== Maintain the code as GRAMPS continues to evolve ==
+
== Maintain the code as Gramps continues to evolve ==
 +
 
 +
Remember that Gramps addons exist for many reasons and there are many
 +
Gramps developers that do support addons in various ways (translations,
 +
triage, keeping in sync with master, download infrastructure, etc).
 +
 
 +
Some reasons why the addons exist; they provide:
 +
* A quick way for anyone to share their work; the Gramps-project has never denied adding a addon.
 +
* A method to continuously update and develop a stand-alone component, often before being officially accepted.
 +
* A place for controversial plugins that will never be accepted into core, but are loved by many users (eg, Data Entry Gramplet).
 +
* A place for experimental components to live.
  
 
= Resources =
 
= Resources =
 +
* [[Brief_introduction_to_Git|Git introduction]]
 +
 +
;Gramps Addons site for Gramps 4.2 and newer
 +
* https://github.com/gramps-project/addons-source  - Source code (Git)
 +
* https://github.com/gramps-project/addons - downloadable .tgz files
  
* http://gramps-addons.svn.sourceforge.net/viewvc/gramps-addons/ - SVN browse
+
;Gramps Addons site for Gramps 3.2 to Gramps 4.1.
 +
* https://sourceforge.net/p/gramps-addons/ - Source code (SVN) and downloadable .tgz files
  
 
[[Category:Developers/General]]
 
[[Category:Developers/General]]
Line 450: Line 558:
 
[[Category:Reports]]
 
[[Category:Reports]]
 
[[Category:Gramplets]]
 
[[Category:Gramplets]]
 +
[[Category:Addons]]

Latest revision as of 22:46, 31 May 2016

Gnome-important.png
Warning:

This page documents the API, methods, and best practices for developing a Third-party Addon for Gramps 4.2 and later. For 4.2 and earlier, see Addons_development_old.

Addons for Gramps can extend the program in many different ways. You can add any of the following types of addons:

  1. Report
  2. Quickreport
  3. Tool
  4. Importer
  5. Exporter
  6. Doc creator
  7. Plugin lib
  8. Map service
  9. Gramps View
  10. Relationships
  11. Gramplet
  12. Sidebar

Writing an addon is fairly straightforward if you have just a little bit of Python experience. And sharing your addon is the right thing to do. The general steps to writing an addon and sharing your own addons are:

  1. Develop your addon
  2. Create a Gramps Plugin Registration file (.gpr.py)
  3. Get translators to translate your addon into multiple languages
  4. Package your addon
  5. List and document your addon
  6. Support it through the issue tracker
  7. Maintain the code as Gramps continues to evolve

We'll now look at each of these steps in detail. Note that this wiki expects that addons are developed under Linux; while it is possible to do so under Windows, some of the steps will vary and the process has not been fully debugged, so user beware.

Develop your addon

The addons-source git repository has the following structure:

  • /addons-source
    • /IndividualNameOfAddon1
    • /IndividualNameOfAddon2
    • ...

The addons git repository has the following structure:

  • /addons
    • /gramps42
      • /download
      • /listings
    • /gramps50
      • /download
      • /listings

The addon-source repository holds the source code for the addons with branches holding the version for different gramps. If you are working on an addon for gramps for gramps42, be sure to use the gramps42 git branch, as the default is master branch (currently gramsp 5.x). Example commands are shown below.

Once you have your addon working in one branch, (say gramps42), then you will also want to copy it to the other branch (master), after you have tested it to work properly and edited the '.gpr.py' file appropriately.

Get a local copy of Gramps and its addons

These steps show how to download the addon sources.

  1. Get an https://github.com/join account if you don't already have one.
  2. Request GIT write access for the https://github.com/gramps-project/addons-source project by emailing the gramps-devel mailing list

See also git introduction for instructions on installing git and getting basic settings configured. Also https://help.github.com/articles/generating-an-ssh-key/ will help with setting up credentials for GitHub. To fully build and advertise a new addon will require local copies of the three repositories, the 'addons-source', 'addons' and the main Gramps source 'gramps'.

This wiki assumes that the three git repositories local locations are all to be put into the users' home directory and named with the repository names.

The three directories must be named as shown, and in the same base directory in order for the make.py script to work properly, however they don't have to be located directory in the users home directory.

From your home directory;

git clone git@github.com:gramps-project/addons-source.git addons-source
git clone git@github.com:gramps-project/addons.git addons
git clone git@github.com:gramps-project/gramps.git gramps

or if you do not have a Github account:

git clone https://github.com/gramps-project/addons-source.git addons-source
git clone https://github.com/gramps-project/addons.git addons
git clone https://github.com/gramps-project/gramps.git gramps

This will create a copy of the addons-source tree in your home directory at "~/addons-source", and the other trees at their respective locations as well.

To switch to a local copy of the gramps42 branch:

cd addons-source
git checkout -b gramps42 origin/maintenance/gramps42

or to work in the master branch:

cd addons-source
git checkout -b gramps42 origin/master

Other pre-requisites

  • Gramps uses Python version 3.2 or higher. You must have at least that version installed. If you have installed Gramps 4.2 or higher on your Linux system already, then a sufficient version of Python will be present. If you have more than one version of Python installed, then you must use the correct version for these scripts. On some systems, both Python 2.x and 3.x are installed. It is possible that the normal invocation of python starts up Python 2.x, and that to start up Python 3.x requires invoking with python3 or python3.4 etc. You can test the version by python –version or python3 –version. If this is so, replace any usage of 'python' in the examples below with the appropriate invocation.
  • The make.py used in construction of the addons requires that the LANGUAGE environment variable be set to 'en_US.UTF-8'.
  • The make.py used in construction of the addons requires that the GRAMPSPATH environment variable be set to your path to the Gramps source tree.
  • intltool must be installed;
sudo apt-get install intltool

For example if your home directory is '/home/name' and you use the suggested path names, use

GRAMPSPATH=/home/name/gramps LANGUAGE='en_US.UTF-8' python3 make.py ...

to replace the ./make.py in the examples below.

Create your addon subdirectory

  • Make a new project directory in addons-source:
mkdir NewProjectName

Follow the development API for your tool

Create your NewProjectName.py and NewProjectName.gpr.py files.

Follow the development API for your tool, report, view, or Gramplets. Place all of your associated .py, .glade, etc. files in this directory. For general information on Gramps development see Portal:Developers and Writing a Plugin specifically.

Test your addon as you develop

To test your addon as you develop it is suggested that you insert your NewProjectName plugin into your Gramps user plugin directory with a link to your addon development directory, like so:

cd ~/.gramps/gramps42/plugins
ln -s ~/addons-source/NewProjectName NewProjectName

Your installed Gramps will search this folder (and subdirectories) for .gpr.py files, and add them to the plugin list.

If you have code that you want to share between addons, you don't need to do anything special. Currently, Gramps adds each directory in which a .gpr.py is found onto the PYTHONPATH which is searched when you perform an import. Thus "import NewProjectName" will work from another addon. You should always make sure you name your addons with a name appropriate for Python imports.

Commit your changes

To commit your changes so that others can see your addon source.

  • Remove the files that should not be added to GitHub:
./make.py gramps42 clean NewProjectName
  • Add the project to the repository:
git add NewProjectName
  • Commit it with an appropriate message
git commit -m "A message describing what this addon is"

Before committing additional edits to your addon, you should:

  • to make sure that outside changes do not affect your commit
git pull --rebase
  • only the files you changed should be in this list
git status
  • Commit it with an appropriate message
git commit -m "A message describing the changes"

If you have been given 'push' rights to GitHub 'gramps-project/addons-source', and when you are sure you are done and want to publish to the repository:

  • to make sure that outside changes do not affect your commit
git pull --rebase
git push origin gramps42

Also you may want to Package your addon so it can be downloaded via the plugin manager.

Config

Some addons may want to have persistent data (data settings that remain between sessions). You can handle this yourself, or you can use Gramps' built-in configure system.

At the top of the source file of your addon, you would do this:

from config import config as configman
config = configman.register_manager("grampletname")
# register the values to save:
config.register("section.option-name1", value1)
config.register("section.option-name2", value2)
...
# load an existing file, if one:
config.load()
# save it, it case it didn't exist:
config.save()

This will create the file "grampletname.ini" and put in the same directory as the addon. If the config file already exists, it remains intact.

In the addon, you can then:

x = config.get("section.option-name1")
config.set("section.option-name1", 3)

and when this code is exiting, you might want to save the config. In a Gramplet that would be:

def on_save(self):
    config.save()

If your code is a system-level file, then you might want to save the config in the Gramps system folder:

config = configman.register_manager("system", use_config_path=True)

This, however, would be rare; most .ini files would go into the plugins directory.

In other code that might use this config file, you would do this:

from config import config as configman
config = configman.get_manager("grampletname")
x = config.get("section.option-name1")

Localization

For general help on translations in Gramps, see Coding for translation. However, that will only use translations that come with Gramps, or allows you to contribute translations to the Gramps core. To have your own managed translations that will be packaged with your addon, read the rest of this page.

For any addon which you have translations into other languages, you will need to add a way to retrieve the translation. You need to add this to the top of your NewProjectName.py file:

from gramps.gen.const import GRAMPS_LOCALE as glocale
 _ = glocale.get_addon_translator(__file__).gettext


Then you can use the standard "_()" function to translate phrases in your addon.

You can use one of a few different types of translation functions:

  1. gettext
  2. lgettext
  3. ngettext
  4. lngettext
  5. sgettext

These have become obsolete in Gramps 4; gettext, ngettext, and sgettext always return translated strings in unicode for consistent portability between Python 2 and Python3.

See the python documentation for documentation of gettext and ngettext. The "l" versions return the string encoded according to the currently set locale; the "u" versions return unicode strings in Python2 and are not available in Python 3.

sgettext is a Gramps extension that filters out clarifying comments for translators, such as

_("Remaining names | rest")

Where "rest" is the English string that we want to present and "Remaining names" is a hint for translators.

Create a Gramps Plugin Registration file

First, create the NewProjectName.gpr.py file. The registration takes this general form:

register(PTYPE,
     gramps_target_version = "4.2",
     version = "1.0.0",
     ATTR = value,
)

PTYPE is TOOL, GRAMPLET, REPORT, QUICKVIEW, IMPORT, EXPORT, DOCGEN, GENERAL, MAPSERVICE, VIEW, or RELCALC.


ATTR depends on the PTYPE. But you must have gramps_target_version and version. gramps_target_version should be a string of the form "X.Y" version number matching Gramps X major, Y minor integer. version is a string of the form "X.Y.Z" representing the version of your addon. X, Y, and Z should all be integers.

Here is a sample Tool GPR file:

register(TOOL, 
         id    = 'AttachSource',
         name  = _("Attach Source"),
         description =  _("Attaches a shared source to multiple objects."),
         version = '1.0.0',
         gramps_target_version = '4.2',
         status = STABLE,
         fname = 'AttachSourceTool.py',
         authors = ["Douglas S. Blank"],
         authors_email = ["doug.blank@gmail.com"],
         category = TOOL_DBPROC,
         toolclass = 'AttachSourceWindow',
         optionclass = 'AttachSourceOptions',
         tool_modes = [TOOL_MODE_GUI]
         )

You can see examples of the kinds of addons here (for example, see gramps/plugins/drawreport/drawplugins.gpr.py) and see the full documentation here in the comments and docstrings.

Note that this .gpr.py will automatically use translations if you have them (see below). That is, the function "_" is predefined to use your locale translations; you only need to mark the text with _("TEXT") and include a translation of "TEXT" in your translation file. For example, in the above example, _("Attach Source") is marked for translation. If you have developed and packaged your addon with translation support, then that phrase will be converted into the user's language.

Report plugins

The possible report categories are (gen/plug/_pluginreg.py):

#possible report categories
CATEGORY_TEXT       = 0
CATEGORY_DRAW       = 1
CATEGORY_CODE       = 2
CATEGORY_WEB        = 3
CATEGORY_BOOK       = 4
CATEGORY_GRAPHVIZ   = 5
REPORT_CAT          = [ CATEGORY_TEXT, CATEGORY_DRAW, CATEGORY_CODE,
                        CATEGORY_WEB, CATEGORY_BOOK, CATEGORY_GRAPHVIZ]

Each report category has a set of standards and interface. The categories CATEGORY_TEXT and CATEGORY_DRAW use the Document interface of Gramps. See also Report API for a draft view on this.

The application programming interface or API for reports is treated at Report-writing_tutorial. For general information on Gramps development see Portal:Developers and Writing a plugin specifically.

General plugins

The plugin framework also allows you to create generic plugins for use. This includes the ability to create libraries of functions, and plugins of your own design.

Example: A library of functions

In this example, a file name library.py will be imported at time of registration (when Gramps starts):

# file: library.gpr.py

register(GENERAL, 
   id    = 'My Library',
   name  = _("My Library"),
   description =  _("Provides a library for doing something."),
   version = '1.0',
   gramps_target_version = '4.2',
   status = STABLE,
   fname = 'library.py',
   load_on_reg = True,
  )

The code in the file library.py will be imported when Gramps begins. You can access the loaded module in other code by issuing an "import library" as Python keeps track of files already imported. However, the amount of useful code that you can run when the program is imported is limited. You might like to have the code do something that requires a dbstate or uistate object, and neither of these is available when just importing a file.

If "load_on_reg" was not True, then this code would be unavailable until manually loaded. There is no automatic mechanism in Gramps to load GENERAL plugins automatically.

In addition to importing a file at startup, one can also run a single function inside a GENERAL plugin, and it will be passed the dbstate, the uistate, and the plugin data. The function must be called "load_on_reg", and take those three parameters, like this:

# file: library.py

def load_on_reg(dbstate, uistate, plugin):
    """
    Runs when plugin is registered.
    """
    print "Hello World!"

Here, you could connect signals to the dbstate, open windows, etc.

Another example of what one can do with the plugin interface is to create a general purpose plugin framework for use by other plugins. Here is the basis for a plugin system that:

  • allows plugins to list data files
  • allows the plugin to process all of the data files

First, the gpr.py file:


register(GENERAL, 
  id    = "ID",
  category = "CATEGORY",
  load_on_reg = True,
  process = "FUNCTION_NAME",
  )

This example uses three new features:

  1. GENERAL plugins can have a category
  2. GENERAL plugins can have a load_on_reg function that returns data
  3. GENERAL plugins can have a function (called "process") which will process the data

If you (or someone else) create additional general plugins of this category, and they follow your load_on_reg data format API, then they could be used just like your original data. For example, here is an additional general plugin in the 'WEBSTUFF' category:

# anew.gpr.py

register(GENERAL, 
  id    = 'a new plugin',
  category = "WEBSTUFF",
  version = '1.0',
  gramps_target_version = '5.0',
  data = ["a", "b", "c"],
  )

This doesn't have load_on_reg = True, nor does it have a fname or process, but it does set the data directly in the .gpr.py file. Then we have the following results:

>>> from gui.pluginmanager import GuiPluginManager
>>> PLUGMAN = GuiPluginManager.get_instance()
>>> PLUGMAN.get_plugin_data('WEBSTUFF')
["a", "b", "c", "Stylesheet.css", "Another.css"]
>>> PLUGMAN.process_plugin_data('WEBSTUFF')
["A", "B", "C", "STYLESHEET.CSS", "ANOTHER.CSS"]

Registered GENERAL Categories

The following are the published secondary plugins API's (type GENERAL, with the following categories):

WEBSTUFF

A sample gpr.py file:

# stylesheet.gpr.py

register(GENERAL, 
  id    = 'system stylesheets',
  category = "WEBSTUFF",
  name  = _("CSS Stylesheets"),
  description =  _("Provides a collection of stylesheets for the web"),
  version = '1.0',
  gramps_target_version = '5.0',
  fname = "stylesheet.py",
  load_on_reg = True,
  process = "process_list",
  )

Here is the associated program:

# file: stylesheet.py

def load_on_reg(dbstate, uistate, plugin):
    """
    Runs when plugin is registered.
    """
    return ["Stylesheet.css", "Another.css"]

def process_list(files):
    return [file.upper() for file in files]

Filters

For example:

register(GENERAL,
   category="Filters",
   ...
   load_on_reg = True
)
def load_on_reg(dbstate, uistate, plugin):
    # returns a function that takes a namespace, 'Person', 'Family', etc.

    def filters(namespace):
        print "Ok...", plugin.category, namespace, uistate
        # return a Filter object here
    return filters

Get translators to translate your addon into multiple languages

  • Initialize and update the template.pot for your addon:
cd ~/addons-source
./make.py gramps42 init NewProjectName
  • You should edit the header of template.pot with your information, so it gets copied to individual language files.
  • Initialize a language for your addon (say French, fr):
./make.py gramps42 init NewProjectName fr
  • Update it from gramps and other addons:
./make.py gramps42 update NewProjectName fr
  • Edit the translations file manually:
/NewProjectName/po/fr-local.po
  • Compile the language:
./make.py gramps42 compile NewProjectName
  • Add or update your local language file, and commit changes:
git add NewProjectName/po/fr-local.po
git commit NewProjectName/po/fr-local.po -m "Added fr po file"
  • If you have been given 'push' rights to GitHub 'gramps-project/addons-source', then;
git push origin gramps42

Package your addon

To create a downloadable package:

./make.py gramps42 build NewProjectName or
./make.py gramps50 build NewProjectName for the master branch.

Note that the

This will automatically include the following files in your build:

  • *.py
  • *.glade
  • *.xml
  • *.txt
  • locale/*/LC_MESSAGES/*.mo

Starting with Gramp 5.0, if you have additional files beyond those listed above, you should create a MANIFEST file in the root of your addon folder listing the files (or pattern) one per line, like this sample MANIFEST file:

README.md
extra_dir/*
help_files/docs/help.html
Gramps-notes.png
Note:

Running the command make.py xxx build will increment the third number in your dotted version number of all addons in the gpr.py file. Consider this number to be a "build number".

This will leave your 'addons-source' with untracked changes according to git. You should delete the 'NewProjectName/locale' directory. The updated 'NewProjectName/NewProjectName.gpr.py ' is ready to add and commit the next time you make other changes.

rm –rf –v 'NewProjectName/locale'

Then add the package to GitHub:

 cd '~/addons'
 git add gramps42/download/NewProjectName.addon.tgz
 git commit -m "Added new plugin: NewProjectName"

or (for the master branch);

 cd '~/addons'
 git add gramps50/download/NewProjectName.addon.tgz
 git commit -m " Added new plugin: NewProjectName"


List your addon in the Gramps Plugin Manager

Gnome-important.png
Gramps needs to have been built

Make sure you have already built gramps42 or master. Change to the appropriate git branch in your gramps directory, and run 'python3 setup.py build' See Linux:Build_from_source

To create a listing:

cd '~/gramps-addons' or wherever you have built your addon
GRAMPSPATH=path/to/your/gramps/install ./make.py gramps42 listing NewProjectName

or (for the master branch);

cd '~/gramps-addons' or wherever you have built your addon
GRAMPSPATH=path/to/your/gramps/install ./make.py gramps50 listing NewProjectName

That will create a series of files in the ../listings/ directory.

Then add the updated listing to GitHub:

 cd '~/addons'
 git add gramps42/listings/*
 git commit -m "Added new plugin to listings: NewProjectName"

or (for the master branch);

 cd '~/addons'
 git add gramps50/listings/*
 git commit -m " Added new plugin to listings: NewProjectName"

List and document your addon on the wiki

Document the addon in the wiki using the name Addon:NewProjectName.

Edit 4.2_Addons or 5.0_Addons and describe your addon.

You can point to the addon.tgz in GitHub as the downloadable file.

Miscellaneous commands

To build and compile translations for all projects to their download/Addon.addon.tgz files:

python3 make.py gramps42 build all

To compile translations for all projects :

python3 make.py gramps42 compile all

Support it through issue tracker

Visit https://gramps-project.org/bugs/view_all_bug_page.php and become a user. Suggest to check it regularly.

Maintain the code as Gramps continues to evolve

Remember that Gramps addons exist for many reasons and there are many Gramps developers that do support addons in various ways (translations, triage, keeping in sync with master, download infrastructure, etc).

Some reasons why the addons exist; they provide:

  • A quick way for anyone to share their work; the Gramps-project has never denied adding a addon.
  • A method to continuously update and develop a stand-alone component, often before being officially accepted.
  • A place for controversial plugins that will never be accepted into core, but are loved by many users (eg, Data Entry Gramplet).
  • A place for experimental components to live.

Resources

Gramps Addons site for Gramps 4.2 and newer
Gramps Addons site for Gramps 3.2 to Gramps 4.1.