20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→2021
m (→2021: https://sourceforge.net/p/flightgear/mailman/message/37297727/) |
m (→2021) |
||
| Line 39: | Line 39: | ||
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> | 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> | ||
In mid 2021, James reported that he is working on some ‘PUICompat’ classes which hold/own/represent the GUI state in C++, but which can be used with Nasal CppBind. And of course we could indeed expose those later on. <ref>https://sourceforge.net/p/flightgear/mailman/message/37297727/</ref> | In mid 2021, James reported that he is working on some ‘PUICompat’ classes which hold/own/represent the GUI state in C++, but which can be used with [[Nasal/CppBind|Nasal CppBind]]. And of course we could indeed expose those later on. <ref>https://sourceforge.net/p/flightgear/mailman/message/37297727/</ref> | ||
=== 2020 === | === 2020 === | ||