20,741
edits
m (Link to special directory articles) |
No edit summary |
||
Line 6: | Line 6: | ||
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. | ||
Most configuration files in FlightGear are XML-encoded | Most configuration files in FlightGear are XML-encoded property lists. PropertyList-encoded XML files use a subset of XML to map the property tree to XML space and vice versa. 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. | ||
To work with PropertyList-XML files, you can use various means, such as: | |||
* fgcommands | |||
* Nasal (props.nas, io.nas) | |||
* C++ APIs | |||
The root element of each file is always named <PropertyList>. Tags are almost always found in pairs, with the closing tag having a slash prefixing the tag name, i.e </PropertyList>. The exception is the tag representing an aliased property. In this case a slash is prepended to the closing angle bracket. | The root element of each file is always named <PropertyList>. Tags are almost always found in pairs, with the closing tag having a slash prefixing the tag name, i.e </PropertyList>. The exception is the tag representing an aliased property. In this case a slash is prepended to the closing angle bracket. | ||
Line 63: | Line 69: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
For further information please refer to [[$FG_ROOT]]/Docs/README.introduction and [[$FG_ROOT]]/Docs/README.properties. | |||
== Also see == | |||
* http://flightgear.org/forums/viewtopic.php?f=18&t=19503 | |||
[[Category:XML]] | [[Category:XML]] | ||
[[Category:Property Tree]] | [[Category:Property Tree]] |