On 19/07/10 11:06, James Turner wrote: > > On 19 Jul 2010, at 09:04, Scott Hamilton wrote: > >> In the long term, I'd like to see being able to also get FIXES, VOR and >> NDB information from Nasal based on a range (and possibly; range and >> heading), that could be quite useful for the increasing number of "glass >> cockpits" I think. >> If anyone is thinking of writing such a Nasal extension, then please >> also give thought to this as well. > > Yep, I am aware there's a whole range of data that should be exposed, and a > huge amount of cockpit / FMS / GPS functions that can be moved to Nasal if > that were done. The geodetical functions in Nasal could also use some love, > in that case, to make navigation work in Nasal easier - basically a smarter > wrapper around SGGeod and the functions in SGGeodesy. > > As always, the problem is time -and also the lag of me coding up new > functions (which is quite easy) to a release, so that they're generally > available to end-users, is quite long - yet another reason for a faster > release cycle :) > > James Does any of this look like it could be part of a GSoC project for next year? Anybody care to write a very brief synopsis of where this fits, what benefits we'd get from fixing it and a vague stab in the dark about expected timescales for a Comp Sci undergraduate or similar to accomplish?
Also if we fix this, what other areas does this open up? Remember however if this becomes a GSoC project, not a line of code will be written before May 2011 ;-( Best Regards Willie ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
