David Culp writes: > > It'll be a real pain developing and testing a/c if a new archive has to be > > created after each change. > > This might mean that unpacking the whole archive first, then > reading, would be > best? This has the benefit of minimizing code changes as well. > > - OR - > > The reading can be made intelligent, so that --aircraft=F16 will be read in > the current way, and --aircraft=F16.tar.gz will be read in as an archive?
Before we get too far down this path, there's one major wrench I need to throw into the gearing. Consider that much/most/all of our model loading is done through plib's loaders. Some model formats allow you to reference models in other files (kind of like #includes.) Just about all 3d model formats allow you to reference textures. Whatever scheme we come up with would also have to modify or overload all of plib's model and texture loading functions with the additional functionality they would need to be able to also read from our archive format. I'm not sure that would be an easy or straightforward thing to do. 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
