I was not intending it to be a book but a restricted (limited) version for beginners (or even the experienced) that could grow (addons) as you found the need. That has the basics but not the whistles and bells
(complexity).
For example why have more than a Pedigree Tree as far I am concerned the most universally understood starting point. I am not knocking the other variants.
If you could have something that you could knock up a tree in a few hours from scratch and printout an Ancestral Report say would that not give people the confidence to progress.
phil
PS maybe my choice of āfor Dummiesā was probably not the best phraseology but they have there place.
There may be examples out there, but for me the real problem started when a new user chose PostgreSQL and filed a bug report. And that is not a bug, because a choice for PostgreSQL implies that you need to install a PostgreSQL server, which can have its own dependencies, and can be installed on the same PC, or somewhere else, even on a server running on another OS, and you may even need to tell your firewall that this connection is legitimate. If you donāt, you may have a situation where the server is running, but where Gramps can still not connect to it.
To me this means, that this whole thing is a red herring, because the user should not use that backend at all. And now weāre in a sort of rabbit hole discussing things that are quite interesting by themselves, touching the UI, and our documentation, but at the same time, you wonāt get much further if you donāt address the real problem, which is the user making a bad choice.
The next thing is, that I donāt think that you can help anyone on Windows by experimenting with this backend on Fedora, or another Linux, for that matter, for the simple reason that the whole configuration process is quite different. It may give you the same port, if thatās not occupied by Microsoft, but by all other means, I really think that you are wasting your time on this, because there are users with a working PostgreSQL config on Windows 10, here on this forum.
There are more users who completed this than @UlrichDemlehner alone, but you may ask him about this, so that we can use his experience to update the wiki, and maybe some other manual too, like Gramps for seniors.
I just noticed that Volker re-installed Gramps and configured it to use SQLite instead, so that part of the problem has been solved.
This leaves the issue that we have no proper manual for setting up Gramps with a PostgreSQL backend on other Linuxes like Fedora, and on Windows 10, and 11.
I agree with this suggestion. Database path should def be on the top and dim them more when they cant be used. Not even a question if it should be done to me.
Alternative solution would be to not show them at all, when other setting is set so they cant be used.
An alternative that would maybe be easier for users that doesnt use the feature, or make setting less confusing/intimidating would be to hide the settings behind a āadvancedā button or drop-down. But I am guessing more people would be against doing that.
I had assumed that these would be filled in if one is to work on database residing on a remote drive of a networked PC ā e.g., on a Windows remote C:\ drive.
But then I just noticed that these two fields are greyed out on my Gramps v5.2.2/Win10.
These fields are only needed when Gramps needs to talk to database server process, which can be local or remote. The standard SQLite database doesnāt need that, because itās a library.
