Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
$USERPROFILE on WinNT shold resolve to the root of the users home directory. $SYSTEMROOT should resolve to the operating system root directory. If I remember right, there is a portable way to find the my documents folder. (ie, win9xnt, any language.) I know the BZFlag project is able to find it reliabaly on my windows 98 machine, for one... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
The Tone'ster writes: IMHO, it would be nice to see default config file names and locations be names that would work across all platforms and to see that they land in places on a given OS that have analogies to each other. Better, IMHO, would be to keep default configuration info encapsulated under the application root somewhere, with command line options for specifying alternate locations and/or names. I guess this flies in the face of what applications typically do on a UNIX machine. No, it's almost identical except that there's a step missing -- Unix apps typically allow both a system-wide default and a per-user default. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
Paul Deppe writes: It looks like it is not possible to specify an --aircraft in system.fgfsrc because the aircraft model is loaded before system.fgfsrc is processed (see program output below). Is this the intended behavior? I thought the processing order was supposed to be 1) preferences.xml, 2) system.fgfsrc, and finally 3) command line. We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
David, From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Megginson We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line I don't fully understand this. Until now, system.fgfsrc was just the equivalent of .fgfsrc on a Windows (and, maybe other) system. Contrary to Unix, you can't name a file .fgfsrc under Windows. So what will Windows users have to do? Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
Michael Basler writes: We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line I don't fully understand this. Until now, system.fgfsrc was just the equivalent of .fgfsrc on a Windows (and, maybe other) system. Contrary to Unix, you can't name a file .fgfsrc under Windows. So what will Windows users have to do? Oh, I see. In Unix, we have (or had) two files: system.fgfsrc in $FG_ROOT .fgfsrc in $HOME The idea was that system.fgfsrc is system-wide, while .fgfsrc is per-user. For Windows, perhaps we should look for fgfs.cfg in My Documents or wherever (is there any concept of separate user directories yet?). All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
David Megginson writes: Paul Deppe writes: It looks like it is not possible to specify an --aircraft in system.fgfsrc because the aircraft model is loaded before system.fgfsrc is processed (see program output below). Is this the intended behavior? I thought the processing order was supposed to be 1) preferences.xml, 2) system.fgfsrc, and finally 3) command line. We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line Please don't do this As I pointed out the last time you suggested doing this, on windows the system.fgfsrc file is the same thing as the ~/.fgfsrc file on Unix This is not 'old stale code' Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
David, The idea was that system.fgfsrc is system-wide, while .fgfsrc is per-user. For Windows, perhaps we should look for fgfs.cfg in My Documents or wherever (is there any concept of separate user directories yet?). Win XP and 2000 allow management of separate user directories under the Documents and Settings path for saving specific settings and files, and you can even login as a specific user. However, all this is less developed and stringet compared to a Unix system. There is no unique direct equivalent of a $HOME directory under Windows, though. Besides, older Windows variants still in use don't have these directories. Personally I've got most of my user's files just on a separate partition (and all the FlightGear stuff on yet another partition and FS2002 on yet another one and so on). From my POV the mechanism we had with just a single system.fgfsrc in $FG_ROOT would be sufficient for most (all?) Windows users. You still can allow and parse a .fgfsrc under $HOME for Unix users, though. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
Michael Basler writes: Personally I've got most of my user's files just on a separate partition (and all the FlightGear stuff on yet another partition and FS2002 on yet another one and so on). From my POV the mechanism we had with just a single system.fgfsrc in $FG_ROOT would be sufficient for most (all?) Windows users. You still can allow and parse a .fgfsrc under $HOME for Unix users, though. What we probably need to do, then, is remove the old system.fgfsrc code, and instead load a file named system.fgfsrc (or perhaps fgfs.cfg) when a Unix system would load $HOME/.fgfsrc. That should fix the init-order problem. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
--- David Megginson [EMAIL PROTECTED] wrote: The idea was that system.fgfsrc is system-wide, while .fgfsrc is per-user. For Windows, perhaps we should look for fgfs.cfg in My Documents or wherever (is there any concept of separate user directories yet?). $USERPROFILE on WinNT shold resolve to the root of the users home directory. $SYSTEMROOT should resolve to the operating system root directory. Many cross platform apps (X-Plane as an example) use the OS root directory ($SYSTEMROOT) to store stuff. I don't know if this is good practice (I don't care for it personally), but nonetheless. IMHO, it would be nice to see default config file names and locations be names that would work across all platforms and to see that they land in places on a given OS that have analogies to each other. Better, IMHO, would be to keep default configuration info encapsulated under the application root somewhere, with command line options for specifying alternate locations and/or names. I guess this flies in the face of what applications typically do on a UNIX machine. Tony = ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
Dear All,
oops, pardon moi ... RE:MSVC6 Update - continued ...
This i added, explicily, to fg_init.cxx
// Next check the 'root' for a system.fgfsrc file
if ( aircraft.empty() ) {
// Check for $fg_root/system.fgfsrc
SGPath config( globals-get_fg_root() );
config.append( system.fgfsrc );
aircraft = fgScanForOption( --aircraft=, config.str() );
}
in the fgInitFGAircraft() service ...
As i intimated in a README.msvc6 i sent to Curt, there seems
some BIG DIFFERENCE in environment variables. The CygWin
'attempts' to re-create the unix 'needed' environment variables,
and thus MSVC? user are quite perplexed. What is THIS?
Look, if when the 'system' loads, there is a thing called ABC
created in the runtime environment, great. But in windows we
have 'some' control on this. There is NO automatic $(HOME)
thingy, unless (perhaps?) you are in the WINNT stream? Or
you REALLY want it created!
This 'dependance' on some RUNTIME creation has always
irked me. If you want an runtime application to 'see' something,
tell it, NOT the 'world', what you want. That is each user will
'run' the application with the information it requires, including
what folders to look in ... there are NO 'global' folders ... for
me, anyway ...
To say suggest My Documents, instead of Mes
Documents, is to not yet grasped the complexity of 'who-am-
i combined with 'where-am-i', it is just too big ... language -
pah!
It really seems sufficient that there is ONE 'system' file that
fgfs loads, if it exists, and that is good. What are we missing?
Thus -
We were planning to drop system.fgfsrc -- I thought
we already had, ..
flies directly in the face of this. What is FGFS doing?
Hope this helps ...
Geoff.
PS: Curt, did you not get my README.msvc6? Or you do
not feel it should be in the CVS just yet?
pps:
Dear David,
Oh, I see. In Unix, we have (or had) two files:
system.fgfsrc in $FG_ROOT
.fgfsrc in $HOME
The idea was that system.fgfsrc is system-wide, while .fgfsrc is
per-user. For Windows, perhaps we should look for fgfs.cfg in My
Documents or wherever (is there any concept of separate user
directories yet?).
Yes, windows, or as sometimes written with an embedded '$' sign,
has or has NOT 'separate user space'. In my single home system,
i reduce all this user stuff to me - i am the user - no one else ...
in the NT vain, they make it 'important', but it can still be reduced.
That means $(HOME) has to end homesystem for .fgfsrc
to work, or in windows use %HOME%, but i digress ...
g.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc
Geoff McLane writes: PS: Curt, did you not get my README.msvc6? Or you do not feel it should be in the CVS just yet? Hmmm, I don't recall, you probably want to send it again. If I did get it, it is now very buried in my email pile. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
