2,733
edits
Howto:Creating a Canvas GUI Widget: Difference between revisions
Jump to navigation
Jump to search
Split into separate paragraphs
Red Leader (talk | contribs) (Split into separate paragraphs) |
|||
| Line 1: | Line 1: | ||
{{Canvas Navigation}} | {{Canvas Navigation}} | ||
As the integrated, and fully script-able, [[Canvas GUI]] develops, new {{wikipedia|Widget (GUI)|widgets}} need to be added <ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=289321#p289321 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Jun 21st, 2016 | |||
|added = Jun 21st, 2016 | |||
|script_version = 0.40 | |||
}}</ref>. This article shows '''how to create a Canvas GUI widget'''. | |||
=== Background === | |||
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. | 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. | ||
| Line 17: | Line 27: | ||
Also, the '''pui2canvas''' approach can help address a number of long-standing PUI related issues, such as rendering arttfacts on some ATI/AMD GPUs, but also PUI/Canvas inter-operability issues related to [[Canvas Event Handling]]. | Also, the '''pui2canvas''' approach can help address a number of long-standing PUI related issues, such as rendering arttfacts on some ATI/AMD GPUs, but also PUI/Canvas inter-operability issues related to [[Canvas Event Handling]]. | ||
=== Status (07/2016) === | |||
As of June 2016, there are just five widgets in the Canvas GUI: | As of June 2016, there are just five widgets in the Canvas GUI: | ||
* {{Canvas Widget|widget=Button}} | * {{Canvas Widget|widget=Button}} | ||