Want to try out Gramps Connect, the hosted version? This is the first run of the new app, still in development, but making progress since … exactly one month ago today. Happy Birthday Gramps connect!
Go to:
And log into one of the accounts:
Username: editor-1, password: editor-1
Username: editor-2, password: editor-2
Username: editor-3, password: editor-3
Why three different editor accounts? Because you can talk to each other, and plan your research.
What to try on the Gramps Example family tree:
Start a discussion on a gramps person, family, etc.
Try out the fanchart with lifespans
Checkout the Stories, and make a new one on a Person or Family
Edit an object, see its history of edits
Add a “Map overlay” to a place
And much more. What do you like? What don’t you like? Feedback appreciated!
If you want to also try the stand-alone desktop version (very small footprint, same functionality of the hosted version) :
Yes, that was my first thought too The backend gramps-web-api doesn’t yet support that, but the logged in people who have made a change (including replying to a discussion) in the last few minutes will appear as an icon in the top-right corner.
Could you add an option to clipboard the Chat conversation? I will probably want to copy the thread as a worklist in a new Note in whichever Genealogy tool I might be using.
Thank you very much! It looks great.
I love the way you can add places with a little help from wikidata.
There is so much talent in the Gramps team! There are several websolutions though…
I hope you will not spreading your resources too thin.
Grampsweb, Grampsconnect, Greatgramps.
What is the difference between them and should there be a focus, a direction the whole team should be working on?
I hope it is cooperation and not competition.
Thank you, and thanks to those who have already made suggestions!
You are right that Gramps has so much talent, and that we are standing on the shoulders of many decades of developers and users.
I wrote up an overview of the Gramps ecosystem here, noting that projects like greatgramps (static generators) were not included but should be:
There is a huge amount of cooperation because gramps-web and gramps-connect depend on gramps-web-api, and that depends on gramps-core. The hope is that even if we have to twist something to work today, in the future some of that will work its way to benefit the entire ecosystem.
I wouldn’t necessarily say components are in competition, but I will say that we are challenging and pushing the systems to be better. And there is a lot of variety, the spice of life
It looks like (I could be wrong) that wikimedia commons (or wikidata) is trying to block the file caption from 3rd party projects, maybe by guessing that it is an AI bot or something like that. Note, this can also be a bug on this project too as some small versions are displayed on the same notice. One bug report has been filled, which should cover my first impression about this issue. Wikimedia commons seems to make the job, there is maybe rather an issue around these external ressources for properly handling data (thumb) into a project
Anyway, I do not want an internet into a big set of sandboxes, but like for hardcoded url or ark (Archival Resource Key), I dislike the idea of broken online ressources. So, does it makes sense to keep some data “offline” (or local) for gramps-connect, like historical data around maps? A map layer, like on gramps desktop version.
Translated (technical stuff) with the help of an AI:
It is just proposals and documentation (no implementation)
Apart from what the developers can do to cooperate, what we should also emphasize is what the community can do: those that have time to test the different tools that are available in the ecosystem, if there is a feature in one of them that you would like to see in another one of them, please let the devs know by opening a feature request. There are two reasons why this is important:
Developers might not have time to try out “the other” tools as they are busy maintaining their own project.
It’s often easier for users to see the value of a particular feature rather than developers who first think in terms of code changes or architectures.
This looks very promising. And fast.
One feature is missing though : there’s no graphical tree view like in gramps?
(the tab that’s between the “families” & “events” tabs)
There we currently have three types of graphs: tree (hourglass ancestor/descendant), fan chart (with slice by age), and a new one called “Generations”. Generations will show generations of relatives (including step and half siblings)
The backend gramps-web-api doesn’t yet support that, but the logged in people who have made a change (including replying to a discussion) in the last few minutes will appear as an icon in the top-right corner.
