580
edits
Plan-zakalawe: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (→GUI / renderer) |
No edit summary |
||
| Line 6: | Line 6: | ||
General areas I'm working on, or planning to work on | General areas I'm working on, or planning to work on | ||
=== Core properties and subsystems === | === Core properties and subsystems === | ||
| Line 38: | Line 39: | ||
* Extend the GPS code to support more flight-plan functions and en-route information | * Extend the GPS code to support more flight-plan functions and en-route information | ||
** Climb/descent computations, based on some aircraft performance data | ** Climb/descent computations, based on some aircraft performance data | ||
** Compute distances along the route path, including as offsets from any waypoint (this will allow aircraft authors to compute sane top-of-climb / top-of-descent locations, for example) | |||
* Allow performance data to be specific per-aircraft | * Allow performance data to be specific per-aircraft | ||
** Initially, basic information such as cruise speed, best climb rates, and so on | ** Initially, basic information such as cruise speed, best climb rates, and so on | ||
** Weight/balance tables | ** Weight/balance tables | ||
** Vspeeds computations | ** Vspeeds computations | ||
** Minimum runway length would allow lots of filtering to be smarter, replacing various hard-coded guesses in the NavDisplay and GPS | |||
=== NAV Display === | === NAV Display === | ||
* Improve API based on feedback from aircraft authors! | * Improve API based on feedback from aircraft authors! | ||
* Tested support for custom symbols specified via properties | |||
=== Miscellaneous === | === Miscellaneous === | ||
* command to load a property-tree XML from a web-service (TCP host + port). Initially to be sued to dynamically retrieve a server list from a server | |||
* HUD configuration improvements | |||