Portal:Developer: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 81: Line 81:
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).
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:''' SimGear 2.11+ now has experimental support for a libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature:
'''Help needed:''' The [[YaSim]] FDM is looking for a new maintainer:


{{cquote|<nowiki>First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40191.html|title=TerraSync libSVN replacement testing|author=James Turner|date=Tue, 11 Jun 2013 08:58:20 -0700}}</ref>|James Turner}}
{{cquote|There are some pending merge requests 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.


{{cquote|<nowiki>So, as I've previously asked before, I really need people running from 'next'
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)
to try with -DSG_SVN_CLIENT=1 when configuring SimGear, move their existing
TerraSync dir out the way, and test, test, test. I'm sure the new code isn't
100% trouble free (in particular I think there is still the occasional time
when it gets stuck not doing any more downloads until FG is restarted), but I
really don't want to move forwards with the code until I have a bit more
assurance it's not going to make everyone's setup crash 80% of the time, which
is what some people have reported.


Note this applies even if you 'don't use' terrasync since the SVN sync engine
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,
is going to be used for other pieces of data as soon as it's stable. (I will be
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.
adding a new preference to globally control whether FG works in online/offline
Suggestions for that means in practice, are most welcome!
mode, of course)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40775.html|title=<nowiki>[Flightgear-devel] Built-in Svn client code crashing</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Fri, 20 Sep 2013 09:54:38 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}}
 
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/>
<references/>

Revision as of 19:47, 3 December 2013

 

Welcome to the developer portal

Please visit our forum if you cannot find what you're looking for.
 
 

Get involved!

If you would like to help with FlightGear's development, it's a good idea to subscribe yourself to the FlightGear development mailing list. Use the list or the FlightGear issue tracker to get in touch with fellow FlightGear core developers.

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: The YaSim FDM is looking for a new maintainer:

Cquote1.png There are some pending merge requests 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.[1]
— James Turner
 Cquote2.png
Cquote1.png 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.[2]
— Andy Ross
 Cquote2.png
  1. ↑ James Turner (Fri, 05 Oct 2012 03:54:43 -0700). YASim and documentation.
  2. ↑ Andy Ross (Fri, 05 Oct 2012 03:54:43 -0700). YASim and documentation.
 
 

Coding Help Needed! (Updated 11/2013)


 
 

Wanted: interview candidates

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.
Development repository status
Current release: 2020.3.19 (18 Oct 2023)
Next release: 2020.3.20
See release plan for details.

Getting started
How the FlightGear project works
The development process · Release plan
Building FlightGear · Git · Build server
Property tree · File formats · Tools of the Trade

General
Long term goals · Google Summer of Code
Project infrastructure enhancements
Improving glider realism / helicopter realism
Setting up a multiplayer server · Expo checklist

Nuvola apps kaboodle.png

Aircraft
Making an aircraft · Flight dynamics model
3D aircraft models · Liveries · Resources
Creating instruments · System dependent instruments
Designing an autopilot

Portal developer.png

Animations
Animate models · Illuminate objects
Gear scissors · Tracking animation
Clickable panels · Knob / slider animation

Portal aircraft.png

Core
List of Core Developers · Developer Plans · Projects
Getting started · Programming resources · Adding scripting bindings
Adding fgcommands · Creating subsystems
Built-in Profiler · Howto:Extend Nasal
Howto:Use Property Tree Objects · Code cleanup
FlightGear-Points of Interest · Request for comments
OpenSceneGraph · Rendering system improvements

FlightGear Scripting with Nasal
Frequently asked questions · Writing simple scripts
Nasal for C++ programmers · Variables and their types
Conditionals · Loops · Operators · In-sim Console

Portal scenery.png

Scenery
Procedural Texturing
Placing objects · Airport signs
Converting from X-Plane/MSFS
Making an airport · Generating terrain
Interactive traffic

Retrieved from "https://wiki.flightgear.org/w/index.php?title=Portal:Developer&oldid=65151"