20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 36: | Line 36: | ||
** [[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]] | ** supporting stand-alone [[Nasal]]/[[Canvas]]-baased applications like a MapStructure-based moving map or a virtual [[Stand Alone ATC Control Development|ATC client]] | ||
** supporting a safe subset of subsystems for [[Howto:Optimizing FlightGear for mobile devices|mobile devices]] | |||
[[File:Towards-canvas-driven-splash-screens.png|500px|thumb|Making Nasal/Canvas available as early as possible, also means that we can show Canvas-based splash screens, or even run Canvas dialogs until the scenery has finished loading. This screen shot shows two fully-responsive Canvas dialogs while FlightGear is still scenery loading.]] | [[File:Towards-canvas-driven-splash-screens.png|500px|thumb|Making Nasal/Canvas available as early as possible, also means that we can show Canvas-based splash screens, or even run Canvas dialogs until the scenery has finished loading. This screen shot shows two fully-responsive Canvas dialogs while FlightGear is still scenery loading.]] | ||