2,561
edits
Aircraft rating system: Difference between revisions
Jump to navigation
Jump to search
m
→Overall Rating/Status
| Line 124: | Line 124: | ||
=== Challenges === | === Challenges === | ||
For some components (like FDM configs, 2D panels, 3D cockpits, exterior models or liveries) it may be possible to specify multiple separately referenced files in one single *-set.xml file, in these cases it would seem more appropriate to also track their development status separately in these files, rather than in the top-level aircraft file, this would make sure that the development status is really tracked on a per-component basis. So, that sharing aircraft resources still works properly while retaining component status information. | For some components (like FDM configs, 2D panels, 3D cockpits, exterior models or liveries) it may be possible to specify multiple separately referenced files in one single *-set.xml file, in these cases it would seem more appropriate to also track their development status separately in these files, rather than in the top-level aircraft file, this would make sure that the development status is really tracked on a per-component basis. So, that sharing aircraft resources still works properly while retaining component status information. | ||
== Ease of Deployment == | |||
In order to simplify the introduction of the aforementioned concept to store aircraft status information, it might make sense to consider requesting aircraft authors/maintainers by convention to specify said status information externally, in a separate PropertyList-encoded XML file, that is then only referenced in a corresponding include attribute (i.e. <aircraft-status include="ac-status.xml"/>. | |||
While this doesn't make any conceptual difference, it helps to to keep this structured information in a separate place. | |||
Enforcing this convention could simplify the required parsing process in certain situations and would thus not only help creating web-based search/sort frontends using such status information attributes, but would also enable the wealth of existing standalone FlightGear launchers (most of which do not link to SimGear, and may thus not easily process PropertyList-XML files) to be able to easily deal with this information without having to parse the whole *-set.xml file, rather it would become possible to just concentrate on parsing said "aircraft-status.xml" file for certain purposes. | |||
== Overall Rating/Status == | == Overall Rating/Status == | ||