Hi Laszlo, On Friday 28 February 2014 12:25:19 Agocs Laszlo wrote: > Keep in mind, though, that the primary goal of QtGui is to enable Qt Quick > and related modules, like Controls, which are all based on OpenGL [ES] 2.0. > Supporting 3rd party renderers that explicitly rely on GL3+ features and > are not interested in true portability (e.g. between desktop and mobile) is > not QtGui's job and is not in scope here, obviously, since some of the > implementations we would dynamically select do only ES 2 or GL 2.1.
This is where I disagree. The goal of QtGui is to enable developers to write GUI applications easily and efficiently. Those applications may or may not use Qt Quick 2 and/or controls and many of them of course do so. However, a very large percentage also need to integrate with other things too. I agree with Bjoern and Gunnar that making use of QOpenGLFunctions within Qt Quick 2 seems the better way to go. I still need to think my way through more of this yet and my brain is already suffering from the Friday Feeling. I totally understand the desire to be able to select an OpenGL/ES2 implementation at runtime for applications that are only using OpenGL indirectly via Qt Quick 2. Have a good weekend, Sean -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK Klarälvdalens Datakonsult AB, a KDAB Group company Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development