20,741
edits
Canvas Map API: Difference between revisions
Jump to navigation
Jump to search
m
→Background
m (→Open Issues) |
m (→Background) |
||
| Line 3: | Line 3: | ||
== Background == | == Background == | ||
As of FlightGear 2.9, the base package contains additional [[Canvas]] helpers to help with the creation of navigational displays (map dialogs or map instruments). These are currently under development and will change rapidly during the next weeks and months, so that we can come up with a generic and re-usable design for different dialogs/instruments. | As of FlightGear 2.9, the base package contains additional [[Canvas]] helpers to help with the creation of navigational displays (map dialogs or map instruments). These are currently under development and will change rapidly during the next weeks and months, so that we can come up with a generic and re-usable design for different dialogs/instruments. | ||
== Objective == | |||
Heavily reduce the amount of specialized Canvas/Nasal code in XML dialogs and instruments related to mapping/charting (airport-selection, map widget, navdisplay etc) and ensure that a maximum degree of code sharing is accomplished, regardless of the canvas placement mode that is used - bottom line being, it really shouldn't matter if a map is shown as part of an airport selection dialog, as part of the moving map dialog, as part of the navdisplay etc. | |||
== Status == | == Status == | ||