2,561
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
m
→Possible Steps
m (→Possible Steps) |
|||
| Line 31: | Line 31: | ||
# Delete (Uninstall) | # Delete (Uninstall) | ||
Installation involved checking if the aircraft exists (better to pull the list of available aircraft to allow user selection). We should check for version compatibility of the install FlightGear binary. If a aircraft is not compatible with the current version of FlightGear, do not allow the installation of it. | Installation involved checking if the aircraft exists (better to pull the list of available aircraft to allow user selection). We should check for version compatibility of the install FlightGear binary (as of 03/2008, the FlightGear binary fgfs doesn't yet provide any sort of version information). If a aircraft is not compatible with the current version of FlightGear, do not allow the installation of it. | ||
Updating an aircraft | Updating an aircraft involves checks if the aircraft is installed and then comparing the installed version with the latest version on a server. if the versions are the same, alert the user that the versions are the same and no update will occur. | ||
''Note:'' While explicit versioning (in XML files) may be one way to tackle the compatibility issue, another one might be to to read in both *-set.xml files and directly compare the resulting SGPropertyNode* structure, this could tell if the XML contents are identical. To do the same for resources included via XML files (i.e. textures, sounds, 3D models etc), one could calculate a simple CRC of each included file. | |||
Deleting an aircraft is even easier as we may not need to talk to the server. Instead we check if the aircraft is installed and should check to ensure that there are no dependencies for the aircraft. An example of which is an aircraft that makes use of another aircrafts instruments and is not centrally installed. | Deleting an aircraft is even easier as we may not need to talk to the server. Instead we check if the aircraft is installed and should check to ensure that there are no dependencies for the aircraft. An example of which is an aircraft that makes use of another aircrafts instruments and is not centrally installed. | ||