From: Thorsten R. <tho...@sc...> - 2015-10-13 14:12:50
|
> 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 requires > zero 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 (sorry Hooray ;). That part I more or less got from James - but note that Qt is supposed to be optional - so what do we do if Qt isn't added at compile time? If someone says 'I don't like the Qt option, I want to use Phi', I'd still like him to fly the Shuttle. * Thorsten |