20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* initializing the Nasal scripting interpreter earlier | * initializing the Nasal scripting interpreter earlier | ||
* moving subsystem-specific initialization of Nasal APIs into each subsystem's bind methods, as per [http://forum.flightgear.org/viewtopic.php?f=71&p=214436#p214436] | * moving subsystem-specific initialization of Nasal APIs into each subsystem's bind methods, as per [http://forum.flightgear.org/viewtopic.php?f=71&p=214436#p214436] | ||
* extending cppbind to keep track of added symbols, to easily remove them on demand | * extending [[Nasal/CppBind|cppbind]] to keep track of added symbols, to easily remove them on demand | ||
* providing an integrated GUI front-end/launcher using [[Canvas]] and [[Nasal]]: [[Aircraft Center]] | * providing an integrated GUI front-end/launcher using [[Canvas]] and [[Nasal]]: [[Aircraft Center]] | ||
* moving $FG_ROOT/Nasal initialization out of C++ into scripting space (aka "bootstrapping") while introducing proper dependency resolution (inter- and intra-modular) | * moving $FG_ROOT/Nasal initialization out of C++ into scripting space (aka "bootstrapping") while introducing proper dependency resolution (inter- and intra-modular) | ||