20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
Philosopher (talk | contribs) m (move initial heading; don't use io.include) |
mNo edit summary |
||
| Line 3: | Line 3: | ||
This is a summary of all discussions relating to: | This is a summary of all discussions relating to: | ||
* 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] | |||
* extending 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) | ||
| Line 11: | Line 13: | ||
** [[FlightGear Benchmark]] | ** [[FlightGear Benchmark]] | ||
** [[FlightGear Headless]] | ** [[FlightGear Headless]] | ||
** supporting stand-alone [[Nasal]]/[[Canvas]]-baased applications like a MapStructure-based moving map or a virtual [[Stand Alone ATC Control Development|ATC client]] | |||
== Objective == | == Objective == | ||