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

Development
,
51

There are a variety of minor tweaks that would make Gramps more friendly. Things that (probably) do not require significant code. Where do they fit in this discussion?

Dashboard

  1. replace the TopSurnames default dashboard gramplets
  2. Three column layout instead of 2 column. (With an empty center column to whet curiosity about why it is empty and invite a place to add a gramplet.)

Geography:

  1. Rename view modes so that more than 3 labeled ones will fit on the Toolbar. (Probably needs consensus about verbiage.) Possible options:

    • Personal tracks All known places for one Person
    • Family tracks All known places for one Family
    • Descendant tracks Every residence or move for person and their descendants
    • Family proximity Would these two families been able to meet?
    • Personal proximity Would they been able to meet?
    • Plottable All known Places—coordinate-ready for plotting
    • Event places All places related to Event Place

  2. During install, add a Gramps User Directory maps/fallback set of custom map tiles (for levels 1-4 only, approx. 2mb) and set the (existing but underdocumented) custom tiles provider to use them.
    This would eliminate the Internet connection dependence for the initial content in the view. And we could evolve the tiles to have ‘hints’ about making a Place with Coordinates and an Event.

  3. swap in the new (more meanful) map pins by @bjpcorp
          image

Charts

  1. either: hide the Category’s empty sidebar and bottombar by default; or, add a default gramplet for each (maybe “Pedigree”, “Relatives” for the sidebar. And “What’s Next?” for bottombar)

Navigator sidebar

  1. select a primary sidebar and demote the other 2 built-ins to being addon “sidebar” plugins. This eliminates the (overly large) mode selector by default.
    • Category current default
    • Drop-down
      (my preferred. It requires the least screen width while having fully labeled view modes in the menus. Good for both power users and newbies)
    • Expander

Feedback

  1. reword the Error Processing Arguments error message about a locked database on the post-crash restart.

More intuitive file locations during install

  1. install the sample data in user writable space instead of write-protected core directories. (Including the gramps/example/csv, gramps/example/gedcom, gramps/example/gramps data/tips.xml) to a example folder in the USER_PLUGINS folder. (Allows revising these files with the Addon Manager.)
  2. set an application-specific Gtk File Chooser Shortcut button to the examples folder path. (addresses #11623)
  3. The use of the USER_CSS directory is unclear. Add a dummy gramps_user.css (or whatever filename will be the topmost CSS layer above data/gramps.css) to that folder during installation.