Labels

Performance


I was recently asked about the performance of the Cairo-based Webkit.  As a first cut I tried running SunSpider to see what would happen.  Unfortunately, it identified a serious bug in the WebKit Cairo port, in that the font handling appears to be screwed up.  Consider the following screenshot...

It appears that the build is not dealing with code elements properly.

By the way, anyone interested in playing with the Release or Debug binaries of this webkit is welcome to grab the Debug or Release ZIP files. They have been tested on one external system, so I believe all dependencies are in the archives, but please let me know if you have any problems.


Labels:

Comments

funtom said…
Is that an experimental build or is the WebKit team commited to use Cairo as the graphic base for future WebKit builds?
9:07 PM
bfulgham said…
The Cairo back-end is experimental. The core WebKit will probably always focus on the Apple libraries just due to the origin of the software. However, those of us who wish to use WebKit outside of Safari are working on this so that we can have a redistributable tool.
10:09 PM
Unknown said…
brent, can cairo version be built without using any patches?

Also can all those dependencies be built into one large webkit.dll
1:14 PM
bfulgham said…
Not as yet. I am working with the core WebKit team to get these changes integrated, but this can be a slow process as they have exacting quality standards, and a focus on their primary product (Safari).

I believe the dependencies can be built into a single DLL, but I am currently using a few of the DLL's that ship with WebKit (e.g., zlib1.dll, libxml2.dll, and so forth).

I believe there are some who are working on building WebKit dependencies that are tightly focused on WebKit/Cairo and that take up less space.
8:01 PM
Post a Comment

Popular Posts