Gramps 4.0 Wiki Manual - Plugin Manager

From Gramps
Jump to: navigation, search
Gnome-important.png Special copyright notice: All edits to this page need to be under two different copyright licenses:

These licenses allow the Gramps project to maximally use this wiki manual as free content in future Gramps versions. If you do not agree with this dual license, then do not edit this page. You may only link to other pages within the wiki which fall only under the GFDL license via external links (using the syntax: []), not via internal links.
Also, only use the known Typographical conventions

Previous Index Next

The Plugin Manager is available from the menu Help ->Plugin Manager. Many of the features of the Plugin Manager are intended for developers, and the dialogues described below are those seen by developers. The features for normal users are noted below where they are different.

Gramps detects whether it is being run in User mode or Developer mode by the 'optimise' flag:

python -O

See Debugging Gramps.

Gramps consists of a core plus many plugins. When Gramps starts, the core is loaded and only a limited number of plugins are loaded. This decreases the startup time and memory requirements of Gramps. Subsequently, many plugins are automatically loaded by Gramps as they are needed, so that many users will not need to be aware of the existence of plugins, or their delayed loading.

The Plugin Manager allows you to control how Gramps manages plugins.

Plugin types

There are two main categories of plugins in Gramps: "user plugins" and "system plugins". User plugins are those that you use and control to provide different functionality for you. The system plugins are used by Gramps.

The following types of User Plugins are present in Gramps:

  1. doc creators: Backends for which Gramps can write reports (pdf, odf, ascii text, ...)
  2. exporters: export formats you can export your data too via menu Family Trees ->Export...
  3. gramplets: small programs you can embed in the GrampletView, or detach and use as a normal window
  4. gramps views: the views visible in the main window of Gramps
  5. importers: import formats from which Gramps can import data via menu Family Trees ->Import...
  6. map service: targets that can be used on the place view to go to an internet map service (Go toolbar button)
  7. quickreport: small reports that are available in the context menu on the listviews, or via the Quickreport gramplet
  8. reports: Textual or graphical reports Gramps can produce
  9. tools: Tools you can start via the menu Tools

The following types of System Plugins are present in Gramps:

  1. plugin libs: libraries that are present giving extra functionality.
  2. relationships: relationship calculators for different languages

There are many plugins that come with Gramps. However, anyone can also write a plugin and share it. These third-party plugins are called "addons". We highly encourage users and developers to share their creations with other Gramps users.

Registration and loading

Plugins are either held locally on the computer and are known about by Gramps, when they are said to be Registered, or they are held on a remote computer and Gramps only knows their name, type and description, when they are said to be Addons.

When Gramps starts, information is automatically read about the local plugins, so that they become registered. The Plugin Manager can be used to download remote Addons so that they too become registered.

Registered (i.e. local) plugins are loaded by Gramps in the following situations:

  1. they are automatically loaded at startup. Some plugin types are loaded at startup (e.g., non hidden views), some plugins can have a flag that forces load on startup,
  2. they are automatically loaded by virtue of the user clicking on a view or requesting a report,
  3. they are loaded by the user explicitly requesting load in the plugin manager,
  4. remote plugins are loaded at the same time as they are registered by using Install Addons described below.


The plugin Manager can be used to hide or unhide plugins. Some menus will not display hidden addons, so that the addon cannot be selected. For example, if a Gramplet is hidden, then it will not appear in the "Add a gramplet" context menu which appear when right clicking the background of the Gramplets main tab. However, hiding some addons (such as Relationships or Gramps Views) has no effect and may not even be allowed.


There are two tabs for the Plugin Manager: Registered Plugins and Loaded Plugins.

Registered Plugins

Fig. 9.1 Registered plugins

Here you see a list of all plugins that Gramps has found. These are the plugins which are part of Gramps, as well as the plugins found in the gramps40/plugins directory within the Gramps User Directory. The type of plugin is shown in the first column.

A plugin can be made hidden or unhidden. This is only useful for the User Plugins.

Loaded Plugins

Fig. 9.2 Loaded plugins

Here you see a list of all plugins that have been attempted to be loaded. Normally, all views (such as the Relationship View) will be loaded, and all gramplets/reports/tools you have used will be loaded automatically.

If there was an error during the loading of a plugin, then the staus will be shown in this tab. Double clicking a row showing a failure opens a dialog showing the error in detail. You can use this to contact the plugin author or the Gramps bug list.

Later if you decide that you do not like an Addon, you can mark it "hidden" and it will no longer show.

Previous Index Next