20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Motivation
| Line 2: | Line 2: | ||
{{WIP}} | {{WIP}} | ||
== Goals == | |||
Work out a sufficiently-complete subset of PUI/XML that can be supported by all existing FlightGear UI efforts, namely: | |||
* [[PUI]] | |||
* [[Phi]] | |||
* [[QUI]] | |||
* [[CUI]] | |||
In particular, this means providing a migration path to get rid of huge embedded custom script blocks, so that these can be re-implemented/provided in the form of generic fgcommands, in order to make dialogs purely declarative, to have most of the logic extracted out of the UI implementation. How many properties do we have to write to to switch from AW to BW? Nothing a UI should know about. A service "GetAvailableWxEngines" and "SelectWxEngine" should do the job.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34534324/ | |||
|title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Oct 12th, 2015 | |||
|added = Oct 12th, 2015 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== Motivation == | == Motivation == | ||