20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Goals
(→Goals) |
|||
| Line 10: | Line 10: | ||
* [[CUI]] | * [[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 | 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 {{fgcommand|GetAvailableWxEngines}} and {{fgcommand|SelectWxEngine}} should do the job.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/34534324/ | |url = https://sourceforge.net/p/flightgear/mailman/message/34534324/ | ||
|title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | |title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | ||
| Line 18: | Line 18: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
== Motivation == | == Motivation == | ||