20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Goals
(→Goals) |
(→Goals) |
||
| Line 42: | Line 42: | ||
|date = Jun 21st, 2016 | |date = Jun 21st, 2016 | ||
|added = Jun 21st, 2016 | |added = Jun 21st, 2016 | ||
|script_version = 0.40 | |||
}}</ref> | |||
the main UI candidates (Phi, Qt5 and Canvas) could actually benefit from each other - the Canvas route could greatly benefit from being able to use Qt5, and Canvas could greatly help clean up/simplify existing PUI dialogs. Equally, some of the ideas used in Phi could be useful for the Canvas/Qt5 approach. I don't think this has to be a mutually-exclusive thing at all - the main issue is the degree of ugly Nasal hacks in those PUI/XML dialogs; however, these dialogs can obviously be processed via Nasal and Canvas easily - so that it would actually make sense to use this opportunity to refactor said dialogs and turn into just declarative XML using tags and fgcommand/remote properties.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=288649#p288649 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 13th, 2016 | |||
|added = Jun 13th, 2016 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||