On Tue, 2009-09-15 at 22:01 -0700, John Denker wrote:
Can I also suggest, that like most things in FG, we have a property
and a Nasal API.
Now I haven't thought about this very much, but rather than forcing
some UI into concrete, it might be better
to provide a programmatic interface, then implement a default
behaviour that can be overridden later, for example
a ATC "aircraft" may wish to manipulate and control this at some
point.
* Nasal interface to lookup available ILS information (from nav.dat)
- airportinfo() already gives us a list of runways and headings
* some properties that can be changed to switch the ILS.
Then someone else can make a Menu in Nasal that uses that above to
achieve item 2 outlined below.
Scott.
>
> There's no need for that.
>
> The simplest approach might be:
> 0) For naive users, and even experienced VFR users,
> they don't know and don't care about this issue,
> and everybody would like to keep it that way.
> 1) At startup, we shall set every reversible ILS to
> the higher-numbered end (19 through 36 inclusive).
> We choose this end because most users live in the
> temperate zones where the prevailing westerlies
> prevail most of the time. (I retract my earlier
> suggestion about initializing them randomly.)
> 2) There shall be a menu item, which appears when
> commanded by the user -- *not spontaneously* -- and
> can be used to reverse the nearby reversible ILS(s).
> Perhaps an array of buttons listing the nearest 10
> airports with reversible ILSs or some such. And
> maybe a textbox to allow reversing an arbitrary
> airport or an arbitrary frequency. This should
> suffice for single-player FGFS. This would most
> likely only be used by instrument-rated pilots, or
> instrument students, so we can assume they have
> enough sophistication and dedication to deal with
> such a popup. We need some kind of switching,
> because the ILS is most needed when the weather is
> very bad, and that usually means the wind is *not*
> from the prevailing fair-weather direction.
> 3) Multiplayer is quite a bit trickier, as previously
> discussed. This is related to MP ATIS, MP lights,
> pilot-controlled lights, navaid IDENT, et cetera.
> This will have to be discussed quite a bit more
> before anybody starts coding it.
**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
