20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 07:52, 23 October 2016
, 23 October 2016→Why Nasal and Canvas ?
No edit summary |
|||
| Line 152: | Line 152: | ||
* PUI widget visibility controlled via props.nas (conditions) | * PUI widget visibility controlled via props.nas (conditions) | ||
* integration with the <code>canvas</code> tag to fully support recursion | * integration with the <code>canvas</code> tag to fully support recursion | ||
== Before this gets committed ... === | |||
For this to be committed, even just as an option, a few things should happen first of all: | |||
* the whole thing should be turned into an optional Nasal submodule | |||
* loading it should be configurable via preferences.xml | |||
* it would make sense to introduce a $FG_ROOT/pui2canvas.xml file included via preferences.xml, which contains script specific settings | |||
* such settings could be a list of dialogs/widgets known to work well enough already (think about.xml, view.xml, scenarios.xml etc) | |||
* menubar.xml could be edited to replace <code>dialog-show</code> entries with a <code>gui.dialog-show</code> entry | |||
* this could transparently let the user decide whether he wants to use PUI, Qt5 or the pui2canvas parser (think [[Aircraft Center]]) | |||
== Why Nasal and Canvas ? == | == Why Nasal and Canvas ? == | ||