Portal:Developer

This article may require cleanup to meet the quality standards of the wiki. Please improve this article if you can.

Developer - User

The Developer Portal This portal is for developers contributing to FlightGear. If you wanna 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: Aircraft Scenery The FlightGear project is looking for organizations/individuals who would be willing to help sponsor a fulltime project coordinator/manager to help oversee the overall development process If you are interested in helping or have anything else to contribute to this issue, please subscribe to the the FlightGear Devel mailing list to discuss details. (Note that the FlightGear project can apply for free funding/sponsoring with nlnet-applications are to be sent here-you can help prepare a template for applying: Funding Application)

Current Efforts/Branches & Work in Progress FlightGear Package Manager (New! Alpha release of Java/XML package manager!) Walk View‎ (New! walk view code!) FlightGear Contest More... Latest Organizational Issues Project Infrastructure Enhancements 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 Pending Patches (2 listed for the moment) Segfaults - Reproducible Critical Bugs in FlightGear Showstoppers - Annoying Issues in FlightGear Background Info Programming Resources Compiling Building Flightgear Building Flightgear - Windows Building Flightgear - Mac OS X Building FlightGear Launch Control Building Terragear Keeping FlightGear (win32) up to date without compiling OpenSceneGraph Tools of the Trade Using TortoiseCVS with FlightGear Flightgear and Git Contributing Code Cleanup Contributor Repositories mirrors, branches and forks privately maintained by contributors Development Resources Extension Support Submitting Patches Technical Reports Code Internals Command Parameters FDM API File Formats Initialization Sequence Nasal scripting language Property Tree Subsystems UML Diagrams YASim 1.0.0 a/c names for command line

Todo Bugs Feature Requests / Proposals / Ideas FGFS Todo FlightGear Expo Checklist Long Term Goals Done Changes since 0.9.10 HowTos Add smooth shadows in Blender 3D Aircraft Models Add aircraft lights Edit a livery Illuminate faces Make a helicopter Set up a multiplayer server More... Instrumentation Creating instruments for FG Nasal scripting Nasal scripting language Writing simple scripts in "nasal" Walk View‎ Autopilot configuration FlightGear Autopilot (Theory, Configuration, and Tuning) Autopilot Tuning Resources 3D Modeling 3D Aircraft Models (howto) Aircraft Information Resources Model Import and Export Modeling - FAQ Modeling - Getting Started Modeling Resources Modeling - SketchUp Normals and Transparency Tutorial Blender3D Modeling Scenery Blender Ground Signs Tutorial Placing 3D Objects with the UFO Signs (placing and explanation) Using Terragear Using the Custom Scenery TerraGear Toolset Building Terragear-cs in Ubuntu Hardy

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 or prioritized by the FlightGear community. These RFC documents are however intended to hopefully help increase 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, refine and help develop new strategies to tackle the challenges presented in these RFCs.

• Autopilot Enhancements - enhancing the autopilot infrastructure.
• Backwards Compatibility Initiative - discussing possible ways to improve FlightGear's backwards compatibility.
• Multiplayer Enhancements - discussing possible steps to enhance FlightGear's Multiplayer support.
• 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.
• 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.
• Simplifying Aircraft Deployment - identifying potential steps to simplify deployment of FlightGear aircraft.