20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
→PLIB/PUI (legacy GUI): http://sourceforge.net/p/flightgear/mailman/message/34532040/
m (→PLIB/PUI (legacy GUI): http://sourceforge.net/p/flightgear/mailman/message/34532040/) |
|||
| Line 129: | Line 129: | ||
Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., '''Qt will never be a requirement to build FG'''), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups). | Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., '''Qt will never be a requirement to build FG'''), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups). | ||
Any in-sim GUI using Qt will exist in parallel to the PLIB/PUI one for at least one major release, although this may mean maintaining two sets of dialogs, unless the XML-translation-tool is good enough that we can use it at run-time for aircraft dialogs<ref>http://sourceforge.net/p/flightgear/mailman/message/34532040/</ref>. | |||
Expect to see a test branch in Git in the next month or so, and hopefully something usable for 3.6. The PLIB code will remain so hopefully it can be a gradual transition<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | Expect to see a test branch in Git in the next month or so, and hopefully something usable for 3.6. The PLIB code will remain so hopefully it can be a gradual transition<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | ||