20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 18:45, 22 October 2016
, 22 October 2016→Why Nasal and Canvas ?
| Line 184: | Line 184: | ||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | ||
|author = <nowiki> Thorsten </nowiki> | |author = <nowiki> Thorsten </nowiki> | ||
|date = Jun 18th, 2016 | |||
|added = Jun 18th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Bottom line, the Canvas UI SGSubsystem is there, it's existing C++ code, that has been integrated years ago - it's used every day - whenever you're seeing a tooltip, a Canvas GUI dialog or a CanvasWidget, it's all there and just works. | |||
If people find it challenging to render a webkit or Qt5 widget into FlightGear, they'd be well-advised to simply come up with a custom Canvas::Element child class - which I also understand how to do, and James has previously done that, too (he implemented/prototyped Canvas::Image for handling raster images), so he understaands perfectly how to extend the Canvas system to support other "elements". | |||
This path is unrelated to PUI or pui2canvas - it's just a way of rendering into the FligthGear window, without having to do much homework - it'll just work, which includes event handling etc - Tom implemented that almost half a decade ago, indeed at the encouragement of James and others back then ...<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=289032#p289032 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 18th, 2016 | |date = Jun 18th, 2016 | ||
|added = Jun 18th, 2016 | |added = Jun 18th, 2016 | ||