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 21:43, 25 June 2016
, 25 June 2016→Is this going to be committed ?
| Line 561: | Line 561: | ||
}} | }} | ||
}} | }} | ||
In summary, the pui2canvas effort does not need to be used, supported, endorsed or even just reviewed/committed by any core developers, because it's just a tiny, and optional, Nasal/Canvas module that can be added to fgdata by fgdata contributors - or even just distributed as a self-contained Nasal module that can be dropped into $FG_HOME/Nasal - and it just works, so there really is no "disconnect" or "communication barrier" here - that debate took place years ago, and James himself came up with most of the ideas related to this, we're really just implementing his original proposal - regardless of his Qt5 work, and regardless of his current priorities - he not only came up with these ideas, but approved them and encouraged this work, just like he encouraged the development of the Canvas based aircraft center<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 | |||
|added = Jun 18th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
=== How can this be helpful to Phi/Qt5 ? === | === How can this be helpful to Phi/Qt5 ? === | ||