20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
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 | ||
* providing an integrated GUI front-end/launcher | * providing an integrated GUI front-end/launcher using [[Canvas]] and [[Nasal]]: [[Aircraft Center]] | ||
* moving Nasal initialization out of C++ into scripting space | * moving $FG_ROOT/Nasal initialization out of C++ into scripting space, introducing dependency resolution via io.include | ||
* decoupling FlightGear initialization such that certain subsystems can be optionally disabled | * decoupling FlightGear initialization such that certain subsystems can be optionally disabled right at the beginning | ||
* making the initialization process/splash screen more responsive by using Nasal/Canvas instead of hard-coded GL code [http://forum.flightgear.org/viewtopic.php?f=71&t=22021] ({{Issue|1456}}) | * making the initialization process/splash screen more responsive by using Nasal/Canvas instead of hard-coded GL code [http://forum.flightgear.org/viewtopic.php?f=71&t=22021] ({{Issue|1456}}) | ||
* allowing custom startup profiles/modes to be implemented via Nasal helper scripts, for example: | * allowing custom startup profiles/modes to be implemented via Nasal helper scripts, for example: | ||