Canvas PUI mapping: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 15: Line 15:


We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets
We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets
Currently, this is accomplished in non-generic, fairly roundabout, fashion in the applyPUIAttributes() helper funciton in the pui2canvas parser

Revision as of 14:29, 8 July 2016

This article is a stub. You can help the wiki by expanding it.

will become a table with the most essential PUI directives (non-widgets), such as layout/styling and common PUI widget functionality (think live properties, bindings, conditions), so that we can keep track of what's missing/needed and finished already.

columns: directive/tag, progress, priority, remarks

The basic idea can be seen below:


We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets


Currently, this is accomplished in non-generic, fairly roundabout, fashion in the applyPUIAttributes() helper funciton in the pui2canvas parser