On 16 Sep 2009, at 06:01, John Denker wrote: > 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. >
<snip> > This will have to be discussed quite a bit more > before anybody starts coding it. A quick comment, wearing my software engineering hat here: there's a lot of opinions about policy here (defaults vs GUI vs heuristic rules based on winds, etc). There's also some key requirements (not upsetting VFR / casual flyers, aka 'keep Curt happy', for example) - and people have asked about control from Nasal or the ATC aircraft, and John Denker has mentioned the multiplayer situation. My point is, what I'm going to do first, is improve the *architecture*, so the policy is explicit (and centralised!). Likely this will include a Nasal interface (to be driven from a GUI dialog / ATC-controller / whatever) and I even have some ideas about synchronising the state across MP. And whatever policy is default, we're going to need a pref property to allow alternate policies to be used, I suspect. Along the way, I'm going to keep the current behaviour (with its inherent problems) working, but that's *all* I'm promising, until the architecture work is done. I now return you to the policy discussion :) Regards, James ------------------------------------------------------------------------------ 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
