Plan-zakalawe: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
=== Core properties and subsystems === | === Core properties and subsystems === | ||
* Support state-machines and some stateful expression in XML, to assist in building complex autopilots. | * Support [[State_machines|state-machines]] and some stateful expression in XML, to assist in building complex autopilots. | ||
* Work with Thorsten to re-write [[Reset & re-init|re-init]] to be a normal sim-startup | * Work with Thorsten to re-write [[Reset & re-init|re-init]] to be a normal sim-startup | ||
* USB-HID support, support for more HID devices | * USB-HID support, support for more HID devices | ||
Line 39: | Line 39: | ||
Using the above, more real-world GPS and FMC units can be created with Nasal to combine C++ core modules. | Using the above, more real-world GPS and FMC units can be created with Nasal to combine C++ core modules. | ||
* Create a generic Boeing CDU instrument, using the existing keypad model, but with the Canvas for the content. Various people have done parts of this, it's mostly a collating and refactoring job to get a solution that will scale to the 747-400, 777 and 737NG. Once that's done should discuss with Scott about any Airbus MCDU overlap (but likely not much is possible) | |||
=== NAV Display === | === NAV Display === |
Revision as of 17:52, 6 January 2013
Task List
Short term
- Improve airport-search performance for the release
Core properties and subsystems
- Support state-machines and some stateful expression in XML, to assist in building complex autopilots.
- Work with Thorsten to re-write re-init to be a normal sim-startup
- USB-HID support, support for more HID devices
- Add a hidapi backend to event-input code
- Write a loader to use existing joystick configs with event-input
- Remove PLIB JS dependency
- Migrate Nasal geo.Coord to be implemented in C++, and hence agree with SGGeodesy functions for courses, distances and so on.
Data / deployment
- Finish libSvn replacement code
- Support a list of 'hangar' repositories and synchronising aircraft from them
- Investigate making other optional base-package data be dynamically loaded
GUI / renderer
- Adapt the 2D panel code to build Canvas nodes
- Adapt the HUD code to build Canvas nodes - horrible task, but needs to be done
GPS / FMS / Route-planning
- Make a 'GPS receiver' instrument which models the physical GPS instrument
- Make an 'IRS' instrument which models an inertial reference platform
- Make a radio-positioning module (DME triangulation)
- GPS Restructuring
- Make the current 'GPS' instrument use a selectable position source - sim position, GPS, or INS.
- Break the C++ GPS into various discrete modules, which can be selected or combined from Nasal
- Bug-fix the various LNAV path controllers (DME arcs, DME intercepts)
- Move many current C++ GPS functions to Nasal (searching for waypoints, etc)
- Make a VNAV module for FMS use (compute climb and descent profiles)
Using the above, more real-world GPS and FMC units can be created with Nasal to combine C++ core modules.
- Create a generic Boeing CDU instrument, using the existing keypad model, but with the Canvas for the content. Various people have done parts of this, it's mostly a collating and refactoring job to get a solution that will scale to the 747-400, 777 and 737NG. Once that's done should discuss with Scott about any Airbus MCDU overlap (but likely not much is possible)
NAV Display
- Port to use the Canvas internally