1
0
Fork 0

README.add-ons: use explicit node typing in the sample metadata file and more spacing

The explicit typing shouldn't change anything for the parsing code in
flightgear/src/Add-ons/AddonManager.cxx, because for each field, this
code knows the correct type and explicitly asks for it (and only once),
but external code might include addon-metadata.xml in some prop tree,
and then the explicit typing is likely to give better results.
This commit is contained in:
Florent Rougon 2017-12-09 13:49:20 +01:00
parent fe3911a2d8
commit 33bc7eabb3

View file

@ -104,16 +104,32 @@ hypothetical add-on called “Flying Turtle” distributed by Joe User:
<PropertyList>
<format-version type="int">1</format-version>
<addon>
<identifier>user.joe.FlyingTurtle</identifier>
<name>Flying Turtle</name>
<version>1.0.0rc2</version>
<short-description>Allow flying with new foobar powers.</short-description>
<long-description>This add-on enables something really great involving turtles...</long-description>
<min-FG-version>2017.4.0</min-FG-version>
<max-FG-version>none</max-FG-version>
<home-page>https://example.com/quux</home-page>
<download-url>https://example.com/quux/download</download-url>
<support-url>https://example.com/quux/support</support-url>
<identifier type="string">user.joe.FlyingTurtle</identifier>
<name type="string">Flying Turtle</name>
<version type="string">1.0.0rc2</version>
<short-description type="string">
Allow flying with new foobar powers.
</short-description>
<long-description type="string">
This add-on enables something really great involving turtles...
</long-description>
<min-FG-version type="string">2017.4.0</min-FG-version>
<max-FG-version type="string">none</max-FG-version>
<home-page type="string">
https://example.com/quux
</home-page>
<download-url type="string">
https://example.com/quux/download
</download-url>
<support-url type="string">
https://example.com/quux/support
</support-url>
</addon>
</PropertyList>