20,741
edits
Howto:Exposing Subsystems to Nasal: Difference between revisions
Jump to navigation
Jump to search
Howto:Exposing Subsystems to Nasal (view source)
Revision as of 19:06, 6 February 2016
, 6 February 2016→Background
(→Status) |
|||
| Line 13: | Line 13: | ||
This article intends to document the steps required to expose meta information about timers and listeners to scripting space so that a Nasal/Canvas bsed UI (dialog) can be displayed with a list of active callbacks, and their runtime characteristics. | This article intends to document the steps required to expose meta information about timers and listeners to scripting space so that a Nasal/Canvas bsed UI (dialog) can be displayed with a list of active callbacks, and their runtime characteristics. | ||
However, the underlying timer/listener APIs are not specific to [[Nasal]] scripting but also commonly used elsewhere (in fact, in most other subsystems), and they are also infamous for buggy C++ code that similarly affected FlightGear performance. | |||
This will include patches to all 3 repositories of FlightGear, i.e. SimGear, FlightGear and fgdata. | This will include patches to all 3 repositories of FlightGear, i.e. SimGear, FlightGear and fgdata. | ||