Quoting Gregory Orange <gregory.orange@...>:
>> DO BACKUP YOUR DATA FIRST. And don't use .grdb for backup, that doesn't
>> you need to export to .gramps and backup that.
> I'll endeavour to spend some time upgrading to 2.2.7. Thanks for the tip
> about backups - should I generally apply that, or is it safe for me to
> take a second copy of my grdb file for my regular personal backups?
No, it is not save to backup grdb. You find the why on the FAQ on the website,
in short, it is a database, so the file analogy to look at it is wrong. In
future version of gramps (3.0) .grdb will be hidden to avoid this confusion.
>> Concerning the report, check it out in 2.2.7, and make a feature request if
>> needed. You say you can do it yourself with pointers as to where to do
>> do you know python?
> Nope, I grew up on C++ and Java. I'm slowly learning a bit of Perl, and
> very much at home with regex and its friends. I'll hopefully be able to
> muddle my way through some code and make a (presumably) small change
> however, so if someone tells me the right bits of code (and where to get
> source) I'll have a look at that report.
Python is far far far easier than those languages. Forget Perl, it'll
On the website you will find a page on how to obtain the SVN code of
as it says in the INSTALL file, but don't actually install it (so no make
install). You can perfectly run gramps locally, while keeping your official
gramps version for the real work.
You need to look in file gramps2/src/plugins/DescendChart.py
The __init__ method is called first, and gets the options of the
screen. You can
easily add an option there
Then the apply_filter function runs recursively. You see it does
get_person_from_handle to get the present person, prints, then gets all
families of this person, and calls apply_filter for each child.
So, your first problem is: a person can have 3 families, so it is not just one
extra spouse you might want to add. I would suggest a slight variation of the
report: family descendent chart, instead of the present person descendent
You can then start at the beginning with a box for the male and female, then
reuse all functionality of the present report. So something like
__init__ --> calls new apply_filter_family(family_handle)
print person and spouse, go into family and for every child:
--> call apply_filter as in existing report
Should not be much work. The problem is choosing the active family you want
output from. I would suggest you reuse the family select code from the family
view to show a drop down box with all families in your database. You can use
the active family, but people will find that counterintuitive as active family
is only set on the family view so they will wonder how you choose the
print data from.
If you make this, do post a feature request with patch, or offer a third-party
plugin, and add it to
If you finished your plugin, you can drop it in .gramps/plugins, and it
available in your globally installed GRAMPS.
This message was sent using IMP, the Internet Messaging Program.