20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Motivation
| Line 40: | Line 40: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
We need to keep the existing way of specifying GUI files via XML - it's a nice, declarative way of building the dialogs. Switching to an imperative system would be a step backwards.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/29592603/ | |||
|title = <nowiki> Re: [Flightgear-devel] Switching from PUI to osgWidget </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jul 26th, 2012 | |||
|added = Jul 26th, 2012 | |||
|script_version = 0.40 | |||
}}</ref> | |||
So long as we keep XML compatibility most of the current Nasal interaction with the GUI will work. There is great scope to make /better/ Nasal APIs for items such as combo-boxes and pickers, especially ICAO and radio frequency pickers, but that's all 'improving the GUI' work than can happen once we've ditched PLIB and have something hackable.<ref>{{cite web | So long as we keep XML compatibility most of the current Nasal interaction with the GUI will work. There is great scope to make /better/ Nasal APIs for items such as combo-boxes and pickers, especially ICAO and radio frequency pickers, but that's all 'improving the GUI' work than can happen once we've ditched PLIB and have something hackable.<ref>{{cite web | ||