20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→2021: https://sourceforge.net/p/flightgear/mailman/message/37296280/
m (→2017) |
m (→2021: https://sourceforge.net/p/flightgear/mailman/message/37296280/) |
||
| Line 27: | Line 27: | ||
== Replacement status == | == Replacement status == | ||
{{See also|FlightGear_and_OpenGL_ES#Example:_disabling_PUI}} | {{See also|FlightGear_and_OpenGL_ES#Example:_disabling_PUI}} | ||
=== 2021 === | |||
Pretty much all of the FlightGear GUI is defined in XML space, except for a few oddments. Let’s say 95% at this point. | |||
Additionally, even if we were to change that for the core sim (and James' current plan is to keep the XML syntax and just extend it), the installed base of *aircraft* ship their own XML dialogs (eg, replacing the autopilot dialog with a custom one, or just adding their own aircraft-specific helper controls for doors / lights / cargo / whatever). So even if we found the most sublimely beautiful, intuitive, compact GUI description language in the world, we have to keep the XML syntax working as-is, for the foreseeable future. | |||
Given this, James' intention is to replace the output side [[PUI]] but keep the front-end side (XML / properties / bindings) unchanged, and therefore backwards compatible, and simply add some new types / options / widget types going forward. This will mean we still have to deal with the slightly cumbersome XML+Nasal syntax, but, well, it’s not *that* cumbersome. <ref>https://sourceforge.net/p/flightgear/mailman/message/37296280/</ref> | |||
=== 2020 === | === 2020 === | ||