20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
→PLIB/PUI (legacy GUI)
| Line 148: | Line 148: | ||
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>. | ||
{{FGCquote | |||
|1= From what I've seen, I don't see any reason why there cannot be a direct one-to-one migration of the PUI GUI main window to a Qt main window, including dynamically generating the aircraft menu and submenus by parsing the XML unmodified. This can be done incrementally as it is developed, and probably in a way that requiresero changes to the aircraft PUI GUI XML (though changes could be made later, as you can do far, far more with Qt than with PUI). So I personally think that targeting dialogs for the PUI GUI would be the best way to go as this can be directly translated by the GUI developers into Qt dialogs requiring the aircraft developers to do nothing | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34536197/ | |||
| title = <nowiki>Re: [Flightgear-devel] GUI questions (again)</nowiki> | |||
| author = <nowiki>Edward d'Auvergne</nowiki> | |||
| date = Oct 13th, 2015 | |||
}} | |||
}} | |||
<references/> | <references/> | ||