On Friday 08 August 2003 20:18, Norman Vine wrote: > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Curtis L. > > Olson > > Sent: Friday, August 08, 2003 2:38 PM > > To: FlightGear developers discussions > > Subject: Re: RFD: Landmarks and scenery (was Re: [Flightgear-devel] CYTZ > > and CNTower) > > > > > > David Megginson writes: > > > Lee Elliott writes: > > > > > > > Perhaps we need a directory in Scenery that can be scanned for > > > > world landmarks like this. Could the model and location data be > > > > defined in an xml file? Would it be possible to animate them? > > > > (thinking rotating restaurants and swing bridges here). > > > > > > I've been thinking about this for a while, and I think that the best > > > approach would be to read scenery from multiple directories at once. > > > For example, I could have the main scenery under > > > /usr/local/FlightGear/Scenery/, and major landmarks under > > > /usr/local/FlightGear/Landmarks/, and configure it something like > > > this: > > > > > > FG_SCENERY_PATH=/usr/local/FlightGear/Scenery/:/usr/local/FlightGear/Landmarks/ > > > > David, > > > > The ":" path separate character might be hard to make unambiguos on > > the windows platform. But it is the standard under unix. > > > > Would anyone be opposed to using the ";" character as a path separator > > since these paths could show up in universeral config files. > > I am wondering what having multiple paths to search will do for 'stutter' > > and as far as LandMarks go I can't really see why they don't just go in the > standard scenery file as since they are LandMarks they probably only > apply to one location :-) > > Norman
While it would be logical to insert them into the standard scenery, I think that expecting a relatively new and unfamilier user to copy the files to the right places in the existing scenery might be asking a bit much - it would almost certainly generate a lot of e-mails, I think. Wherever they go, the procedure for installing, updating and removing them has really got to be 'automated' and as painless as possible. LeeE _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
