Replying from right address this time...
On Mon, Apr 15, 2013 at 9:23 AM, Noam Rosenthal n...@webkit.org wrote:
Thanks Gwang-Yoon
Yes, I would like to get rid of TextureMapperImageBuffer, and we can do
that once Qt-WebKit1 can move to the threaded compositor.
I would like to use the
On Sunday 14 April 2013, Martin Robinson wrote:
I'm surprised you didn't focus on WebKit2, since WebKit1 is in
maintenance mode now.
WebKit1 is easier to develop for. Especially now that we are not allowed to
develop in WebKit2 anymore..
Second. Part of what this worl gives us is to unify
Long time no see.
I would like to share some of progresses about threaded compositor for
WebKitGtk.
First of all, I made a another prototype about it and I push it on github.
https://github.com/ryumiel/webkit-experimental/commits/threaded-compositing
*Needs discussion, and clean up. (For Gtk
On Sun, Apr 14, 2013 at 12:52 AM, Gwang-Yoon Hwang
ryum...@company100.net wrote:
Nice work!
1. There are 3 accelerated compositing methods in WebKit1 Gtk. Cairo,
Clutter, and GL. These patches will adds 1 more options, threaded
compositing. I think we need to simplify/unite rendering paths to
Thanks for respond.
On Mon, Apr 15, 2013 at 1:10 AM, Martin Robinson mrobin...@webkit.orgwrote:
On Sun, Apr 14, 2013 at 12:52 AM, Gwang-Yoon Hwang
ryum...@company100.net wrote:
Nice work!
1. There are 3 accelerated compositing methods in WebKit1 Gtk. Cairo,
Clutter, and GL. These
5 matches
Mail list logo