20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Motivation
| Line 4: | Line 4: | ||
== Motivation == | == Motivation == | ||
Our lowest-effort, most-visually pleasing and consistent result is going to be making both Phi and Qt UIs able to work / translate / parse the dialog XML syntax. Likely with some exceptions, especially on the Phi side if Nasal is involved. The question is how practical this really is; i.e. due to the complexity of the aircraft dialogs - a solution which works with the common 90 or 95% would be good enough<ref>{{cite web | Our lowest-effort, most-visually pleasing and consistent result is going to be making both Phi and Qt UIs able to work / translate / parse the existin dialog [[PUI]]/XML syntax. | ||
Likely with some exceptions, especially on the [[Phi]] side if [[Nasal]] is involved. | |||
The question is how practical this really is; i.e. due to the complexity of the aircraft dialogs - a solution which works with the common 90 or 95% would be good enough<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34537052/ | |url = https://sourceforge.net/p/flightgear/mailman/message/34537052/ | ||
|title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | |title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | ||