Re: [Flightgear-devel] Proposal: New way to add commandline options

2005-12-17 Thread Christian Mayer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Spott schrieb: > > I see three reasons opposing this idea: > 1.) I'm not sure but I assume you can't use ":" inside a command line > option on certain platforms (Windows). I really can't imagine any problems that it might cause under window

Re: [Flightgear-devel] Proposal: New way to add commandline options

2005-12-17 Thread Martin Spott
Erik Hofman wrote: > How would we all fell about minimizing the number of command line > options in favor of the --prop:= method and make sure all > of them are explained in a document rather than the help message. I see three reasons opposing this idea: 1.) I'm not sure but I assume you can't

Re: [Flightgear-devel] Proposal: New way to add commandline options

2005-12-17 Thread Erik Hofman
Frederic Bouvier wrote: I don't see the real benefit of this naming change. I rather see the burden of changing fgrun. And there are options that are not reduced to a property assignment. True, those should be kept. But the main reason I started this was because: 1. We have at least two opti

Re: [Flightgear-devel] Proposal: New way to add commandline options

2005-12-17 Thread Frederic Bouvier
Erik Hofman a écrit : Hi, I was thinking, FlightGear is already able to handle way more options than advertised when running fgfs -h -v How would we all fell about minimizing the number of command line options in favor of the --prop:= method and make sure all of them are explained in a do

[Flightgear-devel] Proposal: New way to add commandline options

2005-12-17 Thread Erik Hofman
Hi, I was thinking, FlightGear is already able to handle way more options than advertised when running fgfs -h -v How would we all fell about minimizing the number of command line options in favor of the --prop:= method and make sure all of them are explained in a document rather than the h