> Possibly if we divided the aircraft up by the class of license that > would be needed to fly them? Given we're trying for a high degree of > realism, that could easily be the most useful approach, and > certainly it'd be one that people might want as an option . . . >
Wouldn't it just be easier to allow the user to configure how they'd like the aircraft lists presented? The model file can indicate aircraft details such as licence requirements, operation category, etc. The user could then configure via a global option of some kind as to how they want the available aircraft sorted and listed. I think storing each aircrafts' data in a tar file was mentioned earlier. Why not use the infozip libs (gpl'd I think) to create ".FGAR" (FlightGearARchive) files that would hold the model configuration and any associated textures in a compressed format. It would keep things simple for the end-user and any fancy editing tools could be built to crack open the archive easily enough. The software should be smart enough (based on data in the "config" portion of the model definition) so that directories breaking down aircraft by FDM wouldn't really be required any longer. Good ideas or should I go back under my rock? :) g. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
