I wondered about changing the database directory too. Figured that there was an added functionality that I was overlooking. So I’ve been mulling it over for the last couple hours.
The only thing I came up with was the educational opportunity of pointing out the database location could be elsewhere. But that would require even more text to build that understanding. So the extra required learning would make the learning curve a bit more steep.
However, this “First Time” implementation uses a conditional test for contextually deciding if a GUI button is needed. (Similar to deciding if the “Archive” or “Extract” buttons are needed.) It creates a special case that is complex to test, document and support.
Imagine the user who has already tried and failed to use Gramps. So the First Time button is gone. They vent a bit in this forum and we have to walk them through finding the User Directory (for their OS), drilling down to the delete the gramps.ini and flushing the database folder. This would amplify the bad first experience.
Say that this new button might be made a bit more available… beyond only being valid for 1st time use, but also anytime there is: 1) NO database loaded, or 2) the loaded database is empty.
(That would certainly make easier access for testing the feature by users who already have trees.) Expanding the conditions means the button would need a different name from “First Time” though. (If no tree was loaded, it does a New tree then Loads the new tree, then goes to the Generate stage. If an empty tree exists, it just jumps to the Generate stage.)
Could it also use the “New” button’s naming convention for the database name? The new Tree creation really doesn’t need any interface either. The “First Time” just creates the “New Family Tree” database, loads it and goes to the generate/Import Tree options dialog. The Family Tree Manager will appear the next time they open Gramps and the “Rename” button is self-explanatory.
Maybe the First Time button could be tied to generating database content from the Generate Testcases module?
The language barrier could be eliminated for the example by generating the given name with the relationship calculator. So the given name would describe that relationship connection. And do so in the users native language. Persons that self identify also eliminate one cognitive barrier. If you’d think that proper Given Names is more intuitive, maybe the relationship could go in the “Title” or “Suffix”? (Although if relegated to the Title, this hint wouldn’t appear in many reports/charts where Gramps generates a formatted name.)
A step further, if the user had a GUI dialog control over the scale of the tree, they would be more invested in exploring the sample. (An even better option would be if this generation dialog could also have an alternative to generating the sample tree. A Import button to open a file selector Import Dialog that is preset to folder path containing the Gramps GEDCOM and XML example folders.)
The maximum scale could be very limited — where the users could select a number of 0-2 (none, parents, grandparents) ancestor generations & 0-2 (none, children, grandchildren) descendant generations.
The last thing that would be helpful is if Gramps had a (default on) preferences option for hint/prompts for empty windows. This is similar to the greyed & italicized text prompts for the unlabeled “Suffix” & “Prefix” fields in the Edit Person dialog.
In the Family Tree Manager, the prompt could say that “There is no tree with Genealogical Data. Click the (née) First Time button to generate or import some sample data.”