Frontend for Gramps Web
Happy 2024!
The first new release of the year mainly improves the data entry workflow. So far, creating a new person and adding a source citation to it required two separate steps: first creating the person and then opening edit mode and associating the citation. This can be cumbersome when adding a large number of new objects; moreover, good genealogy practice means no objects should be added without corresponding source.
The following improvements have been made to the forms for adding new objects:
In addition and as usual, translations have been updated by the diligent Weblate community.
The last release of 2023 contains one new feature: every object can now be bookmarked and accessed quickly via the new bookmarks view. Bookmarks are stored in the user's browser, so edit rights are not necessary to create or delete bookmarks and they are completely private.
Happy new year to all users of Gramps Web! :tada:
This version :christmas_tree: brings another great addition to the chart section: an hourglass chart :hourglass: showing both ancestors and descendants of the person in question. In both directions, the number of generations can be configured and, just like for the ancestor and descendant charts improved in the last release, the chart can be zoomed and panned with mouse or touch gestures. Thanks to @geostag for the implementation!
In addition, translations for Danish, Norwegian, and Ukrainian have been updated. Thanks to the translators!
This first release in November 2023 brings a brand new feature: text recognition in media files directly from Gramps Web!
For any image containing printed text, e.g. the photo of a page in a book, click the "Text Recognition" button in the media object view to run optical character recognition (OCR) powered by Tesseract and display the resulting text. For users with editing permissions, a button allows directly saving the recognized text as media note.
The DNA tab in the person view now shows a table of matches with the number of shared segments, the total size of shared DNA and the size of the largest shared segment. This feature was motivated by the analogous DNA match Gramplet that is in development.
Translations have been updated for numerous languages. Thanks to the Weblate community!
This third release in October fixes a minor bug with the new descendant tree view and updates translations for several languages.
The second release in October brings several new features and one bug fix.
In addition to the ancestor tree and fan chart views, there is now a third chart view: the descant tree! Just like the ancestor tree, the number of generations displayed can be adjusted and the tree is scaled when it doesn't fit on the screen anymore.
So far, the type of an event or of a place could only be chosen when creating the object, but not edited afterwards. Now, both properties can be edited from the UI.
This is the first release in October and it brings a couple of improvements and fixes.
Previously, event roles could only be chosen on event creation, but the proper default ("Primary" for people, "Family" for families) was not preselected. The proper default is now preselected, plus it is now possible to edit an existing event reference's role.
Name suffixes were ignored in most parts of the UI so far (#284). This is now fixed and the display of names has been unified; it should also more properly handle the display of names with multiple surnames or connectors.
The main new feature in this third release in September is a DNA segment map view based on Gramps' DNA segment map Gramplet addon. As for the Gramplet, matching DNA segment data is stored in notes attached to an association between two people, or to a citation of an association.
The segment map can be accessed through the "DNA" tab in the person view.
When editing associations (possible since the last release), it is now also possible to add or edit citations or notes of the association. This allows adding the DNA segment data directly from Gramps Web.
Finally, missing form validation was added to several forms to prevent introducing inconsistencies into the database (#282).
This second release in September brings a couple of smaller improvements: