FlightGear Newsletter October 2012
|
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.
Development news
Note to all contributors: Please also copy your newsletter additions to the changelog of the upcoming release: Changelog_3.0.0.
FGRadar: Standalone ATC client
Since mid-summer, forum user "Icecode GL" has been working on a free and open-source stand-alone ATC client written in C++, totally from scratch with the help of the GTKmm GUI toolkit (http://www.gtkmm.org/en/) and the Cairo 2D graphics library ( http://www.cairographics.org/). He has started this as a project to learn from and take some practice while developing it at the same time, as well as satisfying his needs of a complete and more professional ATC client for FlightGear.
FGRadar is a free, open-source and stand-alone air traffic control (ATC) client for FlightGear. It uses GTKmm (GTK+ port for C++) and Cairo to perform drawing operations.
If someone wants to join the project, give ideas, requests or opinions, feel free to do so. The repository is here: https://gitorious.org/fgradar
Random Buildings
Project Rembrandt
Canvas System
High Level Architecture
FlightGear an Android
Usability Improvements
Mailing list digest
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)
Forum digest
Git digest
Getting involved as a programmer
Please see Howto:Start core development
Release ChangeLog
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.
Interview with a contributor (NAME)
In each edition we have an interview with a contributor. Suggestions for possible questions are available on interview questions, you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the list of interview volunteers! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.
- How long have you been involved in FlightGear?
- What are your major interests in FlightGear?
- What project are you working on right now?
- What do you plan on doing in the future?
- Are you happy with the way the FlightGear project is going?
- What do you enjoy most about developing for FlightGear?
- Are there any "hidden features" you have worked on in FlightGear that new users may miss?
- What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?
More questions are being collected here: Interview questions.
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX
Snapshot releases
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at the issue tracker.
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found at the forum.
Translators required
The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at Help:Translate. | |
Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit Help:Übersetzen an. | |
De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij Help:Vertalen. |
Nasal for newbies
New software tools and projects
FlightGear addons and mods
In the hangar
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at Google Docs. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at Formalizing Aircraft Status. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
New aircraft
Updated aircraft
Liveries
This month the livery database reached several milestones:
- the 800th livery was added.
- the 100th author submitted a livery.
- a livery for the 100th aircraft was commited.
A big "thank you" to all painters!
Scenery corner
Airports
Aircraft of the month
Airport of the month
Screenshot of the month
Suggested flights
Aircraft reviews
Wiki updates
New articles
<DynamicArticleList>
type=new count=10
</DynamicArticleList>
New aircraft articles
<DynamicArticleList>
type=new count=10 categoryRoot=Aircraft
</DynamicArticleList>
Most popular newsletters
<DynamicArticleList>
type=hot count=5 categoryRoot=FlightGear Newsletter
</DynamicArticleList>
Community news
FlightGear on YouTube
New tutorials and screencasts
Forum news
Multiplayer
Virtual airlines
Easy-GO This is a new one... We have three founders - DARK-L, itray, and myself. VAs typically have to make the decision between realism and plain fun. We have implemented both ideas in one airline. Our goal is pretty big, we want to satisfy many categories of pilots. We have a realistic side, containing strictly scheduled and realistic routes using appropriate aircraft for each destination. Our revenue system is based on 6 different static and dynamic factors and all flights must be flown on time with the stated aircraft. On the fun side routes are unscheduled and pilots can fly whatever and whenever they want. The routes flown will be added to the general routes page which will freely evolve. This operation is 100% separate from the realistic operation. We have our hub at SFO so we can meet up and do spontaneous group flights :) - which so far has happened a lot. See the Flightgear VA forum for more details...
FlightGear events
Useful links
And finally ...
Contributing
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.
For ideas on starting to contribute to FlightGear, you may want to check out: Volunteer.
To learn more about how the project works, please see this short essay written by Thorsten.
Call for volunteers
- The FGRadar project (standalone ATC client) is looking for people to join the project, give ideas, requests or opinions.
- The Flightgear On Android team is looking for testers
- The Target4Today team is looking for volunteers to help improving FlightGear's combat support
- The OpenRadar project is looking for a new maintainer.
- The FGFSPM (FlightGear Package Manager) is looking for a new maintainer.