Unifying the 2D rendering backend via canvas: Difference between revisions

Jump to navigation Jump to search

Unifying the 2D rendering backend via canvas (view source)

Revision as of 19:12, 29 June 2014

125 bytes removed ,  29 June 2014
m
→‎Planning
No edit summary
Line 46: Line 46:
* waypoint list widget:  https://gitorious.org/fg/flightgear/blobs/next/src/GUI/WaypointList.cxx
* waypoint list widget:  https://gitorious.org/fg/flightgear/blobs/next/src/GUI/WaypointList.cxx
* map widget: https://gitorious.org/fg/flightgear/blobs/next/src/GUI/MapWidget.cxx
* map widget: https://gitorious.org/fg/flightgear/blobs/next/src/GUI/MapWidget.cxx
This automatically means that PUI callbacks must be forwarded to Nasal, so that they can be implemented as Nasal callbacks.


Also, the Canvas subsystem should be powerful enough to allow re-implementing existing hard-coded [https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/od_gauge.cxx od_gauge instruments], such as:
Also, the Canvas subsystem should be powerful enough to allow re-implementing existing hard-coded [https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/od_gauge.cxx od_gauge instruments], such as:
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/73536"

Navigation menu