7
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
m
Stand Alone ATC Control Development (view source)
Revision as of 19:22, 2 December 2010
, 2 December 2010no edit summary
(Added section about ideal ATC client, based on my experience with IvAc) |
mNo edit summary |
||
| Line 240: | Line 240: | ||
Labels should keep the minimal information needed. That means that traffic under the ATC's control should display more info that traffic out of his control. | Labels should keep the minimal information needed. That means that traffic under the ATC's control should display more info that traffic out of his control. | ||
==Atlas as a starting point== | ==IvAc== | ||
IvAc is the ATC client of the IVAO network. It has all those elements and many many more. This piece of software was developed mainly by Kenny Moens and Filip Jonckers, two guys from the IVAO Software Development department (of which I was member some time ago). Filip is a real-life Air Traffic Controller. I've emailed them asking if they would be willing to give a hand. No reply yet. | |||
==Atlas as a starting point?== | |||
The way I see it, the only thing that Atlas can offer is the code that reads the scenery files. Personally I don't see an ATC client coming from an Atlas fork, or a highly customisable Atlas. In the beginning it can make things easier, but in the long run, I personally think that the structure of one project is different from the other, with different objectives. However, pieces of source code might be reused from Atlas, of course. | The way I see it, the only thing that Atlas can offer is the code that reads the scenery files. Personally I don't see an ATC client coming from an Atlas fork, or a highly customisable Atlas. In the beginning it can make things easier, but in the long run, I personally think that the structure of one project is different from the other, with different objectives. However, pieces of source code might be reused from Atlas, of course. | ||
| Line 246: | Line 250: | ||
There is another application in IVAO, called IvAe, which consists of a "Google Earthish" interface that shows all the pilots and controllers connected to the network, and you can retrieve much of their info (flight plans for pilots, ATIS for controllers, etc.). In this case, Atlas would be a good starting point for that. | There is another application in IVAO, called IvAe, which consists of a "Google Earthish" interface that shows all the pilots and controllers connected to the network, and you can retrieve much of their info (flight plans for pilots, ATIS for controllers, etc.). In this case, Atlas would be a good starting point for that. | ||
=Related= | =Related= | ||