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 8: | Line 8: | ||
* 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) | ||
* decoupling FlightGear initialization such that certain subsystems can be optionally disabled right at the beginning (e.g. FDM, sound, replay, scenery) | * decoupling FlightGear initialization such that certain subsystems can be optionally disabled right at the beginning (e.g. FDM, sound, replay, scenery) | ||
* grouping related subsystems into '''SGSubsystemGroup''' instances to manage them holistically (e.g. xml-autopilot & route-manager) | |||
* 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: | ||