18
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Implementing VNAV support in FlightGear (view source)
Revision as of 03:53, 2 December 2013
, 2 December 2013→Methods for implementing VNAV
No edit summary |
Flyingsolo (talk | contribs) |
||
| Line 119: | Line 119: | ||
* an agreed standard of tests applied to all airplanes (climb/descend profiles with different configurations) | * an agreed standard of tests applied to all airplanes (climb/descend profiles with different configurations) | ||
* an agreed format(data file structure) in which this data is formated, or using an improved database approach and provide mapping via a DBMS for a changing file structure | * an agreed format(data file structure) in which this data is formated, or using an improved database approach and provide mapping via a DBMS for a changing file structure | ||
* an agreed property inside flightgear to hold this data (a single property won't suffice) | * an agreed property *list inside flightgear to hold this data (a single property won't suffice) | ||
* an interface for flightgear to query the data file through the DBMS (FlightGear's scripting language Nasal does have SQLite bindings, another option would be a flat text/XML file) | * an interface for flightgear to query the data file through the DBMS (FlightGear's scripting language Nasal does have SQLite bindings, another option would be a flat text/XML file) | ||
* a way of implementing this data into the aircraft's model(usually xml file) | * a way of implementing this data into the aircraft's model(usually xml file) | ||