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. Making the rendering part of Chromium easier to use for open source project would benefit projects such as mine or uzbl for instance. uzbl is a WebKitGTK+ browser that is controlled similar to Vim. I realize that CEF is an effort at making it easier to embed Chromium, but if it's based on test_shell, then well... what about the platform optimalizations? Are they easy to get into CEF, or does it have to play catch-up? On Fri, Nov 6, 2009 at 12:21 AM, Mohamed Mansour <m...@chromium.org> wrote: > On Thu, Nov 5, 2009 at 5:33 PM, Peter Kasting <pkast...@google.com> wrote: >> >> On Thu, Nov 5, 2009 at 1:51 PM, Nico Weber <tha...@chromium.org> wrote: >>> >>> http://codereview.chromium.org/244003/show might be what you want. >> >> I thought this was intentionally abandoned because it was growing out of >> control. That's what I was alluding to before. > > Not entirely abandoned, true it was getting out of control and that is why I > stopped to take a step back. Technically it should be what I did for patch > set one, which is just fullscreen + no statusbar. That is basically what the > functionality is. I will continue working on it tonight. > - Mohamed Mansour > > > > -- Best regards/Med vennlig hilsen, Alexander Teinum --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
