What do/did you find to be the most complicated parts of Gramps?

Development
,
110

I think we need a consensus on this.

The Example.tree is far from “small” and has a lot of wonky data in it. (For triggering problematic conditions and to demonstrate solutions/workarounds.)

Number of new objects imported:
    People: 2157
    Families: 762
    Sources: 4
    Events: 3432
    Media Objects: 7
    Places: 1294
    Repositories: 3
    Notes: 19
    Tags: 2
    Citations: 2854

Also the pre-installed database included in the install will be vulnerable. Easily deleted or changed. Before a suggestion appears to have 2 copies of the database (one as a SQLite fileset and a .gramps in the Examples), that creates more unproductive synchronization maintenance work. And before the suggestion that it could just be the .gramps file version and imported as part of the 1st run, that import of the Example.gramps is slooow and would add dialogs (a progress dialog and 2 modal dialogs: a fail/success report and Import Statistic) to the 1st run.

I know that this next will initially seem like arguing against myself. But bear with me…
The Example.gramps is only the “most-well-known” of several importable files bundled with Gramps. (There is a CSV, a GEDCOM, and 2 Gramps files) And data.gramps was recently selected for expanding the DNA examples because the other example file is already inappropriate. (Too many disconnected people and not a sufficiently broad/deep network of DNA related people to paint with DNA data samples. You cannot visualize the nodal network of Example.gramps. It would be giving up on the 3 lesser examples by making the main example.gramps (which is cited everywhere) into a brain-dead import.

Also, by slapping a patch over 1 problem for Examples, we are too likely to say to ourselves that Examples have received attention and we can ignore them again for awhile. And that would obscure the larger problems: Examples are buried in the install and not easily updated; relative paths for media for imports are broken (why does that constant name appear sometimes after import); the Gtk File Selector needs default bookmark and shortcut management features for reduce clicks in navigation. And we have tons of ‘changes’ for the example.gramps that seem to have no way to become included in the bundles.

Example.gramps visualization in yEd. From Graphviz Export - Wish for Feature - #14 by GeorgeWilmes :

Gramps "example" data in yEd
Gramps "example" data in yEd1244×846 458 KB

And what is more important, the Example.gramps is not appropriate for a newbie exploring independently… it requires guided exploration. Default inclusion would create the opposite problem of what we are addressing: instead of a scarcity of tree data, it becomes overwhelming. Because there is so much ‘stuff’ stuffed in it.

A tiny twig can easily be FULLY explored… even by a casual guest. And 4 people is small enough to ‘adapt’ as a starting point for your family.