That is why you put the addon out for testing. Nothing compares to how real users put their real data through the view’s options and its results.
@DaveSch
I’ve just created a new version (v0.1.22) in which I’ve rewritten some parts of the abbreviation algorithm. It should be more flexible now and the problem with parentheses, quotes and commas should no longer appear.
Some problems remain when there are other special characters like ?
in the name that are not specially handled by Gramps (like ""
, ()
and ,
). These cases need to be handled somehow but I will probably do this after the enhancements @emyoulation mentioned are released, depending on when that happens.
I’ve also improved the abbreviation inspector Gramplet. It now shows more information for debugging (keep in mind that this Gramplet is made for debugging, not for regular users).
Feel free to attach a screenshot of this Gramplet if there is a problem that is difficult to explain or that may be difficult to reproduce on my end.
@emyoulation
Unfortunately I was not able to find the Import Text Gramplet in the Addon Manager or the Plugin Manager, but I think I have entered all parts of the name of the example person correctly.
@geoglorus
Thanks for offering your help. I’m not sure how translating addons works yet. I’ll let you know as soon as I know how to proceed.
Something else I was thinking about: Since this addon is currently in development, there will probably be a lot of strings to change/add/remove, so it makes more sense to wait until it is reaches a sufficiently stable state, not only in terms of functionality, but also in terms of the interface and the set of strings to be translated.
I understand your opinion. I had thought that even a partial translation would allow non-English-speaking users to use your gramplet and therefore potentially give you fsome eedback to improve it. Don’t hesitate to get back to me when I can help you.
Working great. No more blank quotes.
I implemented the alternative distance calculation a few days ago and made it an “experimental” option.
@Woody has tested this option successfully. I would like to get a confirmation from at least one other user before making this new calculation method permanent and removing the experimental option.
Does anyone have experience with this option and can confirm that it works?
Or, can someone else please test the adaptive distance option to confirm that it works?
In the Badges config you can select to show “Number of families”.
I think it would be smart (user friendly and intuitive) to show a pop-up with the spouses, when clicking this badge, and in this way be able to choose which spouse and children to show in the graph.
Sometimes I have difficulties closing the “Info box”, I need to click a lot of times outside the info box to close it. This might be platform dependent (Mac Ventura).
Perhaps [Escape] would be an easy way to close the info box?
Thanks for the feedback. I really like the idea of being able to select the family to show if there are multiple families for the active person or descendants.
But this particular badge is not meant to be used by everyone and those who don’t want to use the badge would not have that option. Linking this particular badge to changing the structure of the tree is not ideal. I think the better solution is to add some kind of button next to the person box or an item to the context menu (which will be added in the future) to select a different family/spouse. As explained in another comment above, I also want to make it possible to show (expand) the other families/spouses so that they are all visible at once.
@csam
I’ve never experienced this and I don’t have a MacOS machine to test it on. Just to make sure there is no misunderstanding, since you replied to my comment about the experimental adaptive generation distance: Does this only happen when this option is turned on and never when it is turned off? This option should have no effect on the info box, so I would be very surprised if there is a connection.
In any case, I kindly ask you to open a new issue on GitHub to investigate this.
That seems like a reasonable idea. At the moment I haven’t looked at the tree’s canvas getting keyboard focus (e.g. to use shortcuts and arrows to navigate), so it’s not trivial at the moment, but I’ll add it to my list.
@ztlxltl Like @DaveSch I people that have married more than once but these subsequent marriages (and associated children) are not shown. This is a severe limitation for me. Is fixing this on the ‘to do’ list?
@stuck
Thanks for letting me know what your critical missing feature is. It is definitely on my TODO list. Unfortunately, I’m not satisfied with the current idea regarding the visualization. Since now you as well expressed interest in an early implementation (“severe limitation”) of this, I’ll try to look into this as soon as possible with the current visualization I have in mind, then everyone can give feedback on the visualization to further improve it.
Thanks but please don’t shoehorn a fix into the current visualisation, at the expense of a superior version you are still trying to figure out, just for my sake. I’m only someone who dabbles with Gramps.
When I said ‘severe limitation’ what I should have said was because my line descends from a second marriage it means I can’t navigate from my brick wall ancestor at the top down the tree to me at the bottom. However if I start with me, I can navigate up to the root. That asymmetry feels odd and so despite the fact the current GraphView addon refuses to display children in birth order that view works better for me.
Meanwhile, knowing it is on a ‘to do’ list is fine.
Understood! I will think about the current visualization idea but I’m not sure if I have any other ideas. Maybe I will implement the best idea I come up with and ask for feedback and other ideas.
The visualization will also be kind of optional as it can be expanded and collapsed (ideally the default (visible or hidden) is configurable), so everyone can also hide (collapse) it if they don’t like it for the time being.
My TODO list is quite long. While I focus on the requested items, I also work on what I feel like doing at the moment. But I also think it’s a good idea to get feedback early on those items where I’m not happy with that I can come up with on my own. We will see when I have something to discuss.
I’ve implemented the visualization I had in mind. It’s not expandable/collapsible yet, so I haven’t published it yet. You will not see other families in your tree yet. As I wrote in a previous comment, this is a compromise and I’m not 100% happy with the visualization.
Below I’ve summarized some principles I used as a basis for the design of FTV, and my viewpoints on how they apply to multiple/other families of a person.
-
Since the box of a family spans the width of two people and has a “reserved space” above it for each spouse, if a spouse is visualized at another family, that space remains empty. On the one hand, I think it would be confusing to have a copy of that person at every family. On the other hand, the empty space breaks the pattern a bit. I don’t know if a grayed out or opaque copy of the person would have any advantage. Reducing the size of the family box where a spouse is somewhere else would break the pattern a bit (the pattern braking of the empty space would decrease). If it is reduced too much, the intended “reserved space” might also disappear, which is also related to the next point.
-
I also want to keep the rule that spouse 1 (father) is always on the right and spouse 2 (mother) is always on the left. Unfortunately, this causes the two lines to cross.
-
I could increase the vertical space between the people and the families to make more room for the horizontal line going to the other family, but this would result in a looser connection of the three boxes of a family and two spouses. Note that the size of the gap between the spouses and the size of the gap above each family box are the same. I think this is a nice visualization that I think I don’t want to sacrifice.
When badges are activated for families, the line is partially hidden. Since the placement and size of badges are not yet fixed, I do not want to make this a central point of the discussion.
Don’t let the list of my points of view scare you away from the discussion. If I hear good counter-arguments or alternatives, I am willing to reconsider my viewpoints and change the visualization. You can also upload sketches of alternative ideas.
Here is a screenshot of the current implementation (created with unpublished code):
Looking forward to your feedback, comments and ideas!
Could you update your screen capture in the README.md with one that has badges?
Really nice addition, and looks very similar to how scrolling through the familyTree is done on familysearch, it is pretty intuitive. Great work!
I had some trouble installing on Ubuntu 24.04, missing GooCanvas library. Have made a note about that over here, hope this helps others running on Ubuntu:
Connect the other marriages with horizontal lines like in my (poorly drawn) example. For each additional marriage, just one box for the second partner and below that the box for the marriage is only as big as one box.
Have you looked at the layout of multiple families used by the ‘Interactive Family Tree’ addon?
It draws a single dotted horizontal line, out to the right, from the mid point of the person, and then shows both the common person and the new partner. If there’s a third marriage the horizontal dotted line continues and then again shows the common person and their next partner. These multiple marriages only appear if the person common to them is selected.