20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Objective
| Line 66: | Line 66: | ||
Also, we want to work out the details to start up Nasal as early as possible, so that it can be used for most of the currently hard-coded initialization code, which isn't directly performance-critical - i.e. because it just sets up property defaults and parses/processes command line arguments. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg03390.html] | Also, we want to work out the details to start up Nasal as early as possible, so that it can be used for most of the currently hard-coded initialization code, which isn't directly performance-critical - i.e. because it just sets up property defaults and parses/processes command line arguments. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg03390.html] | ||
Nasal dependency resolution can be implemented analogous to how the import() command is done, possibly with some listener glue code. | Nasal dependency resolution can be implemented analogous to how the import() command is done in the Nasal repository [https://github.com/andyross/nasal/blob/master/lib/driver.nas#L163], possibly with some listener glue code. | ||
We probably want "run levels" (groups) to be defined in XML space, so that they can be easily modified and extended as required: | We probably want "run levels" (groups) to be defined in XML space, so that they can be easily modified and extended as required: | ||