Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G


Jump to: navigation, search

Howto:Extend Nasal

560 bytes added, 17:24, 27 June 2012
Wrapping Classes as Nasal Objects (ghosts)
= Wrapping Classes as Nasal Objects (ghosts) =
'''To be written by Hooray & Zakalawe'''
Quoting: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17546.html
Absolutely agreed that making as much data as possible
available is valuable - as you say, I'm always amazed by the neat
things people do in nasal scripts. [...]
I'm still thinking on different ways to make the core datasets a
bit more 'lazy'.
Quoting: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg29032.html
If that sounds impossible, then I'd strongly advocate creating separate special purpose-functions in the short term, that do *one* thing, and be more easily
subsumed if/when we properly expose the C++ types to Nasal.
Quoting: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg29034.html
Yes I'd like to second the idea of returning objects (with attributes
and methods for doing interesting things), I'm guessing we don't need to
box (2 or 4 lat/lon pairs), and if the same could be done with other
navigation elements in nav.dat it would be most excellent!
Quoting: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg29035.html
Well, this is exactly what all the query methods on FGPositioned do - the
problem is, they return FGPositioned subclasses, which aren't much use to Nasal
proper naGhosts, and could have a forwards-compatible APi when the ghosts are

Navigation menu