Correct. The publishing will add all translation files.
1 Like
Not sure pointing to a specific version (0.27.16) is the best solution as time goes forward. When the next version comes out, do you have to change the help_url?
1 Like
WIthin gramps, it looks correct. However when it invokes the browser (Brave, a Chrome derivative) it gets mangled. Setting Safari to be the default browser has similar issue.
There is a long long list of console messages, one per entry in the WebURL, I think. And every time I change active person. So much info I cannot tell the wheat from the chaf.
OS version: MacOS Sonoma 14.6.1 (ARM)
Gramps Settings:
gramps : 5.2.1
o.s. : darwin
kernel : 23.6.0
Required:
Python : 3.11.4
Gtk++ : 3.24.38
pygobject : 3.44.1
Cairo : 1.17.8
pycairo : 1.24.0
Pango : 1.50.14
PangoCairo: 1.0
Use pre-existing FamilySearch (records) link:
Use pre-existing Wikipedia link:
1 Like
Its strange, I have no idea what it could be. Tomorrow I will install it to my windows and mas oc to test more.
That branching problem is why I suggested pointing at the parent Repository for the help_url rather than a specific README.md file within the Repository.
Letting GitHub handle the content delivery sidesteps the branch complication. It works … even though there’s all the extra file listing clutter at the top to wade through.
1 Like
Fixed.
It reproduced on my MAC.
Source code: Release v0.31.19 · jurchello/WebSearch · GitHub
What is the next step for WebSearch gramplet? Should I make PR, or add some documentation? Also, does it make sense to request two PRs for 5.2 and 6.0 Gramps versions? Or 6.0 is enough? What about Weblate translations? Should WebSearch appear there automatically?
Thanks.
The official GEDCOM document about EXID types is GEDCOM-registries/uri/exid-types at main · FamilySearch/GEDCOM-registries · GitHub
2 Likes
I’ve added several new links for web search (people and places):
2 Likes
We can “assume” there will be User docs created at the help_url="Addon:WebSearch" I started to convert the GitHub markdown of the README.md to MediaWiki. But realized that it was developer or advanced user content… for creating new linkaging. (Thank you for that. The lack of such documentation was one factors that caused the WebConnect approach to stagnate.) The wiki page can point to the GitHub README.md for developers and keep stay focused on basic usage.
@Nick-Hall
For a cross-version compatible gramplet like this, what is the right way to submit where only the .gpr.py file differs?
Could it include multiple register entries in a single file with different target versions? (Registration attributes for Target version of 4.2, 5.0, 5.1, 5.2, and 6.0 might be the only differences for backwardly compatible addon updates. I am aware of some Windows 32bit users marooned at 5.1 version. I do not know why other users have chosen to not update.)
Could you add a WebSearch Configure option to hide the URL pattern and show the Comment instead?
Eventually, the Configure might add a line editing feature (similar to in the Projects tab of the Addon Manager) or call an external editor for the CSV file.
could you clarify a bit what do you mean?
Url pattern is shown in csv only. And Final url is shown in the treview
Maybe something like this? Its simmplified version of readme.md (AI created it).
WebSearch Gramplet
1. What is it?
WebSearch is a Gramplet for Gramps that allows you to quickly search for information about people, places, and sources in popular genealogy databases. It automatically generates search links based on data from your genealogy records.
When you select a person or place in Gramps, WebSearch generates a list of links leading to relevant genealogy websites such as FamilySearch, MyHeritage, Ancestry, and more.
2. How does it work?
You activate a person, place, or source in Gramps.
WebSearch automatically generates a list of search links related to the selected entity.
Simply click on the desired link, and it will open in your browser.
3. What can you search for?
WebSearch supports multiple navigation types:
People (name, surname, birth year, death year, birth place, etc.).
Places (name, geographic coordinates, place type).
Families (parent details, marriage place and year, divorce details).
Sources (source title).
4. How to customize?
WebSearch works immediately after installation, but you can customize it:
Choose which websites to use for searches.
Modify the format of generated search URLs.
Use additional variables for search queries.
More detailed information about configuration can be found in the full README.
5. Additional Features
Add links to notes – Save important links in a person's record.
Generate QR codes – Quickly open links on a mobile device.
Sorting and filtering – Easily find the necessary links.
Use OpenAI (optional) – Get additional search recommendations (may require an OpenAI API key).
6. How to install?
WebSearch installs as a standard Gramplet for Gramps. Simply download and add it to the list of available add-ons.
That is totally up to you.
Yes. If you submit your addon to the v6.0 third-party addons repository, then its translations will appear in Weblate automatically.
2 Likes
If an addon is intended for more than one Gramps version, then it will have to appear in multiple branches with different gpr files.
2 Likes
Right you are. Add a Configure option to Hide the final URL and show the comment instead.
I think that I see a real power in having the final URL visible as a feature for advanced users. (Particularly if the gramplet uses the Simple Table feature of a context menu to copy the whole table. Which would allow a list of links to be pasted into a Note or the body of an eMail message. Such a list of fully composed links could then be flowed into a report… like the Narrative Web report.)
But a simplified list with the comment will be less scary to basic users.
I can add a new Comment column, the last. And it will be always visible without scrolling if Final url column is hidden via settings.
Looks like this is exactly what you are expecting
1 Like
It is a solid start and will have to be massaged into our wiki’s format. I also have used a prompt in the past which does a pretty good generation of feature list by examination of source code. It tended to note features that I missed from GUI experiments.
1 Like
You should have a separate PR for each branch you want to add this gramplet. The gramps_target_version in the gpr file will be different (at least).
Once the gramplet exists on a branch, when you make changes you do NOT have to increment the version as this is done automatically in the publish step.
If you want to make changes in a python file that is the same for two branches, you can make 1 PR and note that you want it cherrypicked to the other branch.
2 Likes
