Canvas PUI mapping: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
* {{tag|binding}} | * {{tag|binding}} | ||
* {{tag|default}} | * {{tag|default}} | ||
* {{tag|enable}} | |||
* {{tag|visible}} (easy) | * {{tag|visible}} (easy) | ||
* {{tag|keynum}} and {{tag|key}} | * {{tag|keynum}} and {{tag|key}} | ||
Revision as of 16:53, 9 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:
- https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.gui#l111
- https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/GUI/FGPUIDialog.cxx#l1070
We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets, specifically:
<height>and<width><legend><label><property>and<format><binding><default><enable><visible>(easy)<keynum>and<key><font><color>
Currently, this is accomplished in non-generic, fairly roundabout, fashion in the applyPUIAttributes() helper funciton in the pui2canvas parser