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 8: | Line 8: | ||
=== Adopting the new Canvas 2D rendering system === | === Adopting the new Canvas 2D rendering system === | ||
As of July 2012, FlightGear core developers agreed to adopt Tom's new [[Canvas]] 2D rendering system which is purely property-driven and handles all [[Original Canvas Proposal|2D drawing via the FlightGear property tree]]. Initially, the idea will be to replace the current GUI toolkit (PUI/PLIB) and use a purely [[Canvas]]-based implementation instead, which will be mostly implemented in scripting space using Nasal and merely use the Canvas system as its backend. The implementation details are covered at [[Canvas Widgets]]. | As of July 2012, FlightGear core developers agreed to adopt Tom's new [[Canvas]] 2D rendering system which is purely property-driven and handles all [[Original Canvas Proposal|2D drawing via the FlightGear property tree]]. Initially, the idea will be to replace the current GUI toolkit (PUI/PLIB, which has shown many limitations over time) and use a purely [[Canvas]]-based implementation instead, which will be mostly implemented in scripting space using Nasal and merely use the Canvas system as its rendering backend. The implementation details are covered at [[Canvas Widgets]]. | ||
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. | |||
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 using so called [[Canvas Maps]]. | 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 using so called [[Canvas Maps]]. | ||