From FlightGear wiki
Revision as of 17:49, 20 August 2014 by Berkut (talk | contribs) (Created page with "{{Main page/Header |title=Dobrodošli na razvojni portal |introduction=Posetite [ naš Forum] ako ovde nemožete naći ono tražite. |rightbo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Dobrodošli na razvojni portal

Posetite naš Forum ako ovde nemožete naći ono tražite.

Put a piece of yourself into FlightGear!

In FlightGear, "development" is anything that improves the project. So, it's not just code related core development. There's also scenery development, 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 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 forum, and for core development subscribe to the mailing list too and consider visiting the issue tracker

Remember: we might call it volunteering, but what should drive you is the fun of doing something.

For 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:

Creating an integrated Canvas based GUI launcher/package manager ticket #1295:

Cquote1.png 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.[1]
— James Turner

The YASim FDM is looking for a new maintainer:

Cquote1.png There are some pending merge requests[1] 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.[2]
— James Turner
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.[3]
— Andy Ross
  1. James Turner (2014-04-17 18:23:24). size of flightgear-data.
  2. James Turner (Fri, 05 Oct 2012 03:54:43 -0700). YASim and documentation.
  3. 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.

Status razvojne riznice

Тренутно издање: 2020.3 (6 нов 2020)
Следеће издање: 2021.1 (-143 days од сада)
Погледајте релеасе план за детаље

Prvi koraci
Kako FlightGear projekat radi
Razvojni Proces · Plan izdanja
Gradjenje FlightGear-a · Git · Gradi server
Property tree · File Formati · Tools of the Trade

Dugoročni ciljevi · Popularne Ideje · Google Sumiranje koda
Poboljšanja projektne infrastrukture
Poboljšanje realističnosti jedrilica / Realističnost Helikoptera
Osnivanje multiplayer server-a · Expo checklist

Portal aircraft.png

Pravljenje letelice · Model dinamike leta
3D models letelica · Skinovi · Resursi
Soaring instrumentation sdk · Kreiranje instrumenata · Instrumenti zavisni od sistema
Dizajniranje auto-pilota

Nuvola apps kaboodle.png

Animacija modela · Osvetljenje objekata
Stajni trap · Praćenje animacije
Click panel · Taster / klizač animacija

Portal developer.png

Lista glavnih programera · Planovi Programera · Projekti
Prvi koraci · Programski resursi · Dodavanje veza skripte
Dodavanje fg komandi · Kreiranje podsistema
Built-in Profiler · Kako da:Priširite Nasal
Kako da:Koristite Property Tree Objekte · Čišćenje koda
FlightGear-Tačke od interesa · Zahtev za komentare
OpenSceneGraph · Poboljšanja sistema rendera

Portal scenery.png

Proceduralno Teksturisanje
Postavljanje objekata · Aerodromski znakovi
Konvertovanje iz X-Plane/MSFS
Napravi aerodorm · Generisanje terena
Interaktivni saobraćaj


Nasal skripte
Često postavljana pitanja · Pisanje jednostavnih skripti
Nazal za C++ programere · Promenljive i njihovi tipovi
Nazal Kondicional · Nazal Petlje · Nazal Operatori · In-sim konzole

Animation Icon.png

Effects and shaders
Shaders · Project Rembrandt
Shader programming in FlightGear
Best Practices · GLSL resources