Hi Ryan, please excuse the rather brief comment. I had been short in
time and was about to leave - actually I ended up being too late for
the final rehearsal before a symphony concert this morning .... :-((
Your submission is touching various places, therefore please expect
various people (maintainers) to have their specific opinion on this.
For example I could envision that those who are keeping an eye on the
AI aicraft collection might appreciate the submission to be split into
specific parts - as do I for the Scenery-related files.
Ryan M wrote:
> However, due to the technical details of the new jetways, it is not
> possible to integrate them with Terrasync/Shared models as it was
> previously. This is because the jetways are specified in an XML file for
> each airport that a Nasal script parses and loads models for via
> fgcommand("add-model", ...). That's how each jetway knows its
> independent position and its relative location to the aircraft door,
> unlike a static model in scenery where this is not possible.
I'm not generally against adding specific per-airport jetway
definitions into FlightGear as a whole, but I think we should talk
about the details of the "where". Look, we're already distributing
airport-specific ground networks, why not accompagny the jetway
positions alongside the other airport-specific stuff instead of
creating yet another, new directory.
> Additionally, the 3d models have to be stored somewhere. By my logic,
> that should be in Models/Aiport, hence the new directory.
A good idea in general, but, while you are at it, please read:
http://mapserver.flightgear.org/git/gitweb.pl?p=fgdata;a=blob;f=Models/00README.CONTRIBUTE
> [...] I intended
> this to not be synced with Terrasync (syncing won't have an effect
> anyway, since ATM the script always loads models from the main models
> directory).
I'm a bit uncertain if I understand correctly - would you bother
rephrasing in different words ?
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
