test_shell being a test shell used mostly for non-interactive testing,
we haven't given a lot of concern to its perfomance AFAIK. I'm not
even sure how long of a lifespan it'll have since we aim to
merge/replace it with WebKit's DumpRenderTree at some point soon.
Is there some reason you're not just using Chromium in full screen mode?
-- Dirk
On Thu, Nov 5, 2009 at 1:18 PM, Alexander Teinum <atei...@gmail.com> wrote:
>
> For a personal project (well, an OS -- check out www.brevityos.org if
> you're interested), I need something like test_shell in fullscreen
> mode. The UI is basically an HTML-file with an iframe for every
> document. CSS-classes are used to describe what application is active,
> what documents are active etc.
>
> The problem is that for my project, test_shell performs bad compared
> to Chromium. I have compiled with mode set to release, but it's still
> noticeably slower.
>
> I've watched Darin Fisher and Brett Wilson's presentations about the
> Chromium architecture on YouTube. If I've got it right, then
> test_shell is below the layer that implements multi-processes. Brett
> says that test_shell is based on WebKit glue.
>
> What needs to be done to make test_shell perform as good as Chromium?
> I'm not suggesting that test_shell needs to be changed. I'll probably
> do this in a separate directory under chromium-dir/src, or as a Linux
> port of Chromium Embedded Framework, if Marshall wants CEF to be
> multi-processed.
>
> --
> Best regards,
>
> Alexander Teinum
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
