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
Replying from right address this time...
On Mon, Apr 15, 2013 at 9:23 AM, Noam Rosenthal 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 threaded compositor
Thanks for respond.
On Mon, Apr 15, 2013 at 1:10 AM, Martin Robinson wrote:
> On Sun, Apr 14, 2013 at 12:52 AM, Gwang-Yoon Hwang
> wrote:
>
> Nice work!
>
> > 1. There are 3 accelerated compositing methods in WebKit1 Gtk. Cairo,
> > Clutter, and GL. These patches will adds 1 more options, threa
On Sun, Apr 14, 2013 at 12:52 AM, Gwang-Yoon Hwang
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 reduce
> complexity
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 port
5 matches
Mail list logo
