When you choose a GEDCOM file from your OS desktop and choose Gramps as the Tool to open it, then Gramps launches, creates a new Tree with the filename and imports the selected GEDCOM file.
How can this same simplified and streamlined import process (for a specified GEDCOM file) be done in code?
And can such a process be called from a ‘hotlink’ styled text in a Gramplet or QuickReport?
@Serge did a nice bit of experimental work in PR1297 to create a starting family in a new tree in response to Novice user UX proposed solution and Novice Onboarding Gramplet. But it is too heavy in the Interface (the user has to make too many choices and they have to be completed in the correct order) and the sample family is hard-coded (an embedded XML) and only with English placeholder names. Finally, it is fairly well hidden and ONLY available if NO Trees exist in the Manage Family Trees dialog. (The last item makes the feature and its interface tedious to beta test.)
It would be more flexible to have links to starter GEDCOMs (or .gramps
files) with a common naming pattern: StartingFamily-en.ged
, StartingFamily-fr.ged
, StartingFamily-fr.gramps
Non-programmers could create/submit Trees with localized surnaming conventions.