Template:CppBind Ideas

After working through the Nasal/CppBind article, some of the more useful things to play with it the beginning, would be exposing additional SG/FG classes to Nasal space, such as for example:

• SGPath Done (by TheTom)
• FGProtocol, to implement I/O protocols via Nasal (and help solve ticket #396 and support AJAX, REST, JSON or WebSockets) [1] [2] [3] (stubs available at [4])
• the loglist/SG_LOG() logging buffer machinery [5]
• expose VoiceSynthesizer/FLITE TTS[6] to Nasal to get rid of ATC chatter [7] Not done
• the SGSubsystem interface to register scripted SGSubsystems
• flight path history see: [8]
• the flight recorder system (replay buffers)
• State machines e.g. to help clean up the ND code [9]
• the autopilot system [10] [11] [12] (there are certain Nasal GC issues, so that we ask people not to implement FDM-coupled Nasal code like autopilots)
• exposing the sound manager, so that scripts can directly play audio files [13]
• exposing the random buildings system [14]
• There's also a pending feature request (ticket #619) to implement USB-HID support [15].
• effects framework ?
• Howto:Using OpenCL in FlightGear
• Nasal/HLA bindings, so that we can run certain scripts as HLA federates outside the fgfs process space (such as bombable or local weather)

Before working on anything related, please do get in touch with other contributors to ensure that this list is still up-to-date.

For more technical Nasal questions (C API, internals etc), you'll probably want to refer to Philosopher, TheTom, Zakalawe or Hooray on the forum - TheTom and Zakalawe can also provide help on using cppbind, having both used it extensively during the last months.