Need some help with the macOS section below, which is missing a couple filepaths. And for the listed paths to be double-checked in each OS. (The Linux items were checked with Fedora. Are they compatible with other distributions?)
While attempting to expand the GtkFileChooser documentation, some deficiencies popped up. I intended to follow the pattern of Gramps User Directory wiki article for similar articles on the application install path, example files path, Bookmarks path in the various OSes. (The User Directory page is still too tangled to be used as a quick reference. So revision can start with inserting the following in outline overview section into the article. Then streamline the rest of the article.)
What other paths would be useful? Obviously it is useful to note that most of the “User Defined” paths in the Preferences are found in the gramps.ini. The exception being the Relative Media path… which is stored in each Tree.
(this folder has a gtkfilechooser.ini file. I also have an empty gtk-3.0 folder. I have not done any customization, so maybe that is why gtk-3.0 is empty.)
You might want add a bookmark (your Media relative path tends to be useful) just to verify whether Gramps is using the 2.0 or 3.0 Gtk. If you’re using Gimp, this may add a bookmark there too. (That’s useful if you’re servicing the media objects. Since metadata) In linux, the bookmark appears in the OS filechooser.
If the ~/.gramps folder is empty, then that isn’t the right path. Let’s work backwards from your plugins folder. (Then see if a shorthand element substitution is needed to make the path work for everyone.)
My folders are the same as @GaryGriffin’s. But my gtk-3.0 folder isn’t empty; there’s a “custom-papers” file there, containing the details of a custom page size that I saved at some point. So it seems to be usinf that one.
Can I just say this is not a good place to store a file that a new user might be very interested in?
I would hazard a guess that most Mac users are unaware that an “application” is actually a special type of folder with numerous files stored inside. Apple goes to considerable lengths to maintain the illusion that an app is a single monolithic thing. Trying to get a new Gramps users to navigate into the application’s bundle is far from intuitive. I think a better approach would be a Help menu item that launches the user’s default browser to a web page where they can download any example files that interest them.
If there was a way for the installer (in all OSes and distributions) to put the Examples folder into the Gramps User Directory location, it would be FAR more appropriate than bury it so deeply in the Application. (That might not be possible to integrate into the macOS one-and-done drag"n’drop install. So maybe have them as a ZIPped file in the Application Share path that is unpacked to that location when Gramps is initially registered. The initial building of cached binaries from the python source is already a slow process. An unZIP might not be too much more overhead?)
Unlike the protected Application area, Users would have the ability to tweak the Example files if they were in the User Directory. And Addon plugins could be built that would expand the Examples. So perhaps another set of CSV examples might be added to demonstrate its import capabilities. Or sample files could be provided to demonstate the feature of the Addon.