20,741
edits
mNo edit summary |
m (http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18693.html) |
||
Line 11: | Line 11: | ||
* GUI | * GUI | ||
* Nasal Scripting Interpreter | * Nasal Scripting Interpreter | ||
The way that Nasal is integrated it doesn't really touch the core of FlightGear much at all; they just hook a new subsystem into the global list. SimGear is affected only in that it gets a new directory and a new library to build. | |||
There is some documentation on the language available at: | |||
* http://www.plausible.org/nasal/ | |||
* http://www.plausible.org/nasal/doc.html | |||
* http://www.plausible.org/nasal/sample.nas | |||
Nasal itself has a standard library of general purpose functions, in addition it supports dozens of FG-specific extension functions to do various FG-related things, for example to interact with other subsystems (e.g. AI traffic, weather, FDM, GUI etc). In other words, while you'll find lots of standard library functions, there are many FG/simulation-specific functions available in FlightGear/Nasal. | Nasal itself has a standard library of general purpose functions, in addition it supports dozens of FG-specific extension functions to do various FG-related things, for example to interact with other subsystems (e.g. AI traffic, weather, FDM, GUI etc). In other words, while you'll find lots of standard library functions, there are many FG/simulation-specific functions available in FlightGear/Nasal. |