395
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
m
move initial heading; don't use io.include
No edit summary |
Philosopher (talk | contribs) m (move initial heading; don't use io.include) |
||
| Line 1: | Line 1: | ||
{{Nasal Internals}} | {{Nasal Internals}} | ||
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 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 | * 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 | * 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}}) | ||
| Line 13: | Line 12: | ||
** [[FlightGear Headless]] | ** [[FlightGear Headless]] | ||
== Objective == | |||
{{cquote| | {{cquote| | ||
The position init code is a little complex, to allow for starting on a carrier and some other cases, and ideally we would do it from script, but unfortunately there's some technical limitations on doing that. (Not insurmountable, but not quick either). Adding more cases to the position-init code is certainly doable - one suggestion I made some time ago, is when MP is active, to default to starting at a free parking position instead of on a runway. (When no startup position is provided at all). This would avoid people accidentally starting on the runway in MP events, which would be a big usability win. | The position init code is a little complex, to allow for starting on a carrier and some other cases, and ideally we would do it from script, but unfortunately there's some technical limitations on doing that. (Not insurmountable, but not quick either). Adding more cases to the position-init code is certainly doable - one suggestion I made some time ago, is when MP is active, to default to starting at a free parking position instead of on a runway. (When no startup position is provided at all). This would avoid people accidentally starting on the runway in MP events, which would be a big usability win. | ||