Difference between revisions of "Gramplets"
m (→Gramps 3.x and older: outdated target version made sample non-functional)
|Line 283:||Line 283:|
gramplet = "WidgetGramplet",
gramplet = "WidgetGramplet",
gramps_target_version = "
gramps_target_version = ".",
Revision as of 04:35, 23 August 2020
This section contains technical details about programming Gramplets and is intended for Developers.
A Gramplet is a type of Gramps plugin. Gramplets are mini-view that is designed to be composed with other Gramplets or Views to create a way to see your Family Tree that is just right for you. In fact, Gramplets can be made to do just about anything that you want.
- 1 Gramplet Interface
- 1.1 Hello World
- 1.2 Hello World, with Class
- 1.3 Register Options
- 1.4 Core Methods
- 1.5 Textual Output Methods
- 1.6 GUI Interface
- 1.7 GUI Options
- 1.8 Predefined Properties
- 1.9 Persistance
- 1.10 Advanced Settings
- 1.11 Learning More
There are 6 main kinds of plugins:
- Reports: output for printing or display
- Tools: a method for processing data
- Quick View: a list of details based on the current object
- Importer: reads a file into your current tree
- Exporter: writes a file from your current tree
- Gramplets: interactive views for moving, analysing, displaying, etc.
There are two plugin directories: a global/system one, and a private/personal one. You can easily create a plugin by simply putting a file in your personal plugin directory (usually in .gramps/grampsxx/plugins/gramplet/ ).
In teaching programming, a common "first program" is to write a program that says "Hello World".
Let us jump right in and take a look at such a gramplet named HelloWorld.py:
Create a python file named HelloWorld.py and add the following content:
# File: HelloWorld.py def init(gui): gui.set_text("Hello world!")
And create another python file named HelloWorld.gpr.py with the following content:
# File: HelloWorld.gpr.py register(GRAMPLET, id="Hello World Gramplet", name=_("Hello World Gramplet"), description = _("a program that says 'Hello World'"), status = STABLE, version="0.0.1", fname="HelloWorld.py", height = 20, gramplet = 'init', gramplet_title=_("Sample Gramplet"), gramps_target_version="5.1", help_url="Sample Gramplet" )
If you place these files in your personal user plugins directory (usually in .gramps/grampsxx/plugins/gramplet/ ), and then restart Gramps, you will be able to create this Gramplet. On the Dashboard Category View, right-click in an open area and select the "Hello World Gramplet". You should then see:
The main work of a Gramplet is performed in a function, or a class. In this very simple example, a function
init is defined that takes a single argument,
gui. The function simply sets the gui's text area to be "Hello World!", and that's it. It does this just once, and never changes.
Before a plugin can be used, it needs to be "registered". You call the register function with a number of named-arguments. There are a number of named-arguments that you can provide, including: name, height, content, title, expand, state, and data. We will explore those in detail, below.
Hello World, with Class
Here is the same functionality again, but this time as a class (and the 'Hello World' text in Spanish):
# File: HolaMundo.py from gramps.gen.plug import Gramplet class HolaMundoGramplet(Gramplet): def init(self): self.set_text("¡Hola Mundo!")
# File: HolaMundo.gpr.py register(GRAMPLET, id="Hola Mundo Gramplet", name=_("Hola Mundo Gramplet"), description = _("un programa que dice 'Hola Mundo'"), version="0.0.1", gramps_target_version="5.1", status = STABLE, fname="HolaMundo.py", height = 20, gramplet = 'HelloWorldGramplet', gramplet_title=_("Muestra Gramplet"), help_url="Muestra Gramplet" )
This is the recommended method of creating a Gramplet. The following details describe the properties and methods of this class.
- GRAMPLET: the first argument is the keyword GRAMPLET
- id: the identifying name of the gramplet, unique among all plugins
- name: the translated gramplet's name
- height: the minimum (or maximum) height of the gramplet in normal mode
- fname: the name of your gramplet file
- gramplet: the name of the function or class in fname that creates the gramplet
- gramplet_title: the default gramplet title; user changeable in Configure View
- status: STABLE or UNSTABLE
- version: a string with 2 dots (such as "1.23.14") representing the version number
- gramps_target_version: a string with 2 dots representing the version of Gramps that this gramplet was written for
- help_url: the title of the wiki page that describes the gramplet
At the bare minimum, you need to have the above 10 options when registering your Gramplets.
In addition, you can use the following as well:
- detached_width: the size in pixels of the minimum and default detached height
- detached_height: the size in pixels of the minimum and default detached height
- expand: whether or not the Gramplet should expand to fill the column, if it can
- description: a description of the gramplet
The class-based gramplet utilizes the following methods:
- init(): run once, on construction
- main(): run once per update
- update(): don't change this, it calls main
- active_changed(): run when active-changed is triggered
- db_changed(): run when db-changed is triggered
- set_tooltip(TEXT) - tooltip for gramplet
Don't call main directly; use the update method.
In the db_changed method, you should connect all of the signals that will trigger an update. That typically looks like:
def db_changed(self): self.dbstate.db.connect('person-add', self.update) self.dbstate.db.connect('person-delete', self.update) self.dbstate.db.connect('person-update', self.update) self.dbstate.db.connect('family-add', self.update) self.dbstate.db.connect('family-delete', self.update) self.dbstate.db.connect('family-update', self.update)
The method main() can be written as a normal Python method, or it can be written to run nicely in parallel with other Gramps code. To make it run nicely in parallel, you should issue a yield True every once in a while. For example:
def main(self): for i in range(5000): if i % 500 == 0: yield True yield False
The True means that there is more to do; False means that there is nothing left to do.
Textual Output Methods
The most common kinds of Gramplets are text-based. There are a number of methods to assist with handling this text.
- set_text(TEXT) - clear and set text to TEXT
- append_text(TEXT, scroll_to=POSITION)
- POSITION is 'begin' (top), 'end' (bottom) or 'start' (start of append)
- clear_text() - clears all text
- render_text(TEXT) - for use with A, B, I, U, and TT tags
- A for creating links; use tag HREF="url" for URLs, and WIKI="name" for pages on the wiki
- B for bold
- I for italics
- U for underlined
- TT for a fixed-width, typewriter font
- link(TEXT, LINK-TYPE, DATA) -
- TEXT can be any text
- LINK-TYPE is:
- 'Person' - and DATA is a person handle
- 'PersonList' - and DATA is a list of handles
- 'Family' - and DATA is a family handle
- 'Surname' - and DATA is a person
- 'Given' -
- 'Filter' - and DATA is either:
- 'all people' -
- 'males' - all males
- 'females' - all females
- 'people with unknown gender' - people marked as unknown
- 'people with incomplete names' - people who have a missing surname or given name
- 'people with missing birth dates' - people who have missing birth dates
- 'disconnected people' - people with no parents and no children
- 'all families' - all families
- 'unique surnames' - list of all unique surnames
- 'people with media' - people who have media
- 'media references' - all of the media
- 'unique media' -
- 'missing media' - media for which the file does not exist
- 'media by size' -
- 'list of people'-
- 'URL' - and DATA is a URL
- 'WIKI' - and DATA is a wiki page
- 'Attribute' - and DATA is an attribute (eg, 'Nickname')
- no_wrap() - turn word wrap off DEPRECATED
- set_wrap(BOOL) - change word wrap
Tags are the manner in which you format the text.
tag = self.gui.buffer.create_tag("fixed") tag.set_property("font", "Courier 8") ... start, end = self.gui.buffer.get_bounds() self.gui.buffer.apply_tag_by_name("fixed", start, end) self.append_text("", scroll_to="begin")
Please update or expand this section.
Widget Gramplet example
Occasionally, you might have to dive down to the graphical objects that compose a Gramplet.
If you wanted to put an arbitrary gtk object into the main area of a Gramplet, then you need to replace the standard textview object with your own. Here is the basic structure:
# File: Widget.py from gettext import gettext as _ from gramps.gen.plug import Gramplet from gi.repository import Gtk class WidgetGramplet(Gramplet): def init(self): self.gui.WIDGET = ### Some Widget Constructor ### self.gui.get_container_widget().remove(self.gui.textview) self.gui.get_container_widget().add_with_viewport(self.gui.WIDGET) self.gui.WIDGET.show()
# File: Widget.gpr.py register(GRAMPLET, id= "Widget Gramplet", name=_("Widget Gramplet"), description = _("Widget Gramplet example"), height=100, expand=False, gramplet = 'WidgetGramplet', gramplet_title=_("Widget"), version = '0.0.1', gramps_target_version = "5.1", fname="Widget.py", )
Gramps 3.x and older
# File: Widget.py from gettext import gettext as _ from gramps.gen.plug import Gramplet import gtk class WidgetGramplet(Gramplet): def init(self): self.gui.WIDGET = ### Some Widget Constructor ### self.gui.get_container_widget().remove(self.gui.textview) self.gui.get_container_widget().add_with_viewport(self.gui.WIDGET) self.gui.WIDGET.show()
# File: Widget.gpr.py register(GRAMPLET, id= "Widget Gramplet", name=_("Widget Gramplet"), height=100, expand=False, fname="Widget.py", gramplet = "WidgetGramplet", gramps_target_version = "3.4", gramplet_title=_("Widget"), )
Cairo Clock Example
In fact, with Python, GTK, and cairo, you can make your own widgets that do pretty much anything and look very nice.
Here is an example adding a Cairo Clock (which really keeps time)
- OPTION is one of the menu options in gramps/gen/plug/menu eg:
- OPTION is one of the menu options in gramps/gen/plug/menu eg:
There are a number of preset properties:
- dbstate.db.connect(SIGNAL, METHOD)
- force_update: set True to have the gramplet update, even when minimized
To learn more about writing a Gramplet, it is suggested to look at the existing Gramplets. You can see a complete list of the Gramplet source code here:
- Gramps 3.4 Gramplets
- Gramps 4.2 Gramplets
- Gramps 5.0 Gramplets
- Gramps 5.1 Gramplets
- Gramps Master Gramplets
Click on a filename, to view the source code of that Gramplet.
- master/gramps/gen/plug/_gramplet.py - Base class for non-graphical gramplet code.