Portal:Developer: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 191: | Line 191: | ||
* [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions) | * [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions) | ||
* [[Autopilot Enhancements]] - enhancing the autopilot infrastructure | * [[Autopilot Enhancements]] - enhancing the autopilot infrastructure | ||
* [[Unified XML Processing API]] - Unifying XML Processing | |||
* [[Usability Improvements]] - improving FlightGear's usability | * [[Usability Improvements]] - improving FlightGear's usability | ||
=== Miscellaneous === | === Miscellaneous === |
Revision as of 21:31, 1 November 2008
|
|
|
Developer Documentation
RFC Topics
Clarification:In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).
Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is endorsed by the FlightGear community.
- Next Generation Scenery - revamping the FG scenery engine
- Keyboard function priority list - reorganizing FlightGear keybindings
- FlightGear Sessions - discussing possible steps to finally allow aircraft to be reliably switched at runtime
- Formalizing Aircraft Status - discussing suggestions about how to more properly describe aircraft development status
- Simplifying Aircraft Deployment - identifying potential steps to simplify deployment of FlightGear aircraft
- FDM engine feature standardization - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines
- FlightGear Glass Cockpits - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems
- Recommended Property Tree Enhancements - discussing possible property tree enhancements to help ensure integrity of crucial runtime state
- Backwards Compatibility Initiative - discussing possible ways to improve FlightGear's backwards compatibility
- Recommended Project Policies - discussing recommended policies for future contributions to the project
- Distributed Interactive Simulation - discussing possible steps to prepare FlightGear for HLA
- Property Tree Reorganization - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions)
- Autopilot Enhancements - enhancing the autopilot infrastructure
- Unified XML Processing API - Unifying XML Processing
- Usability Improvements - improving FlightGear's usability
Miscellaneous
Middleware & Base Package Development
Misc
Old work in progress links
- Warning! These links outdated, and some of these projects are finished:
- Efforts to create photo realistic scenery for FlightGear (Images: [1] [2] [3] [4]
- New aircraft model under development: Bede BD-5J
- F14-Tomcat aircraft model under development (F-14 released!)
- 787 being revamped
- LFLJ enhancements
- Free Walking mode for FlightGear using the Jeep vehicle in CVS
- Random Trees for FlightGear