Jim Wilson writes: > We certainly need to decide on which ones to include. It would > seem that 10 or so aircraft and a total base package size of 50mb > compressed (150-200mb uncompressed) would be reasonable. For CVS > users having the models in a separate tree so they can be download > selectively makes sense. BTW the AC3D files, compress 90% or more.
Agreed. In fact, I think that we should package *all* of the models individually but then preinstall a few of them in the base package, just as we do with the scenery. So how does this look? Aircraft/<type>/config.xml Aircraft/<type>/info.xml Aircraft/<type>/picture.jpg Aircraft/<type>/Documentation/ Aircraft/<type>/Model/ Aircraft/<type>/Panel/ Aircraft/<type>/Physics/ Aircraft/<type>/Sound/ Aircraft/<type>/Systems/ config.xml would include properties to be placed in the main property tree, while info.xml would contain properties exclusively for sorting and selecting aircraft (such as a description, manufacturer, etc.), and an optional reference to an image (like 'picture.jpg') that could be displayed in a selection box. Documentation/ would contain human-readable documentation, Model/ would contain the 3D model including animations, Panel/ would include a 2D panel (if appropriate), Physics/ would include all of the aero files for different FDMs, Sound/ would include sound samples for the aircraft and the sound config file, and Systems/ would include special config files for systems like the electrical system, autopilot, or FMS. 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