@hamkg
The hardest part (adapting the abbreviated name display) was done about 3 weeks ago, and the changes worked with 6.0 at that time. They are not public yet. Hopefully I’ll find time this weekend to release the addon for 6.0.
There was no release version yet, so all versions of FTV should be considered pre-release and somewhat unstable. I’ll let you know when I release the addon for Gramps 6.0.
@Nick-Hall When this is done: I had no success using fpath. My experience was that this is overwritten. Whatever is in the .gpr.py file is discarded and a default path is used.
The fpath attribute is used in the import_plugin method of the plugin manager. It is only used on Windows and the path is only set when an addon is imported. The change is not permanent.
I’m in no rush to upgrade to Gramps 6.0 but I will get there in due course. Most likely after the first maintenance release. Meanwhile, given that Gramps 6.0 is the future, will you continue to develop FTV for Gramps 5.2? What I mean is, supporting two versions will be a lot of work and since FTV is still pre-release is there any point in carrying on with FTV for Gramps 5.2?
I’ve thought about this as well. I think I won’t add new features for both versions because of the extra work and testing on my part. If I continue to work only based on one Gramps version, it makes more sense to continue to implement new features in the 6.0 version, to reduce the potential work of porting those changes from 5.2 to 6.0 later when the version switch for the addon is made. From a user perspective: If I wait to switch to 6.0, users who switch Gramps version earlier will not be able to use FTV at all. If I switch early, everyone will be able to use FTV (while those using 6.0 will get new features).
Since I don’t know how fast people update Gramps (more precisely, how fast FTV users update Gramps*), it’s hard to find the best time, but it seems like switching FTV to 6.0 earlier is the lesser of two evils.
* I don’t even know how many people use FTV at all. There were a lot of comments on the forum in the weeks after the first beta was published/announced, but it slowed down.
I wonder if GitHub has an option to measure the rate that the addons-xx.json are touched?
There would be a lot of repeats from the same IPs but it would hint at the volume of active users. And measuring the surge when you do a 6.0 curated project listing would be informative too.
I tried to find an api for raw.githubusercontent.com statistics, but I couldn’t find one. If anyone knows of an endpoint for specific files, let me know!
I’d like to give a small update of the changes that have not yet been discussed in this thread (as of v0.1.118):
I improved the translatability of FTV and started a separate topic to organize the preparation and testing of the translation workflow of FTV. Currently I’m waiting for a PR with a few translated labes/strings to test the next step in the workflow.
There is now a config option for whether you want to highlight the home person. (By default, Gramps uses a green background for the home person.) In previous versions, the home person was always highlighted.
A gallery was added to the person panel.
Improved tag placement for multiple tags.
PRs #37 and #35 were merged to fix bugs in the panel timeline. Many thanks to @TJB!
#37 fixes the timeline when events are hidden due to options in the config dialog
#35 introduces escaping special characters in the timeline (since markup (bold) is used there, some special characters need to be escaped)
Small fixes, e.g. grandparents were not aligned correctly in some cases.
FamilyTreeView is now available for Gramps 6.0 (FTV v0.1.120). Please note that the addon should not be considered stable yet. Back up your data before and while using this addon!
New features will only be available for FTV when used with Gramps 6.0, but you can still download the version for Gramps 5.2 using the old URL.
In order to make the addon work with Gramps 6.0, some major changes to the abbreviated name display and some minor changes to the panel gramplet were required. Please let me know if you find any new bugs in FTV.
Hello. Just a small issue on Gramps 6.0 : there is still a dependency on the “Themes” add-on, which I thought had been corrected for Gramps 5.2 (I didn’t re-check).
If it is not installed, FTV can’t start.
@Bouscram
Thanks for reporting this. It seems that ConfigManager.is_key() and ConfigManager._validate_section_and_setting() only check ConfigManager.data, but don’t check ConfigManager.callbacks, so ConfigManager.connect can fail in edge cases. I wrapped a try … except block around the calls to the connect method.
I don’t think this is a new bug, but it’s just surfacing now that edge cases are more likely due to many new installations.
Can you try FTV v0.1.121 and report back? If it still doesn’t work, could you open a GitHub issue?
I already have FTV 0.1.121 installed, I spotted the issue with it while trying to identify the source of the issue I have with launching Gramps from the Mac Finder…