Which new names? Are the old ones wrong?
Well cosmetic changes like changing yf23 -> YF-23 ...
What really disturbs me is that Lee's aircrafts are full of redundant stuff. Look for example at a10/Sounds/Samples/*.wav! These are no a10 specific sounds, but only some sounds copied from $FG_ROOT/Sounds/.
Or look at a10/Panels/Instruments/Textures! Lots of textures, simply copied from Aircraft/Instruments! Almost 2 MB of silly redundancy. And this misbehavior can be found in any of Lee's aircraft dirs.
Aircrafts in the base package shouldn't act like independent addons,
but re-use the common files. I'd rather clean that mess than do
cosmetic operations on directory names.
There's a balance to be had here ... I don't know that either extreme is correct. We are still feeling out this aircraft development and management process. We still have a few things to iron out.
Currently our relative path names embedded all through the various config files for aircraft (panels, animation, etc.) are all relative to the data/Aircraft/ subdirectory. This means we can't relocate an aircraft to a sub-sub folder without changing all it's built in paths. It would be nice to get to a point some day where all our aircraft our truly relocatable.
I am leaning towards in the future, only including a half dozen of our best or most representative aircraft in the base package. But doing this means we need to make sure that our aircraft are as easy for newcomers to install as our <cough> scenery chunks </cough>. Hopefully this improves with the fgadmin utility for scenery in the upcoming release, but we probably need to do something for aircraft packages too.
It's convenient to expect that all our users can figure out the directory layout of our project, but it isn't quite as obvious to a lot of people as we'd like to think it is.
Anyway, I'm starting to ramble here, but my point is that we shouldn't be too critical of Lee's arrangement until we get some of the higher level aircraft management issues all sorted out and perfectly thought through. In the mean time, aircraft designers are going to do the best they can.
Regards,
Curt.
-- Curtis Olson Intelligent Vehicles Lab 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
