> What are the advantages/disadvantages of moving to GraphicsWebView for a user > like me? :-P
>From the user point of view: 1) speed when on an accelerated compositing path (CSS animations or 3D transform). 2) 3D transforms. You might have seen this demo: http://www.satine.org/research/webkit/snowleopard/snowstack.html (only working with Safari Mac and QtWebKit with a GL viewport). Currently this kind of websites only work with graphics view and openGL. No'am is working on a pure software implementation of accelerated compositing so that works with QWebView, but that cannot match the speed of openGL (and that will be for QtWebKit 2.2 or later). 3) better future support of WebGL (currently broken in QtWebKit trunk, but hopefully available one day). The disadvantages is that we no longer have native widgets. So we can have problems with stuff like contextual menu and modal dialog which we should be careful with. This can also be used to implement more easily stuff like a preview of all tab opened in the current window (like topsite of safari but with live websites). I am personally not a fan of GraphicsView, because it makes the rendering pipeline incredibly complex. But that is unfortunately the best way to get hardware acceleration with openGL for web content, and unfortunately the only way to get 3D transforms for the next ~6 months. Benjamin _______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
