Initializing Nasal early: Difference between revisions

Jump to navigation Jump to search
m
http://forum.flightgear.org/viewtopic.php?f=71&t=23542
No edit summary
m (http://forum.flightgear.org/viewtopic.php?f=71&t=23542)
Line 24: Line 24:
* decoupling FlightGear initialization such that certain subsystems can be optionally disabled right at the beginning (e.g. FDM, sound, replay, scenery) {{Progressbar|10}}
* decoupling FlightGear initialization such that certain subsystems can be optionally disabled right at the beginning (e.g. FDM, sound, replay, scenery) {{Progressbar|10}}
* grouping related subsystems into '''SGSubsystemGroup''' instances to manage them holistically (e.g. xml-autopilot & route-manager) {{Progressbar|20}}
* grouping related subsystems into '''SGSubsystemGroup''' instances to manage them holistically (e.g. xml-autopilot & route-manager) {{Progressbar|20}}
* 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}}) {{Pending}}
* 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=23542] [http://forum.flightgear.org/viewtopic.php?f=71&t=22021] ({{Issue|1456}}) {{Pending}}
* allowing custom startup profiles/modes to be implemented via Nasal helper scripts, for example: {{Not done}}
* allowing custom startup profiles/modes to be implemented via Nasal helper scripts, for example: {{Not done}}
** [[FGCanvas]]
** [[FGCanvas]]

Navigation menu