Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Durk Talsma
On Saturday 24 November 2007 21:32, Melchior FRANZ wrote: where name seems to be totally free and without rules. Some examples are Custom Startup Location, Startup, Anchor, Ramp, Gate A 1, East Mil cargo Ramp 65, 249.660 (huh?), Plataforma 1 (oh, plataforma ...), etc. There should be a type

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Durk Talsma -- Sunday 25 November 2007: On Saturday 24 November 2007 21:32, Melchior FRANZ wrote: [alternative startup location entries in apt.dat] All very good reasons why I opted not to use this information directly, but can it into the AI related parking.xml file. And how do those help

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Durk Talsma
On Sunday 25 November 2007 09:43, Melchior FRANZ wrote: * Durk Talsma -- Sunday 25 November 2007: On Saturday 24 November 2007 21:32, Melchior FRANZ wrote: [alternative startup location entries in apt.dat] All very good reasons why I opted not to use this information directly, but can it

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Durk Talsma -- Sunday 25 November 2007: To summarize, the C++ infrastructure is there to support this for user aircraft. All that's needed is to add a command line option, like: --parking-id= --get-available-parking, and probably one c function to interpret the lat /lon/heading values and

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Melchior FRANZ -- Sunday 25 November 2007: But I don't like that the very much un-dynamic parking information isn't in the Airports/ dir, where it belongs, and that this somehow drags AI/Traffic into the game. What about this: we create in $FG_ROOT/Airports/ a subdir with airport files which

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Durk Talsma
On Sunday 25 November 2007 11:13, Melchior FRANZ wrote: * Melchior FRANZ -- Sunday 25 November 2007: But I don't like that the very much un-dynamic parking information isn't in the Airports/ dir, where it belongs, and that this somehow drags AI/Traffic into the game. What about this: we

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Durk Talsma -- Sunday 25 November 2007: But while we're at it, wouldn't it be better to update and extend the parking.xml files into PropertyList XML, and move those to $FG_ROOT/Airports/Data, like you suggested? And that sounds good to me! :-) Is there any information in the current

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Melchior FRANZ -- Sunday 25 November 2007: So, a file $FG_ROOT/Airports/Data/K/KSFO.xml would contain [...] I think this should be for KSFO: $FG_ROOT/Airports/Data/K/KS/KSFO.xml The Data/ dir name is a bit ugly, as all in $FG_ROOT is data, after all. I wouldn't mind using something else.

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Melchior FRANZ -- Sunday 25 November 2007: $FG_ROOT/Airports/Data/K/KS/KSFO.xml The script is done, and generates files like the attached one for LEAB. The source is $FG_ROOT/Airports/apt.dat.gz, used are entries 1, 14, 15, 5? as described in http://www.x-plane.org/home/robinp/Apt810.htm The

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* Melchior FRANZ -- Sunday 25 November 2007: The script is done, and generates files [...] ... which I haven't tested with xmllint. ichannel should, of course, be /channel. m. - This SF.net email is sponsored by: Microsoft

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Durk Talsma
On Sunday 25 November 2007 17:01, Melchior FRANZ wrote: - is the parking information enough for AI/Traffic. It's all there is in apt.dat.gz, but the parking.xml files have more. Is the extra information from different sources, or just made up? For AI/Traffic, we'd need some additional

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Melchior FRANZ wrote: [...] The overall disk space consumption is 34 MB (tar.gz: 633 kB). That is rather large, a more compact way than loads and loads of files maybe? After all even if file is small it will take at least one block in the file

Re: [Flightgear-devel] startup menu option

2007-11-25 Thread Melchior FRANZ
* AnMaster -- Sunday 25 November 2007: Melchior FRANZ wrote: [...] The overall disk space consumption is 34 MB (tar.gz: 633 kB). That is rather large, We have aircraft in CVS which use well over 20 MB, so I find the 34 MB not really shocking. The problem is that this will grow. I did

[Flightgear-devel] startup menu option

2007-11-24 Thread SydSandy
Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread Melchior FRANZ
* SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what that should be. I wouldn't be happy to release 0.9.11 with an Aircraft menu with a

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread SydSandy
On Sat, 24 Nov 2007 20:55:59 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread Melchior FRANZ
Just to make this clear: I'm not against an Aircraft menu, if it isn't empty and/or non-functional in 99.% of the fgfs runs. But exactly that will happen if we rush it in now. I suggest to wait with that until after the release, which, as everyone knows, will happen around Xmas (we just don't

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread Melchior FRANZ
* Melchior FRANZ -- Saturday 24 November 2007: Obligatory clicking on startup dialogs is a pain, and I don't think we want that. I'd say we make an option like --startup-mode={parked,idle}(or something) BTW: there are a lot of optional startup locations defined in apt.dat: $ zgrep

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread alexis bory
SydSandy a écrit : On Sat, 24 Nov 2007 20:55:59 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread SydSandy
On Sat, 24 Nov 2007 21:21:23 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: Just to make this clear: I'm not against an Aircraft menu, if it isn't empty and/or non-functional in 99.% of the fgfs runs. But exactly that will happen if we rush it in now. I suggest to wait with that until

Re: [Flightgear-devel] startup menu option

2007-11-24 Thread Bohnert Paul
Hi All, I like the way the cvs c150 starts. It has a pop up menu, Hot or Cold start. The apt.dat file supports named start up locations associated with an airport. As an example the latest apt.dat file has one location defined for KSFO named CAL RAMP AREA. FlightGear could make use of start