Erik Hofman writes: > Curtis L. Olson wrote: > > > If nothing else we should first work on being able to have completely > > self contained aircraft trees (rather than needing a -set.xml file in > > one directory (possibly the aircraft fdm config in another direcotry) > > and everything else in a separate area.) > > The directory layout I've always envisioned was: > > Aircraft/<type> > /JSBSim > /YASim > /UIUC > /Sound > /Models > /Panel > /HUD > > But so far we didn't come to the conclusion this was actually needed.
I had a bit different idea ... well looking more closely it may not be that different, but I don't know if I'm correctly interpreting the above structure. - I'd like to see each aircraft be completely self contained in it's own subdirectory (except for "standard" base package stuff it could feel free to reference.) These standard pieces wouldn't necessarily need to live in the Aircraft subdirectory too. - We would eliminate the YAsim fdm config directory. Instead the fdm config would live in the individual aircraft trees. - We would move each of the -set.xml to also live in the individual aircraft tree. - Then to install an aircraft you need to drop the aircraft's directory somewhere inside the top level Aircraft directory. We could have abitrary subdirectories to organize by aircraft type or livery or era or whatever we felt like. - To completely remove all pieces of a particular aircraft, you just remove that aircraft directory. Is that the same thing as you were saying? Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org 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
