[webkit-qt] Accelerated compositing: enable by default?

[noam.rosenthal at nokia.com]

Hi Antti
Currently there's no such mechanism, but it could be pretty easily added - I'll add a bug for it. There might be other optimizations like that as well... we'll have to add them as we go along.

Cheers
No'am

________________________________________
From: akoivisto at gmail.com [akoivisto at gmail.com] On Behalf Of ext Antti Koivisto [koivisto at iki.fi]
Sent: Tuesday, February 23, 2010 5:00 AM
To: Rosenthal Noam (Nokia-D-Qt/RedwoodCity)
Cc: webkit-qt at lists.webkit.org
Subject: Re: [webkit-qt] Accelerated compositing: enable by default?

Sounds like a good idea.

Does the current implementation cope well with large layers? That is,
is there a mechanism (size cutoff?) in place in some level that
prevents large layers from eating all the memory for caching? Layer
tiling would be nice in the future...


   antti

On Sat, Feb 20, 2010 at 12:19 AM,  <noam.rosenthal at nokia.com> wrote:
> Hi guys
>
> I'm at a situation where AC (accelerated compositing) is getting more and more solid, but there are very few people using it because it's disabled by default. The consequence of that is that we receive "CSS is slow" bug, which we know AC fixes at some cases, instead of "AC breaks website foobar", which is the kind of bug I'm hoping to get at this point. Making AC enabled by default is likely to have the desired effect.
> Of course, AC needs a lot more testing before 2010.1, but that testing would be accelerated if more people (who are the people using trunk version anyway) would use it.
>
> Any thoughts / objections / life threats? :)
>
> Cheers
> No'am
>
> _______________________________________________
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>