Howto:Start core development: Difference between revisions

Jump to navigation Jump to search
m
Line 156: Line 156:
Also, you can get a fair amount of information out of the FG sources by running them through doxygen, too.
Also, you can get a fair amount of information out of the FG sources by running them through doxygen, too.


== Plain C ? ==
== Plain C ? (Nasal) ==
If your C++ is rusty and you'd just like to get started quickly, there are also certain FG components that are strictly (largely) pure C, the Nasal interpreter is just one example (Nasal is FlightGear's built in scripting language): http://wiki.flightgear.org/Nasal_scripting_language
If your C++ is rusty and you'd just like to get started quickly, there are also certain FG components that are strictly (largely) pure C, the Nasal interpreter is just one example (Nasal is FlightGear's built in scripting language): http://wiki.flightgear.org/Nasal_scripting_language


Line 164: Line 164:


There's also a separate wiki article providing a list of issues related to the Nasal interpreter itself: [[Improving Nasal]].
There's also a separate wiki article providing a list of issues related to the Nasal interpreter itself: [[Improving Nasal]].
None of this requires any C++ knowledge!
Only the scripting interface connecting the Nasal interpreter and FlightGear is implemented in C++, it can be found in $FG_SRC/Scripting: http://gitorious.org/fg/flightgear/trees/next/src/Scripting


= Getting started =
= Getting started =

Navigation menu