From: James T. <zak...@ma...> - 2016-06-13 16:06:11
|
> On 13 Jun 2016, at 16:30, Edward d'Auvergne <tru...@gm...> wrote: > > Parsing the XML directly and dynamically generating a menu and > submenus in Qt should be quite an easy task :) It might be easier to > preserve that than to come up with a new standard. The hardest task > will be to attach the QMenuBar element onto the window, without Qt > managing the main FG window. I'm willing to guess that this FG main > window will need to be eventually embedded within a QMainWindow > element. I’m currently undecided if Qt Quick or widgets is the better way to go, with a preference towards Qt Quick, since it will allow things closer to current PUI (semi-transparent widgets on top of the 3D content). It still allows creating separate windows too (Erik’s use case), but means we get consistent, custom theming on all platforms, since standard desktop look is not so nice for a flight-sim. My intention is to make a QML-hosting OSG-drawable, and add this as a concept in Qt-enabled builds, then port some PUI dialogs to it, and see how easy / painful the process is. I’ll create some QObjects which expose commands and the property tree and Nasal. This has the advantage of not touching the OSG window at all, QtQuick simply provides some additional OpenGL rendering on top, which we pass events to - pretty much exactly the same as what we already do for PUI, and hopefully can co-exist with it. I have this working in a local OSG tree in a standalone demo, but that’s based on osgQt - I want to see if I can make it work on a normal, non-Qt OSG window inside FlightGear. Kind regards, James |