Portal:Developer: Difference between revisions
No edit summary |
No edit summary |
||
Line 56: | Line 56: | ||
=== Done === | === Done === | ||
* [[ Changes since 0.9.10 ]] | * [[ Changes since 0.9.10 ]] | ||
=== 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 | |||
=== Miscellaneous === | |||
* [[ Glass Cockpit Projects ]] | |||
* [[ Copyright Inquiry ]] | |||
* [http://www.cafepress.com/fgfs_gear FlightGear - Gear] | |||
* [[ Sign Specification Proposal ]] |
Revision as of 17:53, 1 March 2008
Developer Documentation
Latest Organizational Issues
Background Info
Current Efforts/Branches & Work in Progress
TODO: use to document and keep track of official branches (i.e. plib/OSG) and local efforts/projects of individual contributors.
- XML Particles
- Random Trees for FlightGear
- ATC Enhancements
- Leak Reduction
- TileProxy for FlightGear?
- TerraGear fork
- FlightGear 1.0 Live CD
- Complete FlightGear Scenery on one DVD
Compiling
- Building Flightgear
- Building Flightgear - Windows
- Building Terragear
- OpenSceneGraph
- Building FlightGear Launch Control
HowTos
Contributing
Code Internals
- Property Tree
- Subsystems
- UML Diagrams
- Commands
- FDM API
- Nasal scripting language
- File Formats
- Initialization Sequence
Todo
Done
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