20,741
edits
PropertyList XML files: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Aliased properties: Clarifying that the aliases work both ways.) |
No edit summary |
||
| Line 2: | Line 2: | ||
Most configuration files in FlightGear are '''PropertyList XML files''' using a subset of XML to encode lists and trees of [[Property Tree Intro|properties]] as XML. PropertyList-XML files are the main mechanism to populate the FlightGear property tree (or a sub branch of it) from XML files, but also to serialize (save) property tree/branch state to an XML file. XML attributes are mainly used as meta-directives for the property tree. | Most configuration files in FlightGear are '''PropertyList XML files''' using a subset of XML to encode lists and trees of [[Property Tree Intro|properties]] as XML. PropertyList-XML files are the main mechanism to populate the FlightGear property tree (or a sub branch of it) from XML files, but also to serialize (save) property tree/branch state to an XML file. XML attributes are mainly used as meta-directives for the property tree. | ||
{{Note| | |||
{{FGCquote | |||
|any --prop: argument can be just as well added to preferences.xml<br/> | |||
For that, you only need to understand how properties are mapped to XML space and vice versa: | |||
<syntaxhighlight lang="xml"> | |||
<sim> | |||
<foo n="0">teddy</foo> | |||
<foo n=1">tiger</foo> | |||
</sim> | |||
</syntaxhighlight>these can be expressed using <nowiki>--prop:/sim/foo[0]=teddy and --prop:/sim/foo[1]=tiger</nowiki> | |||
You should however not edit $FG_ROOT/preferences.xml directly - which should be considered readonly, instead, use $FG_HOME, which will be treated as an overlay (on top of $FG_ROOT/preferences.xml). | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=234298#p234298 | |||
|title=<nowiki>Re: Command line arguments with 3.4 launcher?</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Fri Mar 06</nowiki> | |||
}} | |||
}} | |||
}} | |||
For additional background information, you'll also want to refer to [[$FG_ROOT]]/Docs/README.introduction. | For additional background information, you'll also want to refer to [[$FG_ROOT]]/Docs/README.introduction. | ||