|
From: Alan T. <ajt...@v-...> - 2017-01-05 23:30:48
|
-----Original Message----- From: geneb Sent: Thursday, January 5, 2017 10:16 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Hard coded fg-root path in flightgearstartup? On Thu, 5 Jan 2017, Alan Teeder wrote: > Whilst we are discussing fg-root can I chime in with some of pet my > grudges? > > On Windows Flightgear´s directory structure does seem a little confusing - > to me at least. > > I use git and the sources plus fgdata are in C:\Flightgear. I have > Flightgear installed in C:\Flightgear\install\msvc140-64. I have custom > aircraft in C:\Flightgear\MyAircraft and custom scenery in > C:\Flightgear\MyScenery. > Just a note - it's bad practice to install software to the root directory of the boot drive - it was deemed "bad" once the Program Files directory structure was implemented in Windows. (personally, I don't care where you install software, I'm just pointing this out from a 'best practices' standpoint. :) ) If it was up to me, the executables would live in Program Files (x86) or Program Files (x86 vs 64 bit) and ALL the data (and configuration files) would live in C:\users\<user>\FlightGear. The leading dot (.fgfsrc) is how *nix hides filenames. IMO, no configuration file should be hidden - especially if it's expected that the end user may make changes by hand editing. "flightgear.ini" makes more sense in that context. g. ------------------- My computers are single user so this is not much importance to me. If my computers were multi-user I would be using C:/user/alan/Documents/Flightgear for a work directory , which I think is the equivalent of /home/user/alan/Flightgear on unix. I take your point. IMHO "Program files" is not a good place for installing WIP (in this case flightgear/simgear git) executables. They belong in the user area. On the other hand data should be split between core data and user data. Also (at least the last time I forgot to change Flightgear´s Cmake install directory) Visual Studio blocks installing directly into "Program Files". Alan |