>One option is to put an aircraft completely into its own >subdirectory, and then put the *-set.xml file inside there. So, >instead of
Why not take this idea a step further? Instead of each aircraft having it's own seperate directory, why not have one directory for all aircraft. Each aircraft could be tar.gz'd with all of its relevant files in this archive. Since the files in the archive would be acessable to the user, there aren't any real issues with the user not being able to tweak things (aside from him having to extract the file, and then re-archive it). Doing this might make each aircraft more plug-and-play, in my opinion. Example: Airplane.tgz |->Compiled Model Data |->FDM (set.xml or whatever) |->Textual description, etc. * You get the idea. Major note: I've been trying to follow FG development for somewhat over a year, and still haven't been able to really figure out how FDMs are handled (are they internal to the software, or are they externally loaded). If each plane came with it's own FDM file/script, the approach of archiving each plane to a tgz with everything it needs to fly would work out very nicely. This would be practical even if all the FDMs are internally processed the same (with some data being fed to the simulation engine from an external source). David Megginson wrote: > Jim Wilson writes: > > > > I'm already concerned about the base-package size. We need to start > > > thinking seriously about making most aircraft optional add-ons. It's > > > easy for me with a fast cable modem, but I don't want to scare away > > > regular users. If the DC-3 (for example) was its own, separately > > > downloadable package, then I'd have no problem including the Blender > > > and XCF sources with it. > > > > What are the options as far as CVS? I can see splitting up the base package > > release, either into individual aircraft perhaps a few groups of aircraft. > > But it seems a little trickier with CVS and the current directory structure. > > One option is to put an aircraft completely into its own > subdirectory, and then put the *-set.xml file inside there. So, > instead of > > Aircraft/c172p-set.xml > > we'd have > > Aircraft/c172p/set.xml > > That's an easy code change. The hard part is managing panels, 3D > models, and aero models, since there's not a 1:1:1 relationship among > these. > > All the best, > > David > > -- > David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- "The modern definition of 'racist' is someone who is winning an argument with a liberal." --Peter Brimelow _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
