On Thursday, October 16, 2003, at 09:55 am, Erik Hofman wrote:
As a sidenote to all FG developers, it would be great if any part of the base package that normal users might want to expand can handle multiple paths : then I can locate the main base package, which is essentially static for a given release, inside the the application bundle (i.e invisible to the end user), and they can drop new aircraft / scenery / other extendable resource into a 'plugin' directory location as described above.
This sounds like an excellent idea!
Heh, I'll take a look once I have a working binary, then. Packaging is a pet-peeve of mine, because installing and un-installing add-ons for MSFS and Fly! was such a chore. This is related to my desire of packaging each add-on as a zip / tarball, but that's going to have to wait until the PLIB model loaders are fixed not to access the filesystem directly.
Anyway, just being able to search a list of places for Scenery and Aircraft will be a start, I have no idea which other pieces of the base package end-users might modify (nav-data maybe? but even then, probably not, if releases are every 6 months ... and most people don't care about having the most accurate AIRAC cycles)
H&H James
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
