20,741
edits
FlightGear Newsletter July 2012: Difference between revisions
Jump to navigation
Jump to search
m
→Adopting the new Canvas 2D rendering system
| Line 11: | Line 11: | ||
This step will make it eventually possible for end users to easily customize the FlightGear GUI and its appearance by creating custom GUI styles (themes/skins), but also by creating completely new GUI widgets using an SVG editor like Inkscape. | This step will make it eventually possible for end users to easily customize the FlightGear GUI and its appearance by creating custom GUI styles (themes/skins), but also by creating completely new GUI widgets using an SVG editor like Inkscape. | ||
{{#ev:youtube|CIS8UyuJLgM}} | |||
Future plans include reimplementing the current HUD and 2D panel systems using the Canvas system. In addition, the canvas system will provide an opportunity to increasingly unify the 2D rendering backend in FlightGear in the months to come: [[Unifying the 2D rendering backend via canvas]]. Furthermore, the canvas system provides a novel way to abstract away the creation of fully interactive and dynamic moving map displays and GUI widgets for charting using so called [[Canvas Maps]]. | |||
=== Mailing list digest === | === Mailing list digest === | ||