Portal:Developer

2015-09-19T10:14:41Z

Lexy0202: minor grammatical correction and update of moved URL for issue tracker

{{Main page/Header
|title=Welcome to the developer portal
|introduction=Please visit [http://forum.flightgear.org our forum] if you cannot find what you're looking for.
|rightbox=

|rightcolumn1= </div>
[[FlightGear and Git|Development repository status]] 
<center style="padding-top:.9em;">{{GitStatus}}</center>

|rightcolumn2= </div>
Getting started 

[[How the FlightGear project works]] 
[[Howto: Understand the FlightGear development process|The development process]] · [[Release plan]] 
[[Building FlightGear]] · [[FlightGear and Git|Git]] · [[FlightGear Build Server|Build server]] 
[[Property tree]] · [[File formats]] · [[Tools of the Trade]]

|rightcolumn3= </div>
General 

[[Long Term Goals|Long term goals]] · [[:Category:Popular Community Requests|Popular Ideas]] · [[Google Summer of Code]] 
[[Project Infrastructure Enhancements|Project infrastructure enhancements]] 
[[Improving Glider Realism|Improving glider realism]] / [[Improving Helicopter Realism|helicopter realism]] 
[[Howto:Set up a multiplayer server|Setting up a multiplayer server]] · [[FlightGear Expo Checklist|Expo checklist]]

|rightcolumn4= [[File:Portal aircraft.png|40px]]</div>
[[Portal:Developer/Aircraft|Aircraft]] 

[[Howto: Make an aircraft|Making an aircraft]] · [[Flight Dynamics Model|Flight dynamics model]] 
[[Howto: 3D Aircraft Models|3D aircraft models]] · [[Howto: Edit a livery|Liveries]] · [[:Category:Aircraft Resources|Resources]] 
[[Soaring instrumentation sdk]] · [[Creating instruments for FG|Creating instruments]] · [[System dependent instruments|System dependent instruments]] 
[[Howto: Design an autopilot|Designing an autopilot]]

|rightcolumn5= [[File:Nuvola apps kaboodle.png|40px]] </div>
Animations 

[[Howto: Animate models|Animate models]] · [[Howto: Illuminate faces|Illuminate objects]] 
[[Howto: Animate gear scissors|Gear scissors]] · [[Tracking animation]] 
[[Howto: Make a clickable panel|Clickable panels]] · [[Knob / slider animation]]

|rightcolumn6= [[File:Portal developer.png|40px]] </div>
Core 

[[:Category:FlightGear Core developers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] 
[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Nasal/CppBind|Adding scripting bindings]] 
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]] 
[[Built-in Profiler]] · [[Howto:Extend Nasal]] · [[Howto:Using Ada in FlightGear]] (updated!) 
[[Howto:Use Property Tree Objects]] · [[Code cleanup]] 
[[FlightGear-Points of Interest]] · [[Request for comments]] 
[[OpenSceneGraph]] · [[Rendering system improvements]]

|rightcolumn7= [[File:Portal scenery.png|40px]] </div>
[[Portal:Developer/Scenery|Scenery]] 

[[Procedural Texturing]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]] 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]] 
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]] 
[[Interactive traffic]]

|rightcolumn8= [[File:Nasallogo3.png|40px]] </div>
[[Nasal|Scripting]] 

[[Nasal FAQ|Frequently asked questions]] · [[Howto:Write simple scripts in Nasal|Writing simple scripts]] 
[[Nasal for C++ programmers]] · [[Nasal Variables|Variables and their types]] 
[[Nasal Conditionals|Conditionals]] · [[Nasal Loops|Loops]] · [[Nasal Operators|Operators]] · [[Nasal Console|In-sim console]]

|rightcolumn9= [[File:Animation Icon.png|40px]] </div>
Effects and shaders 

[[Shaders]] · [[Project Rembrandt]] 
[[Howto:Shader Programming in FlightGear|Shader programming in FlightGear]] 
[[Shader Coding - Best Practices|Best Practices]] · [[GLSL Shader Programming Resources|GLSL resources]]


|sections=

{{Main page/Leftbox|title=Put a piece of yourself into FlightGear!
|contents=In FlightGear, "development" is [[Howto:Understand the FlightGear development process|anything that improves the project]]. So, it's not just code-related [[Howto:Start core development|core development]]. There's also [[Portal:Developer/Scenery|scenery development]], [[Portal:Developer/Aircraft|aircraft development]] and all the stuff you can see in the column here on the left. If you want an extended overview, check out the [[Volunteer]] page.

Actually that's not all you can contribute. There's also documentation, with the [[FlightGear Manual]]... and this wiki of course! To contribute to the wiki, head off to the [[Portal:Wiki|Wiki Portal]]. There's a lot to do there too.

If you want to get in touch with other developers, register an account at the [http://forum.flightgear.org/viewforum.php?f=18 forum], and for core development subscribe to the [[mailing list]] too and consider visiting the [http://sourceforge.net/p/flightgear/codetickets/ issue tracker].

Remember: we might call it volunteering, but what should drive you is [[How the FlightGear project works|the fun of doing something]].
}}

{{Main page/Leftbox|title=For core developers
|contents=Visit [[:Category:Core development projects]] to see a list of currently ongoing projects!
See [[:Category:Developer Plans]] to see a list of developer plans for the upcoming release.
See [[request for comments]] for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress (admittedly a little outdated meanwhile).

'''Help needed:'''

Creating an integrated [[Canvas]] based GUI launcher/package manager {{Issue|1295}}:

{{cquote|For aircraft, the system supports aircraft dirs, there is the package manager code which works but is currently unused, which can download and extract zipped aircraft. This needs a GUI but thanks to the new reset architecture we can finally build this GUI inside FG - i.e an ‘aircraft chooser’ UI - however I am find building such a UI rather outside my comfort zone. If anyone would like to help in this area, let me know.<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32239376/
|title=size of flightgear-data
|author=James Turner |date= 2014-04-17 18:23:24}}</ref>|James Turner}}

The [[YASim]] FDM is looking for a new maintainer:

{{cquote|There are some pending merge requests[http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/533DBD01.9040802%40sol2500.net/#msg32183541] to add some YASim features, but we have an issue that since none of the current C++ developers own, or are experts in YASim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.

Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)

So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too,
if people are new to C++), and providing we have some assurance that a representative sample of YASim aircraft are unchanged or improved by the patch.
Suggestions for that means in practice, are most welcome!

Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}

{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my latencies here are measured in weeks.Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}

<references/>

}}

{{Main page/Leftbox|title=Coding Help Needed! (Updated 11/2013)
|contents=
* {{Pending}} [[World Scenery 3.0 roadmap]]
* {{Pending}} [[Reset & re-init]] and [[Fixing Presets]]
* {{Pending}} [[USB HID Support]] - mapping USB/HID devices onto the property tree
* {{Pending}} [[Project Rembrandt#TODO List|Project Rembrandt (Todo List)]] (Shadows/Deferred Rendering: OpenGL/OSG, C++)
* {{Pending}} [[Canvas Development]] - discusses possible future Canvas additions
* {{Pending}} [[Canvas Properties#Planned Features|Canvas Project (Planned Features)]] (fully scriptable 2D rendering API)
* {{Pending}} [[Canvas Widgets#Missing_.2F_Todo|Canvas Widgets (Missing Features)]] (Canvas GUI layer for scriptable widgets)
* {{Pending}} [[Howto:Use Property Tree Objects|Depreciate tied properties and use PropertyObjects instead]]
* {{Pending}} [[A_local_weather_system#Feature_requests_on_the_C.2B.2B_side|Local weather system Improvements]] (Requested C++ Changes)
* {{Pending}} [[Subsystem-level Memory Tracking for FlightGear]]
* {{Pending}} [[How the Nasal GC works|Fixing the Garbage Collector]] (the GC in [[Nasal]] needs to be improved)
* {{Pending}} [[CompositeViewer Support|Switching to osgViewer::CompositeViewer]] (multiple scenery cameras and moving maps)
* {{Pending}} [[Performance Database via FDM]] - implementing VNAV support for FlightGear aircraft
* {{Pending}} [[TerraGear scenery build server]]


}}

{{Main page/Leftbox|title=Wanted: interview candidates
|contents=Every month we try to include an interview with a contributor in the [[FlightGear Newsletter]]. Anyone contributing to FlightGear, in whatever way, is welcome to answer a few questions and write his/her own interview.

More info at [[FlightGear Newsletter: Interview]].
}}
}}

[[Category:Portals]]

[[es:Portal:Desarrollo]]
[[fr:Portal:Développeur]]
[[sr:Portal:Razvoj]]

FlightGear wiki - User contributions [en]

Portal:Developer