20,741
edits
m (wiki links) |
No edit summary |
||
Line 1: | Line 1: | ||
Last updated: Sept. 2010 | |||
Status: Discussion | |||
This wiki is created upon the fired up debate and forum talks to create a centralized idea-bank, so the development proposals/goals can clearly be identified. All users are welcomed to contribute to this entry with their real or virtual world experience and simulator environment requirements for a stand alone [[ATC]] client for [[FlightGear]] [[Howto: Multiplayer|Multiplayer Network]]. | This wiki is created upon the fired up debate and forum talks to create a centralized idea-bank, so the development proposals/goals can clearly be identified. All users are welcomed to contribute to this entry with their real or virtual world experience and simulator environment requirements for a stand alone [[ATC]] client for [[FlightGear]] [[Howto: Multiplayer|Multiplayer Network]]. | ||
==Related content | =Minimum set of required features= | ||
* multiplayer support | |||
* display a radar-like screen | |||
* display data tags (altitude, callsign, course, sqwk code etc) | |||
=Other features and ideas = | |||
* [[FGCom]] integration | |||
=Customizing [[Atlas]] for use as an ATC client = | |||
In the scope of the ATC discussion, we have also talked about extending [[Atlas]] to use it as the foundation for a standalone ATC client, concentrating on a maximum degree of code reuse. | |||
It seems, that most of the existing atlas features could be used for ATC purposes, too. While only very few new features would be needed that would require changes to the C++ source code. This would make it possible to generalize the atlas code some more, so that using Atlas for ATC purposes would merely be a different "mode". | |||
For the time being, the most important new feature for atlas would be multiplayer support. | |||
Most of the other changes would be about making atlas features either more configurable (i.e. moving hard coded defaults out of the C++ source code into configuration files, plain text or XML based), or about provididing an option to completely disable other features. | |||
== Required enhancements == | |||
* multiplayer support | |||
* possibility to customize appearance for typical ATC use | |||
== Open questions == | |||
* should atlas connect to fgms as a server (relay?) or a client (observer), or should it just poll fgms for updates? | |||
* how about reusing data that is already sent to FlightGear (that would require a running FlightGear instance) | |||
=Related content= | |||
* [[OpenRadar]] | * [[OpenRadar]] | ||
== Open source == | |||
== Freeware == | |||
== Proprietary == |