Portal:Developer

Developer - User - Pilot

The Developer Portal This portal is for developers contributing to FlightGear. If you want to help with FlightGears development, it's a good idea to subscribe yourself to the FlightGear devel mailing list. The list archive is also available and should be searched before posting the same question. Please choose a sub-portal: 3D Modelers Aircraft Scenery

Events, Efforts/Branches & Work in Progress FlightGear Package Manager (Alpha release of Java/XML package manager (2008)) Walk View‎ More... Latest Organizational Issues FlightGear Build Server Project Infrastructure Enhancements Source Code Management Issues Google Summer of Code Candidate Projects - application template to allow community members to prepare a possible application to decrease the effort required to actually apply Programming Resources Tools of the Trade Improvement Initiatives Improving Helicopter Realism Improving Glider Realism Usability Improvements (list of related feature requests) More... Compiling Howto: Build FlightGear with NetBeans using CMake Building FlightGear - Linux Building FlightGear - Mac OS X Building FlightGear - Windows Building FlightGear Launch Control OpenSceneGraph FlightGear and Git FlightGear Package Manager Todo FlightGear Expo Checklist Long Term Goals

Contributing Howto: Understand the FlightGear development process Howto: Start core development Release plan Howto: Add new fgcommands to FlightGear Howto: Create new subsystems Howto: Work with the Property Tree API Code Cleanup Code Internals Command Parameters File Formats Initialization Sequence Nasal scripting language Property Tree UML Diagrams YASim HowTos Set up a multiplayer server More... Nasal scripting Improving Nasal Nasal FAQ Nasal scripting language Nasal Snippets Nasal Modules Nasal Style Guide Writing simple scripts in "nasal" Walk View‎ Howto: Nasal in scenery object XML files Howto: Extend Nasal

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 prioritized or generally endorsed by the FlightGear community. These RFC documents are however intended to hopefully help increase and maintain awareness of long-standing issues and challenges affecting FlightGear's evolution and overall development progress in order to solicit community feedback about possible approaches to address these in an efficient and structured fashion. Anybody is welcome to comment on, help refine and develop new strategies to tackle the challenges presented in these and future RFCs.

• A local weather system - improving the FlightGear weather system to make it more configurable and feature rich
• An Integrated AI Traffic System - improving the integration of the AI traffic system with the rest of FlightGear
• Autopilot Enhancements - enhancing the autopilot infrastructure.
• Backwards Compatibility Initiative - discussing possible ways to improve FlightGear's backwards compatibility.
• Canvas Properties - discussing ways to add a 2D drawing API to FlightGear that is property driven
• CDI instrument - collection of information relating to creating a formal CDI instrument in FG
• Decoupling the AI Traffic System - discussing possible ways to decouple the AI traffic system from FlightGear in order to improve overall performance and synchronize AI state across multiplayer clients
• Multiplayer Enhancements - discussing possible steps to enhance FlightGear's Multiplayer support.
• Modularizing, parallelizing and distributing FlightGear - splitting fgfs into distinct components that are to be run as separate processes using the property tree for IPC purposes in order to leverage SMP platforms and distribution/remoting to help FlightGear become more scalable.
• 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.
• FlightGear Headless - discussing required steps to enable FlightGear to be used as its own regression testing framework
• FlightGear Sessions - discussing possible steps to finally allow aircraft to be reliably switched at runtime.
• Potential alternatives to Plib's PUI library - collection of cross-platform GUI libraries that work with OpenGL
• Formalizing Aircraft Status - discussing suggestions about how to more properly describe aircraft development status.
• Keyboard function priority list - reorganizing FlightGear keybindings.
• Next Generation Scenery - revamping the FG scenery engine.
• Property Tree Reorganization - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions).
• Recommended Property Tree Enhancements - discussing possible property tree enhancements to help ensure integrity of crucial runtime state.
• Recommended Project Policies - discussing recommended policies for future contributions to the project.
• Redesigning the Replay System - addressing the restrictions in the current implementation of the replay system
• Remote Properties - introduces a small but powerful extension to the property tree in order to allow properties to be maintained in a different (remote) instance of a property tree, that is transparently accessed using a network socket.
• Simplifying Aircraft Deployment - identifying potential steps to simplify deployment of FlightGear aircraft.