[Interest] some doubts about current graphics stack in Qt 5.1

[Thiago Macieira]

On segunda-feira, 9 de dezembro de 2013 15:43:22, pritam.ghanghas at gmail.com 
wrote:
> Within Qt
> QtWIdgets use QPainter, which can use raster, native or opengl backends.

There's no native backend anymore.

> Most of the time it will be raster. But if one is using QGLWidget or sets a
> QGLWidget as viewport. QPainter will switch to opengl. There are non
> programmatic ways as well to make OpenGl default.
> 
> QQuick always uses opengl API (it may not be hardware accelerated if mesa
> or angle is used)

ANGLE is accelerated. It's meant to translate OpenGL ES 2 to DirectX, which is 
usually accelerated.

> Now a little specific, how does webkit rendering is done. Using QPainter,
> opengl or it follows the same rules as above.

QPainter.

> ################# 1 #############
> QWebView view;
> view.show();
> 
> 
> ################# 2 ##############
> QGraphicsScene scene;
> scene.addWidget(new QWebView);
> view.addWidget(&scene);
> view.setViewport(new QGLWidget);
> view.show();
> 
> I would assume 1 is using raster and second one is using opengl.
> Are there any platforms where 2nd will be slower than first?
> And what about WebView QML element?

Everything is raster with WebKit. Web content was not designed for OpenGL, 
except for WebGL.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20131209/c7b0029a/attachment.sig>