20,741
edits
FlightGear Newsletter January 2013: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter January 2013 (view source)
Revision as of 02:08, 30 January 2013
, 30 January 2013promoting the CDU section to get an anchor, moving it to the canvas/dev section (not really hangar specific) - anchor will be used at Cdu
(promoting the CDU section to get an anchor, moving it to the canvas/dev section (not really hangar specific) - anchor will be used at Cdu) |
|||
| Line 23: | Line 23: | ||
=== High Level Architecture === | === High Level Architecture === | ||
=== FlightGear on Android === | === FlightGear on Android === | ||
== Canvas-based CDU development == | |||
James has done a survey of the existing CDU setups, and produced a new version which combines the best parts of most of them - it uses the Canvas for rendering, but has a simple Nasal API for defining new pages and data fields, and for specifying how editing and buttons interact. (The later inspired by earlier work by Claus Christiansen) The code will be published in Git soon, and should be easily adaptable for any Honeywell-CDU equipped aircraft, providing you can compute suitable data values! For Boeing family aircraft the set of pages is quite similar, so the hope is to share some pages between at least the 737NG, 747-400 and any others where the developers wish. | |||
In particular there is separation of the CDU core setup from the page layouts, and those are separated from the field data. This makes development easier (pages and data models can be reloaded easily), but also increases the changes that some aspects can be shared between families of aircraft. | |||
[[File:cdu1.png|300px|Position initialization]] | |||
[[File:cdu2.png|300px|Departure selection]] | |||
[[File:cdu3.png|300px|Waypoint information lookup]] | |||
The screenshots above shows a few pages from the 737NG - of the total pages, about 2/3rd now exist in some form, but with many placeholder values until the matching FMS code is developed. Note the font rendering is not quite correct - Yves has generated a better font with proper characters, but there wasn't yet time to include it. But the system already supports both the tradition CRT 'green' appearance and the more modern LCD appearance. | |||
If you're unsure how much a given aircraft's CDU pages overlap with the 737NG, James is happy to help, assuming you have a suitable reference (manual) for your target aircraft. Even the Airbus MCDUs seem to share some concepts with Boeings, for once! | |||
=== Procedural Terrain Texturing === | === Procedural Terrain Texturing === | ||
| Line 111: | Line 125: | ||
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 [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US 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. | 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 [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US 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 === | === New aircraft === | ||