20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Objective
No edit summary |
|||
| Line 18: | Line 18: | ||
Come up with a design to make subsystem initialization more explicit, and provide dependency resolution (run levels or system groups), so that subsystem initialization can be better controlled and explicitly enabled/disabled on an individual basis during startup. | Come up with a design to make subsystem initialization more explicit, and provide dependency resolution (run levels or system groups), so that subsystem initialization can be better controlled and explicitly enabled/disabled on an individual basis during startup. | ||
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. | |||
== Ideas == | == Ideas == | ||