20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Objective
| Line 22: | Line 22: | ||
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, 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: | |||
<syntaxhighlight lang="xml"> | |||
<runlevels> | |||
<runlevel n="0"> | |||
<subsystem> | |||
<name>sound</name> | |||
<property-signal>/runlevels/signals/sound</property-signal> | |||
</subsystem> | |||
<subsystem> | |||
<name>autopilot</name> | |||
<property-signal>/runlevels/signals/autopilot</property-signal> | |||
</subsystem> | |||
<subsystem> | |||
<name>route-manager</name> | |||
<property-signal>/runlevels/signals/route-manager</property-signal> | |||
</subsystem> | |||
</runlevel> | |||
</runlevels> | |||
</syntaxhighlight> | |||
In addition, we'll want to declare subsystem dependencies in XML space, too - using "groups" which are resursively started - so that the "aircraft" group starts the ROUTE MANAGER, AUTOPILOT, FDM, TERRAIN subsystems recursively. | |||
== Ideas == | == Ideas == | ||