20,741
edits
m (→2021: https://sourceforge.net/p/flightgear/mailman/message/37296280/) |
m (→2021: https://sourceforge.net/p/flightgear/mailman/message/37295586/) |
||
Line 29: | Line 29: | ||
=== 2021 === | === 2021 === | ||
In early 2021, James did a brief evaluation of ImGUI as a possibility - he's also evaluating it in some projects at his day job. | |||
The APi is interesting if you’re starting from scratch and only exclusively in C++, but it’s not a great fit for how we define GUIs in FG (via XML/Nasal): there is no back door that he could find, to access the persistent state of the GUI, or build it up in a data-driven way. So making a mapping to keep our existing GUI XML working (and updating correctly) becomes a bit of a chore.<ref>https://sourceforge.net/p/flightgear/mailman/message/37295586/</ref> | |||
Pretty much all of the FlightGear GUI is defined in XML space, except for a few oddments. Let’s say 95% at this point. | Pretty much all of the FlightGear GUI is defined in XML space, except for a few oddments. Let’s say 95% at this point. | ||