[Webkit-unassigned] [Bug 36883] Generic parallel painting in WebKit with Qt backend

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 28 13:04:35 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=36883





--- Comment #19 from Simon Hausmann <hausmann at webkit.org>  2010-04-28 13:04:31 PST ---
(In reply to comment #18)
> 1) I thought so. As QPicture is Qt specific, I asked the community whether they
> would prefer a less platform dependent solution, and some said yes. Since
> GraphicsContext and QPainter basically have the same purpose, I can record the
> GraphiscContext commands as well.
> 
> 2) I know the first title was misleading. The focus of the project is speeding
> up the painting. Anti-aliasing is also applied to the images, which I don't get
> when drawing on the screen.
> 
> Still, I think this approach is a benefit regardless of the process model,
> would make both WebKit and WebKit2 model faster. Although the QPixmap drawing
> restrictions are still a blocker, but I hope Qt will eventually make it thread
> safe.

My point remains even with a platform-independent implementation of QPicture,
doesn't it? Just recording the paint commands should be considerably less work
than _actually_ rasterizing text, tesselating polygons and uploading textures.

What's the gain that remains when _that_ work is still done in the gui thread,
blockingly?

Less threading related, but I wonder how well things work with "recording"
WebKit's painting into GL display lists :)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list