[webkit-dev] restructuring, kwq and QPainter

Leo Savernik l.savernik at aon.at
Fri Feb 24 09:23:50 PST 2006


Due to the latest restructurings of WebCore am I right of the impression that 
Apple is going to outphase kwq completely?

In this case I have to remark that painting is a speed-critical path in khtml 
used under KDE. Therefore I propose that the painting routines of the render 
tree are not replaced by another abstraction layer, but staying as close as 
possible to Qt4's QPainter (with provisions for platform-dependent 
extensions, of course).

The mac platform wouldn't incur a speed penalty because they have to map the 
painting routines to their primitives anyway. KDE, on the other hand, makes 
use of QPainter as its abstraction layer. So having an "independent" 
WebcorePainter layer penalises KDE with a double indirection through 
WebcorePainter -> QPainter -> X11MagicStuff etc.

Enabling an efficient integration into Qt/KDE-based environments will raise 
WebCore's consideration for a full merge back into KDE. How's Apple's devs 
opinion on this subject?


More information about the webkit-dev mailing list