|
|
| Line 114: |
Line 114: |
|
| |
|
| == Planned Features {{Pending}} == | | == Planned Features {{Pending}} == |
| Future extensions will probably include support for:
| |
|
| |
| * using SVG files instead of manually coded geometry {{Done}}
| |
| * stylable elements (font size, color etc) {{Not done}}
| |
| * showing AI/MP traffic {{Pending}}
| |
| * show navaids and fixes {{Pending}}
| |
| * showing ILS symbols (depending on scale) {{Pending}}
| |
| * showing route manager routing {{Pending}}
| |
| * weather radar {{Not done}} (local weather?)
| |
| * compass roses {{Pending}}
| |
| * map center / off center mode {{Pending}}
| |
|
| |
| Basically, the main features supported by existing NDs will be supported by the new map system (i.e. APP/VOR/MAP/PLN), while ensuring that it is still kept generic enough so that the same backend code can not only be used for cockpit gauges, but also for GUI widgets, i.e. custom charting/mapping widgets.
| |
|
| |
| All of these will be implemented as "layers" (canvas groups) which can be dynamically toggled using properties. These layers will be internally converted to "canvas groups", so that they can be efficiently sorted.
| |
|
| |
| Looking at the [[Map]] dialog docs, James was planning to add a bunch of other features which are not currently supported by the map widget, but which would probably be worth keeping in mind for the canvas system as such, for example: | | Looking at the [[Map]] dialog docs, James was planning to add a bunch of other features which are not currently supported by the map widget, but which would probably be worth keeping in mind for the canvas system as such, for example: |
| * "use terrain height intersections to compute a EGPWS / G1000-style terrain clearance overlay" | | * "use terrain height intersections to compute a EGPWS / G1000-style terrain clearance overlay" |