20,741
edits
FlightGear Newsletter September 2012: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter September 2012 (view source)
Revision as of 12:21, 19 September 2012
, 19 September 2012→Canvas System
| Line 36: | Line 36: | ||
Ultimately, this will make it possible to re-implement existing features such as [[ATC-FS]], the [[Map]] dialog and even Brisa's [[Airport Diagram Generator]] or the [[Kelpie Flight Planner]] directly in FlightGear, using Nasal scripting and the [[Canvas]] system, without having to write any C++ code - so that people won't need to use external tools or programming languages to create such applications. | Ultimately, this will make it possible to re-implement existing features such as [[ATC-FS]], the [[Map]] dialog and even Brisa's [[Airport Diagram Generator]] or the [[Kelpie Flight Planner]] directly in FlightGear, using Nasal scripting and the [[Canvas]] system, without having to write any C++ code - so that people won't need to use external tools or programming languages to create such applications. | ||
In the long run, we want to come up with a very flexible design so that the "map.nas" module cannot only be used for creating maps used in GUI dialogs, but also for creating moving map displays like the existing hard-coded [[ | In the long run, we want to come up with a very flexible design so that the "map.nas" module cannot only be used for creating maps used in GUI dialogs, but also for creating moving map displays like the existing hard-coded [[Navigation display]] or the [[TCAS]] and WXRADAR displays ("glass" displays), i.e. as cockpit instruments/avionics. | ||
This approach would also make it possible to directly show instruments in GUI dialogs or vice versa. | This approach would also make it possible to directly show instruments in GUI dialogs or vice versa. | ||