Changing the multimerge's help_url in the gramplet registration file to the GitHub source folder's README.md file would give you direct control over the documentation. (We don't have the target webpage on the Gramps Project wiki for this tool yet. Windows doesn't ship with a .md Markdown built-in viewer. But GitHub's server automatically renders the README.md as HTML.)
(I'm looking into what it takes to use a local README.html in a docs subfolder of the same folder as the registration file. Perhaps it would be easy enough to ship an add-on with documentation. This discussion on Discourse may also be of interest.)
changed
help_url="MultiMergeGramplet",
to
help_url="https://github.com/Taapeli/isotammi-addons/tree/master/source/multimergegramplet/README.md",
Modified the version number slightly. (You probably increment more than a hundredth in the 3rd value.)
Changed the .gpr.py file as requested, except that the help_url that starts with https does not work. This seems to be a defect in Gramps code. Now the url uses plain http.
Changing the multimerge's
help_url
in the gramplet registration file to the GitHub source folder'sREADME.md
file would give you direct control over the documentation. (We don't have the target webpage on the Gramps Project wiki for this tool yet. Windows doesn't ship with a.md
Markdown built-in viewer. But GitHub's server automatically renders theREADME.md
as HTML.)(I'm looking into what it takes to use a local README.html in a docs subfolder of the same folder as the registration file. Perhaps it would be easy enough to ship an add-on with documentation. This discussion on Discourse may also be of interest.)
changed
help_url="MultiMergeGramplet",
tohelp_url="https://github.com/Taapeli/isotammi-addons/tree/master/source/multimergegramplet/README.md",
Modified the version number slightly. (You probably increment more than a hundredth in the 3rd value.)