Difference between revisions of "Getting started with Gramps development"

From Gramps
Jump to: navigation, search
m
(Eclipse + PyDev)
 
(71 intermediate revisions by 14 users not shown)
Line 1: Line 1:
{{man warn|Warning:|This tutorial is work under progress. Feel free to help and modify it.}}
+
{{man warn|Warning:|This tutorial is a work in progress. Feel free to help and modify it.}}
  
This tutorial aims to help you in your first hacking of GRAMPS. It will help you setting up a development environment and explain where to find the files you need.
+
This tutorial aims to help you in your first [http://en.wikipedia.org/wiki/Hacker_%28programmer_subculture%29 hacking] of Gramps. It will help you setting up a development environment and explain where to find the files you need.
  
 
This tutorial assumes that you are using GNU/Linux (but it might help under another OS) and that you know the basics of Python programming language.
 
This tutorial assumes that you are using GNU/Linux (but it might help under another OS) and that you know the basics of Python programming language.
Line 8: Line 8:
 
== Optional : set up a development environment ==
 
== Optional : set up a development environment ==
  
{{man warn|Warning:|I highly recommend that you do not use your usual environment for developing GRAMPS. Definitely do '''not''' work on your main GRAMPS family tree. Doing so may result in data loss in your GRAMPS Family Tree !}}
+
{{man warn|Warning:|It is highly recommended that you do not use your normal/usual environment for developing Gramps.<br />Definitely do '''not''' work on your main Gramps family tree.<br />Doing so may result in data loss in your Gramps Family Tree !}}
  
If you run your development version of GRAMPS as the usual user, it will show all your usual GRAMPS family trees, so loading one by mistake is possible and a bug may result in losing productive data.  To prevent this, you could use a GRAMPSHOME environment variable to create a separate folder for productive data, see [[Run GRAMPS from a portable drive]] for more information.
+
If you run your development version of Gramps as the usual user, it will show all your usual Gramps family trees, so loading one by mistake is possible and a bug may result in losing productive data.  To prevent this, you could use a [[GRAMPSHOME]] environment variable to create a separate folder for productive data, see [[Run Gramps from a portable drive]] for more information.
  
 
Here are some options you may choose to prevent this. If you have enough resources, I recommend using VirtualBox.  
 
Here are some options you may choose to prevent this. If you have enough resources, I recommend using VirtualBox.  
  
 
=== VirtualBox ===
 
=== VirtualBox ===
[http://www.virtualbox.org/ VirtualBox] is an open source virtualisation solution. Install it, run it and you have a virtual PC in your PC. Network connection works out of the box without extra configuration needed. Install your favorite Linux distribution and start hacking GRAMPS in a full separated environment.
+
[http://www.virtualbox.org/ VirtualBox] is an open source virtualisation solution. Install it, run it and you have a virtual PC in your PC. Network connection works out of the box without extra configuration needed. Install your favorite Linux distribution and start hacking Gramps in a fully separated environment.
  
 
=== Chroot ===
 
=== Chroot ===
You may also use a chroot to result in a similar separation as virtualbox. If you use a chroot for developing GRAMPS, please add information here.
+
You may also use a chroot to result in a similar separation as virtualbox.  
 +
 
 +
If you use Ubuntu, you can set up the chroot environment following these instructions:
 +
[https://help.ubuntu.com/community/BasicChroot Creating a basic Ubuntu chroot]
 +
If you use Gramps in a chroot jail with another Linux distribution, please add information here.
 +
 
 +
You should then have a working chroot environment in /var/chroot (or whichever location you chose).
 +
Enter it with
 +
sudo chroot /var/chroot
 +
This means that within this directory, applications cannot access files without the chroot jail,
 +
i.e. your Gramps install within the directory cannot destroy another install of Gramps in your usual home directory.
 +
 
 +
From a shell within your chroot directory, just clone the Git repository into the chroot folder as usual.
 +
Please note that before running the autogen-Script for generating makefiles, you may need to get some packages:
 +
apt-get install python intltool libglib2.0-dev gedit
  
 
=== Another user ===
 
=== Another user ===
You may also simply do your development as another user, so you won't access to your usual ~/.gramps database when testing.  
+
You may also simply do your development as another user, so you won't access your usual <code>~/.gramps</code> database when testing.
  
=== None of above ===
+
You can also create an alias account with the same user and group IDs, but with a different login name and different home directory, typically, a subdir of the real user's home directory. This gives the benefit of less disk usage, and no permission boundary between the two account aliases. On the other hand, if you are afraid of malicious code within gramps purposefully breaking out and wreaking havoc on your real home account's <code>.gramps</code>, this method is too weak for you. For regular development scenario, though, this setup certainly does suffice.
You have been warned! At a minimum name your test family trees 'a_test_name'. By starting with 'a_test' they show at the top of the family tree manager, and the test makes it clear what they are for.
+
 
 +
This is what the cloning looks like in my <code>/etc/passwd</code>:
 +
vassilii:x:1000:1000:Vassilii Khachaturov,,,:/home/vassilii:/bin/bash
 +
v:x:1000:1000:Vassilii Khachaturov,,,:/home/vassilii/pub:/bin/bash
  
[[Category:Developers/General|G]]
+
Create symlink to the dotfiles you want to reuse. Obviously, don't do this for ''<code>.gramps</code>''! Something like (inside <code>~vassilii/pub</code>):
 +
ln -s ../.bashrc ../.mozilla ../.ratpoisonrc ../.gitconfig .
  
== Get the source tree ==
+
You can use the alias account in a standalone matter (X session under it), or just inside a terminal window (su - <name of the alias account>). All the build, install, and test run of gramps should be done under this account. This will preserve your normal account's .gramps.  
To get the source tree, you will need SVN. Please have a look at the dedicated tutorial [[Brief introduction to SVN]] for details on getting the source trees for the latest current stable branch and the development trunk.
 
  
You can also use a graphical SVN manager like "kdesvn" or "SVN Workbench".
+
Having obtained the gramps source tree, as the first build step, do
 +
./autogen.sh -- --prefix=/home/vassilii/pub/local
 +
('''replace /home/vassilii/pub/ with the actual aliased home directory!!!''')
  
'''This tutorial now assumes you have downloaded GRAMPS' trunk into "~/gramps-trunk". If not, you have to change this path when it is used below.'''
+
After you build and install (no root needed! you install under the local prefix), check that the right (locally built) gramps is on your PATH. Tweak your shell profiles as needed.
  
 +
=== None of above ===
 +
{{man warn|You have been warned!|At a minimum name your test family trees <code>'a_test_name'</code>. By starting with <code>'a_test'</code> they will show at the top of the {{man label|Family Tree}} manager, and the word '''test''' makes it clear what they are created for.}}
  
{{man warn|Warning:|Let it be clear that the settings directory "~/.gramps/" is a '''different''' hidden directory in your home-dir. Do not store anything there.''}}
+
== Mac OS X ==
 +
In order to develop (or even use) Gramps on an Apple Macintosh, you must first install all of the prerequisite libraries and their headers. There are three choices for this [http://live.gnome.org/Gtk%2BOSX Gtk-OSX], [http://www.macports.org MacPorts], or [http://www.finkproject.org Fink]. Full instructions for building Gramps for each is provided here: [[Mac OS X:Build from source:Application package]], [[Mac OS X:Build from source:MacPorts]], or [[Mac OS X:Build from source:fink]].
 +
The last only works with X11, which is no longer included in OS X but can be installed separately. MacPorts can be built with/for either X11 or OS X's native Quartz graphics backend, and Gtk-OSX is exclusively for Quartz.  
  
 
== Install a text editor ==
 
== Install a text editor ==
The following is in alphabetic order. Choose the one you like. Whichever editor you use, make sure that it is set up so that the indent level is 4 spaces. Do not use the Tab character to indent.
+
;Whichever editor you use, make sure that it is set up so that the indent level is 4 spaces. Do not use the Tab character to indent.
 +
 
 +
The following is in alphabetic order. Choose the one you like.
 +
 
 +
=== Eclipse + PyDev ===
 +
[http://www.eclipse.org/downloads/ Eclipse] with [http://pydev.org/manual_101_install.html PyDev] brings an integrated IDE for Python. To run it, you have to do a few steps configuration:
  
=== Eclipse + pydev ===
+
* First, you have to set the path to your python interpreter:
Eclipse with pydev brings an integrated IDE for Python. To run it, you have to do a few steps configuration.
+
** Go in the menu '''Window > Preferences...''';
 +
** Then choose '''PyDev > Interpreters > Python Interpreter'''.
 +
** Click '''New...''' to create a link to your Python executable (for example ''/usr/bin/python3.5'').
  
First, you have to set the path to your python interpreter. Go in the menu "Window"->"Preferences...", then choose "Pydev"->"Interpreter - Python". With "new", you can create a link to "/usr/bin/python2.5". there you are.
+
* Next, you have to set up a PyDev project:
 +
** Go in the menu '''File > New > Project...''';
 +
** Choose '''PyDev Project'''
 +
** Project name could be ''Gramps''
 +
** Uncheck '''Use defaults''' and choose '''~/gramps-trunk''' as the project directory.
 +
** Project type is '''Python 3.5'''
 +
** Interpreter is the one you created at the first step above
 +
** And then you can press '''Finish'''.
  
Next, you have to set up a pydev project. Go in the menu "File" -> "New" -> "Project", and choose a Pydev projet. Project name could be "GRAMPS trunk", uncheck "Use defaults" and choose "~/gramps-trunk" as the project directory. Project type is "Python 2.5", and then you can press "Finish". You are now ready to start coding !
+
You are now ready to start coding!
 +
 
 +
=== pycharm ===
 +
[http://www.jetbrains.com/pycharm/ PyCharm] is more powerful and out-of-the-box than Eclipse with pydev, although it is not Free Software like Eclipse is. Seems to be recognizing more Python syntax and feels faster on my box. I unpacked the distribution, launched bin/pycharm.sh script, and it just worked. 'File » Open Directory' and selected the "Gramps/src" directory in my local checked out Git WD, and things work from there.  
 +
 
 +
'Version Control » Update Project' automatically syncs up with the Git repository.
  
 
=== Emacs or Vim ===
 
=== Emacs or Vim ===
Line 52: Line 94:
  
 
=== Eric4 ===
 
=== Eric4 ===
[http://www.die-offenbachs.de/eric/index.html Eric4] is a python editor. It has everything you need (code completion, python shell, ...)
+
[http://eric-ide.python-projects.org/index.html Eric4] is a python editor. It has everything you need (code completion, python shell, ...)
  
 
=== Geany ===
 
=== Geany ===
[http://geany.uvena.de/ Geany] is a nice development Editor. One feature I like is that it will automaticly recognise python code and list Symbols in a side bar, allowing to jump quickly in your code.
+
[http://www.geany.org/ Geany] is a nice development Editor. One feature I like is that it will automaticly recognise python code and list Symbols in a side bar, allowing to jump quickly in your code.
 +
Install it and you can start coding !
  
Install it and you can start coding !
+
Note, you can also get [http://wiki.geany.org/howtos/pydocw instant documentation for python modules].
  
 
=== SPE ===
 
=== SPE ===
SPE or Stani's python editor, is a python editor. It is somewhat more powerfull than Erik4 (quick access to code fragments, extensive search, ...) but can be unstable on some setups. Try it to know.
+
[http://pythonide.stani.be/ SPE] or Stani's python editor, is a python editor. It is somewhat more powerfull than Erik4 (quick access to code fragments, extensive search, ...) but can be unstable on some setups. Try it to know.
  
 +
=== Scribes ===
 +
[http://scribes.sourceforge.net Scribes] is a text editor written in python and Gtk, that uniquely blends simplicity with well researched powerful functions.
  
 
=== Other ===
 
=== Other ===
  
"Kate" works well as a general editor for Python. It also recognises key words of Python and marks them in colours. Kate is a Linux KDE desktop program.  Of course, it also works on gnome installations.
+
[http://kate-editor.org/ Kate] works well as a general editor for Python. It also recognizes key words of Python and marks them in colours. Kate is a Linux KDE desktop program.  Of course, it also works on gnome installations.
  
"Idle" is a handy simple editor that takes advantage of the interpreter features of Python. Often Idle comes with Python packages. Idle works well in Linux and other OS's, including the "dominant OS". If you install Windows version of Python, you will probably install from the same package Idle. One feature of Idle tends to confuse newcomers: Idle main window is NOT used for program writing, but for displaying the results. Notice that there is a Python tutorial, automagically installed with Idle on a Windows box. It is worth noting that the Tutorial gives quite extensive introduction into Python and is authored by the originator of Python Guido van Rossum.
+
'''Idle''' is a handy simple editor that takes advantage of the interpreter features of Python. Often Idle comes with Python packages. Idle works well in Linux and other OS's, including the "dominant OS". If you install Windows version of Python, you will probably install from the same package Idle. One feature of Idle tends to confuse newcomers: Idle main window is NOT used for program writing, but for displaying the results. Notice that there is a Python tutorial, automagically installed with Idle on a Windows box. It is worth noting that the Tutorial gives quite extensive introduction into Python and is authored by the originator of Python: Guido van Rossum.
  
 
(If you have a favourite Editor and want to share it : describe how to set it up here.)
 
(If you have a favourite Editor and want to share it : describe how to set it up here.)
  
== Run GRAMPS from the source ==
+
== Get the source tree ==
To test that you did all well, you may want to run GRAMPS from your downloaded svn tree. This is explained in the [[Brief introduction to SVN]] but here are the quick steps :
+
To get the source tree, you will need Git. Please have a look at the dedicated tutorial [[Brief introduction to Git]] for details.
cd ~/gramps-trunk
+
 
./autogen.sh
+
You can also use a graphical Git tool like "gitk" or "git-gui".
make
+
 
python src/gramps.py
+
'''This tutorial now assumes you have cloned the Gramps repository into a directory called "~/Gramps". If not, you have to change this path when it is used below.'''
  
= Browse the source code =
+
{{man warn|Warning:|Let it be clear that the settings directory <code>"~/.gramps/"</code> is a '''different''' hidden directory in your home-dir. Do not store anything there.''}}
== data ==
+
 
You will find here various data files used by gramps : manpages, icons...
+
== Run Gramps from the source ==
 +
To test that you did all well, you may want to run Gramps from your downloaded Git tree. This is explained in the [[Running a development version of Gramps]]; here are the quick steps:
 +
 
 +
For the internationalization code to work, you need to have the translation tools.
 +
 
 +
On Debian, just run (as root) - ('''Only if Debian installs Gramps 4.0+ as Gramps version!):
 +
apt-get build-dep gramps
 +
 
 +
On Fedora 20+, you will need:
 +
yum install intltool gettext git-core rcs
 +
 
 +
Build Gramps with:
 +
cd ~/Gramps
 +
python setup.py build
 +
 
 +
To run Gramps, type:
 +
python Gramps.py
 +
 
 +
== Correct Translation in development ==
  
== src ==
+
'''To check if following is still current!'''
In this folder, you will find GRAMPS' source code. There are a lot of subfolders, which are explained in the folowing sections.
+
Warning: you will not be able to load translations on /usr/local/share/locale, because you will load /usr/share/locale, which could be translations for stable release (set on grampsapp.py).
 +
You may generate a custom launcher by adding this line:
 +
export GRAMPSI18N=/usr/local/share/locale
 +
if you want to use an other path, you may add this line:
 +
export GRAMPSI18N=@prefix@/share/locale
 +
on current gramps.sh.in (source file) before installation.
  
In most folders, there is an __init.py__ file. You may find some explanations there about the package.
+
= Browse the source code =
  
=== src/gen ===
+
* For further information see: [[Gramps 4.x File Organization|Gramps 4.x File Layout Organization]]
This is GRAMPS' core. It defines database classes (Person, Place, Note...), database access :
 
* '''src/gen/db''' : GRAMPS Database Handling
 
* '''src/gen/lib''' : The core library of GRAMPS objects
 
* '''src/gen/proxy''' : Proxy class for the GRAMPS databases. This is a very powerful tool used to propose a filtered view of the database : Objects which are not marked private, (not) living persons...
 
* '''src/gen/utils''' : Common utilities for GRAMPS code (progess monitor dialog, database utilities, callbacks between UI and database code)
 
  
=== other ===
+
= Develop =
* src/BasicUtils : Basic functions to be called from other Gramps code
+
Before you start developing, read
* src/Config : This package implements access to GRAMPS configuration. It provides the choice between different storage backends.
+
* [[Programming guidelines]]
* src/data : Data for Gramps ('''What is the difference with the root data folder ?''')
+
* [[UI style]]
* src/DataViews : Gramps Main Views (PersonView, FamilyList...)
+
* [[Brief introduction to Git]]
* src/DateHandler : Class handling language-specific selection for date parser and displayer.
+
* [[Using database API]]
* src/DisplayModels : ??
+
* [http://www.gramps-project.org/docs/ API Code Documentation] - Gramps master
* src/DisplayTabs : ??
+
* [[Devhelp]]
* src/docgen: Gramps Document Generator (for reports)
+
* [[Committing policies]]
* src/Editors: Editors for the different Gramps Objects (Person, Place...)
 
* src/FilterEditor: Filter Editor
 
* src/Filters: Package providing filtering framework for GRAMPS
 
* src/glade: UI designed with glade. There are few UIs designed with glades. I suppose the other are hard-coded.
 
* src/GrampsDbUtils: This package implements additions to the the GrampsDb database.
 
* src/GrampsLocale: locale workaround for some OSes
 
* src/GrampsLogger: This package implements some extensions to the standard Python logging module that support a consistent logging and bug reporting framework for Gramps.
 
* src/images: images for Gramps.
 
* src/Merge: Merge functions
 
* src/Mime: Mime types handling
 
* src/Models
 
* src/plugins
 
** src/plugins/docgen
 
** src/plugins/drawreport
 
** src/plugins/export
 
** src/plugins/gramplet
 
** src/plugins/graph
 
** src/plugins/lib
 
** src/plugins/mapservices
 
** src/plugins/quickview
 
** src/plugins/rel
 
** src/plugins/textreport
 
** src/plugins/tool
 
** src/plugins/webreport
 
* src/PluginUtils
 
* src/ReportBase
 
* src/Selectors
 
* src/Simple: Provides a simplified database access interface to the Gramps database.
 
* src/test
 
* src/widgets
 
  
Further information about files can be found in [[GEPS 008: File Organization]]. Please note that GEPS 008 is a change proposal and does not reflect the actual source tree.
 
  
 
[[Category:Developers/Tutorials]]
 
[[Category:Developers/Tutorials]]
[[Category:Developers/General]]
+
[[Category:Developers/General|G]]

Latest revision as of 17:02, 22 December 2016

Gnome-important.png
Warning:

This tutorial is a work in progress. Feel free to help and modify it.

This tutorial aims to help you in your first hacking of Gramps. It will help you setting up a development environment and explain where to find the files you need.

This tutorial assumes that you are using GNU/Linux (but it might help under another OS) and that you know the basics of Python programming language.

Set up your environment

Optional : set up a development environment

Gnome-important.png
Warning:

It is highly recommended that you do not use your normal/usual environment for developing Gramps.
Definitely do not work on your main Gramps family tree.
Doing so may result in data loss in your Gramps Family Tree !

If you run your development version of Gramps as the usual user, it will show all your usual Gramps family trees, so loading one by mistake is possible and a bug may result in losing productive data. To prevent this, you could use a GRAMPSHOME environment variable to create a separate folder for productive data, see Run Gramps from a portable drive for more information.

Here are some options you may choose to prevent this. If you have enough resources, I recommend using VirtualBox.

VirtualBox

VirtualBox is an open source virtualisation solution. Install it, run it and you have a virtual PC in your PC. Network connection works out of the box without extra configuration needed. Install your favorite Linux distribution and start hacking Gramps in a fully separated environment.

Chroot

You may also use a chroot to result in a similar separation as virtualbox.

If you use Ubuntu, you can set up the chroot environment following these instructions: Creating a basic Ubuntu chroot If you use Gramps in a chroot jail with another Linux distribution, please add information here.

You should then have a working chroot environment in /var/chroot (or whichever location you chose). Enter it with

sudo chroot /var/chroot 

This means that within this directory, applications cannot access files without the chroot jail, i.e. your Gramps install within the directory cannot destroy another install of Gramps in your usual home directory.

From a shell within your chroot directory, just clone the Git repository into the chroot folder as usual. Please note that before running the autogen-Script for generating makefiles, you may need to get some packages:

apt-get install python intltool libglib2.0-dev gedit

Another user

You may also simply do your development as another user, so you won't access your usual ~/.gramps database when testing.

You can also create an alias account with the same user and group IDs, but with a different login name and different home directory, typically, a subdir of the real user's home directory. This gives the benefit of less disk usage, and no permission boundary between the two account aliases. On the other hand, if you are afraid of malicious code within gramps purposefully breaking out and wreaking havoc on your real home account's .gramps, this method is too weak for you. For regular development scenario, though, this setup certainly does suffice.

This is what the cloning looks like in my /etc/passwd:

vassilii:x:1000:1000:Vassilii Khachaturov,,,:/home/vassilii:/bin/bash
v:x:1000:1000:Vassilii Khachaturov,,,:/home/vassilii/pub:/bin/bash

Create symlink to the dotfiles you want to reuse. Obviously, don't do this for .gramps! Something like (inside ~vassilii/pub):

ln -s ../.bashrc ../.mozilla ../.ratpoisonrc ../.gitconfig .

You can use the alias account in a standalone matter (X session under it), or just inside a terminal window (su - <name of the alias account>). All the build, install, and test run of gramps should be done under this account. This will preserve your normal account's .gramps.

Having obtained the gramps source tree, as the first build step, do

./autogen.sh -- --prefix=/home/vassilii/pub/local

(replace /home/vassilii/pub/ with the actual aliased home directory!!!)

After you build and install (no root needed! you install under the local prefix), check that the right (locally built) gramps is on your PATH. Tweak your shell profiles as needed.

None of above

Gnome-important.png
You have been warned!

At a minimum name your test family trees 'a_test_name'. By starting with 'a_test' they will show at the top of the Family Tree manager, and the word test makes it clear what they are created for.

Mac OS X

In order to develop (or even use) Gramps on an Apple Macintosh, you must first install all of the prerequisite libraries and their headers. There are three choices for this Gtk-OSX, MacPorts, or Fink. Full instructions for building Gramps for each is provided here: Mac OS X:Build from source:Application package, Mac OS X:Build from source:MacPorts, or Mac OS X:Build from source:fink. The last only works with X11, which is no longer included in OS X but can be installed separately. MacPorts can be built with/for either X11 or OS X's native Quartz graphics backend, and Gtk-OSX is exclusively for Quartz.

Install a text editor

Whichever editor you use, make sure that it is set up so that the indent level is 4 spaces. Do not use the Tab character to indent.

The following is in alphabetic order. Choose the one you like.

Eclipse + PyDev

Eclipse with PyDev brings an integrated IDE for Python. To run it, you have to do a few steps configuration:

  • First, you have to set the path to your python interpreter:
    • Go in the menu Window > Preferences...;
    • Then choose PyDev > Interpreters > Python Interpreter.
    • Click New... to create a link to your Python executable (for example /usr/bin/python3.5).
  • Next, you have to set up a PyDev project:
    • Go in the menu File > New > Project...;
    • Choose PyDev Project
    • Project name could be Gramps
    • Uncheck Use defaults and choose ~/gramps-trunk as the project directory.
    • Project type is Python 3.5
    • Interpreter is the one you created at the first step above
    • And then you can press Finish.

You are now ready to start coding!

pycharm

PyCharm is more powerful and out-of-the-box than Eclipse with pydev, although it is not Free Software like Eclipse is. Seems to be recognizing more Python syntax and feels faster on my box. I unpacked the distribution, launched bin/pycharm.sh script, and it just worked. 'File » Open Directory' and selected the "Gramps/src" directory in my local checked out Git WD, and things work from there.

'Version Control » Update Project' automatically syncs up with the Git repository.

Emacs or Vim

Experienced Unix-like users and developers will often use one of these editors. They're available with virtually all distributions of modern Unix-like systems.

Eric4

Eric4 is a python editor. It has everything you need (code completion, python shell, ...)

Geany

Geany is a nice development Editor. One feature I like is that it will automaticly recognise python code and list Symbols in a side bar, allowing to jump quickly in your code. Install it and you can start coding !

Note, you can also get instant documentation for python modules.

SPE

SPE or Stani's python editor, is a python editor. It is somewhat more powerfull than Erik4 (quick access to code fragments, extensive search, ...) but can be unstable on some setups. Try it to know.

Scribes

Scribes is a text editor written in python and Gtk, that uniquely blends simplicity with well researched powerful functions.

Other

Kate works well as a general editor for Python. It also recognizes key words of Python and marks them in colours. Kate is a Linux KDE desktop program. Of course, it also works on gnome installations.

Idle is a handy simple editor that takes advantage of the interpreter features of Python. Often Idle comes with Python packages. Idle works well in Linux and other OS's, including the "dominant OS". If you install Windows version of Python, you will probably install from the same package Idle. One feature of Idle tends to confuse newcomers: Idle main window is NOT used for program writing, but for displaying the results. Notice that there is a Python tutorial, automagically installed with Idle on a Windows box. It is worth noting that the Tutorial gives quite extensive introduction into Python and is authored by the originator of Python: Guido van Rossum.

(If you have a favourite Editor and want to share it : describe how to set it up here.)

Get the source tree

To get the source tree, you will need Git. Please have a look at the dedicated tutorial Brief introduction to Git for details.

You can also use a graphical Git tool like "gitk" or "git-gui".

This tutorial now assumes you have cloned the Gramps repository into a directory called "~/Gramps". If not, you have to change this path when it is used below.

Gnome-important.png
Warning:

Let it be clear that the settings directory "~/.gramps/" is a different hidden directory in your home-dir. Do not store anything there.

Run Gramps from the source

To test that you did all well, you may want to run Gramps from your downloaded Git tree. This is explained in the Running a development version of Gramps; here are the quick steps:

For the internationalization code to work, you need to have the translation tools.

On Debian, just run (as root) - (Only if Debian installs Gramps 4.0+ as Gramps version!):

apt-get build-dep gramps

On Fedora 20+, you will need:

yum install intltool gettext git-core rcs

Build Gramps with:

cd ~/Gramps
python setup.py build

To run Gramps, type:

python Gramps.py

Correct Translation in development

To check if following is still current! Warning: you will not be able to load translations on /usr/local/share/locale, because you will load /usr/share/locale, which could be translations for stable release (set on grampsapp.py). You may generate a custom launcher by adding this line:

export GRAMPSI18N=/usr/local/share/locale

if you want to use an other path, you may add this line:

export GRAMPSI18N=@prefix@/share/locale

on current gramps.sh.in (source file) before installation.

Browse the source code

Develop

Before you start developing, read