20,741
edits
Howto:Creating a Canvas GUI Widget: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Canvas Navigation}} | {{Canvas Navigation}} | ||
Originally, [[Canvas Widgets|suggested and discussed back in early 2014]] by a few FlightGear core developers, the [[Howto:Processing legacy PUI dialogs using Canvas|pui2canvas]] approach to parsing a subset of PUI/XML has turned out to be a suitable fasttrack solution to get rid of the legacy PUI engine, without causing major regressions or tons of work. | Originally, [[Canvas Widgets|suggested and discussed back in early 2014]] by a few FlightGear core developers, the [[Howto:Processing legacy PUI dialogs using Canvas|pui2canvas]] approach to parsing a subset of PUI/XML and mapping that to Canvas widgets/properties, has turned out to be a suitable fasttrack solution to get rid of the legacy PUI engine, without causing major regressions or tons of work. | ||
It seems, that probably nobody would object against removing PUI and replacing it by CUI, keeping the old PUI/XML syntax. | It seems, that probably nobody would object against removing PUI and replacing it by CUI, keeping the old PUI/XML syntax. | ||
At least for a while. Dropping PUI would be a huge step forward.<ref>{{cite web | At least for a while. Dropping PUI would be a huge step forward.<ref>{{cite web | ||