Currently, there's a problem with our *-set.xml system for aircraft
selection. If I want to fly the YASim DC-3, say (I love that plane),
then I invoke FlightGear like this:
fgfs --aircraft=dc3-yasim
So far, so good. Now, let's say that someone prefers another 3D model
to my modest effort,
David Megginson writes:
My proposed solution is to add a layer of abstraction to every
*-set.xml file. It will be annoying for John and me, but will make
things simpler for everyone else.
Hmm. On further reflection, this might cause trouble for properties
that are tied, like
David,
It seems to me like it would be *much* simpler to just make a copy of
the dc3-yasim-set.xml file. Say I wanted an American Airlines DC-3:
http://dfw.citysearch.com/E/V/DALTX/0213/06/66/cs1.html
I could make a dc3-aa-yasim-set.xml and repaint your model.
This means one -set.xml
Curtis L. Olson writes:
It seems to me like it would be *much* simpler to just make a copy of
the dc3-yasim-set.xml file. Say I wanted an American Airlines DC-3:
http://dfw.citysearch.com/E/V/DALTX/0213/06/66/cs1.html
I could make a dc3-aa-yasim-set.xml and repaint your model.
David Megginson [EMAIL PROTECTED] said:
David Megginson writes:
My proposed solution is to add a layer of abstraction to every
*-set.xml file. It will be annoying for John and me, but will make
things simpler for everyone else.
Hmm. On further reflection, this might cause
