[webkit-qt] Switching to texture-mapper by default

viatcheslav.ostapenko at nokia.com viatcheslav.ostapenko at nokia.com
Fri May 27 10:47:08 PDT 2011

I think plugins/media implementation has to be checked/fixed before switching to texture mapper.


From: webkit-qt-bounces at lists.webkit.org [mailto:webkit-qt-bounces at lists.webkit.org] On Behalf Of Rosenthal Noam (Nokia-CTO-Qt/SiliconValley)
Sent: Friday, May 27, 2011 12:34 PM
To: webkit-qt at lists.webkit.org
Subject: [webkit-qt] Switching to texture-mapper by default

Hi all
Now that the TextureMapper implementation of accelerated compositing is up and running, thanks to Slava's help in upstreaming the changes we've made for WebKit2,
I'd like to find the right time to switch it on by default, and after the dust settles remove the old GraphicsLayerQt implementation altogether.

I don't want to do this in a way that hurts some kind of release, and of course I'll make sure it doesn't break any tests.

Any thoughts/objections/threats?

PS If you don't know what I'm talking about, you can check out http://qtwebkit.blogspot.com/2010/10/texture-mapper-accelerated-compositing.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-qt/attachments/20110527/6c2473c6/attachment.html>

More information about the webkit-qt mailing list