Unifying the 2D rendering backend via canvas: Difference between revisions
No edit summary |
m (→Background) |
||
Line 13: | Line 13: | ||
* 2D PANEL | * 2D PANEL | ||
* GUI | * GUI | ||
Also, the Canvas subsystem should be powerful enough to re-implement existing hard-coded od_gauge instruments, such as: | |||
* wxRadar | |||
* agradar | |||
* NavDisplay |
Revision as of 15:28, 6 July 2012
The FlightGear forum has a subforum related to: Canvas |
Background
The Canvas subsystem is flexible enough to re-implement existing 2D rendering related features, such as the HUD system or the 2D panel system, in scripting space, so that legacy C++ code can be incrementally replaced with a more accessible and more maintainable version in scripting space, i.e. as part of the base package - while ensuring that the 2D rendering backend is increasingly unified, as part of the Canvas subsystem.
The idea is to provide wrappers for these systems, which implement the existing behavior, so that the C++ code can be phased out. In particular, this means that wrappers for the following systems will be added:
- HUD
- 2D PANEL
- GUI
Also, the Canvas subsystem should be powerful enough to re-implement existing hard-coded od_gauge instruments, such as:
- wxRadar
- agradar
- NavDisplay