Have there been any discussions or decisions made regarding when to split FlightGear up into separate downloadable modules? At the moment it's only the scenery which works in this way but we're going to need to do the same for aircraft in the near future as well as other "stuff".
If someone creates an aircraft that weighs in at 30MB I don't think it should go into the base package. It makes more sense to me to have all the "extras" as downloadable modules and keep just a couple of default aircraft in the base package. One could still keep everything in CVS so that the developers can check it all out in one go but then split the stuff up when building a release. If we really want to get fancy we can list all the modules in a browser in FlightGear and if the user selects something that is not in the base package it automatically downloads and installs it. Examples : - User selects an aircraft from an integrated aircraft dialog that's not on his system. - User creates a flightplan with an integrated flightplan editor - the editor selects all the tiles based on the route Just some wild thoughts ... Paul _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
