580
edits
Aircraft-set.xml: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 153: | Line 153: | ||
</maintainers > | </maintainers > | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==== Tags ==== | |||
The [[Catalog metadata|tag system]] allows systems to categorise aircraft, for example allowing more advanced searches in the future. Tags allow better feedback to the user when interacting with your aircraft - for | |||
example if the aircraft is tagged as towable, a glider, or a helicopter, the startup behaviour can be customised. | |||
Most importantly, set the following tags if appropriate: | |||
*. glider | |||
* helicopter | |||
* floats | |||
* skis | |||
* seaplane | |||
* airship | |||
* amphibious | |||
* vtol | |||
These tags are the most helpful in customising the start-up experience based on the type of aircraft. (Especially, which starting locations are offered / preferred when searching) | |||
==== Urls ==== | |||
Aircraft can list significant URLs, such as their home page, support forum or code repository. Again the format matches that uses for add-ons: | |||
<syntaxhighlight lang="xml"> | |||
<urls> | |||
<home-page>http://www.flightgear.org</home-page> | |||
<wikipedia>https://en.wikipedia.org/wiki/Cessna_172</wikipedia> | |||
<support>http://forum.flightgear.org</support> | |||
</urls> | |||
</syntaxhighlight> | |||
The support URL is perhaps the most important, to direct users to a forum or bug-tracker where they can ask questions or report issues with the particular aircraft. | |||
==== Previews ==== | ==== Previews ==== | ||