On Thu, Nov 5, 2009 at 3:34 PM, Alexander Teinum <atei...@gmail.com> wrote:
> I want to make it clear, and it might be obvious by now, but
> test_shell isn't interesting to me. I just want the fastest browser
> engine that I can get.
>
> What makes Chromium different than WebKitGTK+ for my project, is that
> Chromium renders the GTK stuff correctly with CSS transformations.
> It's also snappier.
Conceptually Chrome is a bunch of layers, from top to bottom
1) chrome+ui junk
2) multiprocess rendering
3) webkit API
4) webkit
Test shell covers layer 3 and down. Unfortunately, all the
performance you like is in layer 2. We don't have a simple place to
cut for that; however, since Chrome and test_shell are both just
clients of the WebKit API, you could write your own client (like
test_shell) and then copy the performant bits out of Chrome. It will
require some work, but if it were easy then your job would be boring.
:)
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
