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 | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34537052/ | |||
|title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Oct 13th, 2015 | |||
|added = Oct 13th, 2015 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Adding another dependency to FlightGear is usually very controversial, i.e. the consensus was that that is not something to be taken lightly. And then again, it would require updating all of the gui definitions.<ref>{{cite web | Adding another dependency to FlightGear is usually very controversial, i.e. the consensus was that that is not something to be taken lightly. And then again, it would require updating all of the gui definitions.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/29583534/ | |url = https://sourceforge.net/p/flightgear/mailman/message/29583534/ | ||