20,741
edits
Unifying the 2D rendering backend via canvas: Difference between revisions
Jump to navigation
Jump to search
m
Unifying the 2D rendering backend via canvas (view source)
Revision as of 15:32, 6 July 2012
, 6 July 2012→Background
m (→Background) |
|||
| Line 8: | Line 8: | ||
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 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: | The idea is to provide Nasal wrappers for these systems, which implement the existing behavior using the canvas system, so that the old C++ code can be phased out. In particular, this means that wrappers for the following systems will be added: | ||
* HUD | * HUD | ||
| Line 25: | Line 25: | ||
* agradar | * agradar | ||
* NavDisplay | * NavDisplay | ||
As of 07/2012 the navdb is fully exposed as part of the NasalPosition module $FG_SRC/Scripting. | |||