Hello. I'm a software developer and try to fix some disturbing problems in Gramps. Unfortunately there's more to Free Software than meets the eye so patches often get relegated since I'm not an official Gramps developer. I'll post the links to my bug reports with patches here so that perhaps it can help someone. Additionally I'll post links to patches which make Gramps better for me but do not classify as bug fixes. Hopefully they'll make it better for you too. If you want to try these patches bear in mind they're "Third-party patches". You might need to create an account in the bug tracker so you can download them which is not complicated. The patches are for Gramps Trunk but should apply with some fuzz to any problematic or recent version.

+

Hello. I'm a software developer and try to fix some disturbing problems in Gramps. Unfortunately there's more to Free Software than meets the eye so patches often get relegated since I'm not an official Gramps developer. I'll post the links to my bug reports with patches here so that perhaps it can help someone. I'll also post links to patches which make Gramps better for me but do not classify as bug fixes. Hopefully they'll make it better for you too. If you want to try these patches bear in mind they're "Third-party patches". You might need to create an account in the bug tracker so you can download them which is not complicated. The patches are or were for Gramps Trunk, generally Gramps 3.2-3.3 or more recent, but should apply with some fuzz to any problematic or correspondent version. I'm interested in the plugins/textreport Gramps subsystem.

−

Note: many of the patches have eventually been accepted and applied to Gramps. I'm leaving them here anyway. Be sure to check whether your version of Gramps does not already offer the correspondent functionality.

+

Note(a): Many of the patches listed here have eventually been accepted and applied to Gramps. Be sure to check whether your version of Gramps does not already offer the correspondent functionality.

+

+

Note(b): For a discussion on attempting to apply patches on the Windows platform, see this discussion on the GRAMPS - Windows mailing list: http://gramps.1791082.n4.nabble.com/Fwd-Re-How-to-install-patch-td3206174.html .

__TOC__

__TOC__

Line 7:

Line 9:

== Third-party patches ==

== Third-party patches ==

=== Bug fixes ===

=== Bug fixes ===

−

* Fix for weird parentheses in the Descendant Report: http://www.gramps-project.org/bugs/view.php?id=3255

Gramps' Detailed Descendant Report was already quite complete but there was a point in which it deviated from classic descendancy reports. The descendant numbers in the child list were put to the right of their name which made it uneven. The patch in the link below fixed this putting child numbers at the far left as most descendant reports do.

Gramps' Detailed Descendant Report was already quite complete but there was a point in which it deviated from classic descendancy reports. The descendant numbers in the child list were put to the right of their name which made it uneven. The patch in the link below fixed this putting child numbers at the far left as most descendant reports do.

If you'd like to change the default family relationship type from "Unknown" to "Married" in Gramps, do the following. Exit Gramps, edit the file src/gen/lib/familyreltype.py in your Gramps source code directory (you may need to be root) and change the penultimate line from

In sequence of the patch for by-branch structure for the text Detailed Descendant Report, this patch adds a simple numbering option to said report, as used by Pedro Taques de Almeida Paes Leme in Nobiliarchia Paulistana, Genealogia das Principaes Familias de S. Paulo with by-branch style.

+

* {{bug|5503}}

+

+

==== Changing the default family relationship type from "Unknown" to "Married" in Gramps (as of March 2010) ====

+

If you'd like to change the default family relationship type from "Unknown" to "Married" in Gramps, as of March 2010, do the following. Exit Gramps, edit the file src/gen/lib/familyreltype.py in your Gramps source code directory (you may need to be root) and change the penultimate line from

value = self.UNKNOWN

value = self.UNKNOWN

Line 44:

Line 60:

then restart Gramps.

then restart Gramps.

+

+

== Third-party plugins ==

+

The plugins I have written for Gramps are available as addons at the gramps-addons repository,

Latest revision as of 18:06, 15 February 2012

Hello. I'm a software developer and try to fix some disturbing problems in Gramps. Unfortunately there's more to Free Software than meets the eye so patches often get relegated since I'm not an official Gramps developer. I'll post the links to my bug reports with patches here so that perhaps it can help someone. I'll also post links to patches which make Gramps better for me but do not classify as bug fixes. Hopefully they'll make it better for you too. If you want to try these patches bear in mind they're "Third-party patches". You might need to create an account in the bug tracker so you can download them which is not complicated. The patches are or were for Gramps Trunk, generally Gramps 3.2-3.3 or more recent, but should apply with some fuzz to any problematic or correspondent version. I'm interested in the plugins/textreport Gramps subsystem.

Note(a): Many of the patches listed here have eventually been accepted and applied to Gramps. Be sure to check whether your version of Gramps does not already offer the correspondent functionality.

Other

Gramps' Detailed Descendant Report was already quite complete but there was a point in which it deviated from classic descendancy reports. The descendant numbers in the child list were put to the right of their name which made it uneven. The patch in the link below fixed this putting child numbers at the far left as most descendant reports do.

In sequence of the patch for by-branch structure for the text Detailed Descendant Report, this patch adds a simple numbering option to said report, as used by Pedro Taques de Almeida Paes Leme in Nobiliarchia Paulistana, Genealogia das Principaes Familias de S. Paulo with by-branch style.

Changing the default family relationship type from "Unknown" to "Married" in Gramps (as of March 2010)

If you'd like to change the default family relationship type from "Unknown" to "Married" in Gramps, as of March 2010, do the following. Exit Gramps, edit the file src/gen/lib/familyreltype.py in your Gramps source code directory (you may need to be root) and change the penultimate line from

value = self.UNKNOWN

to

value = self.MARRIED

then restart Gramps.

Third-party plugins

The plugins I have written for Gramps are available as addons at the gramps-addons repository,