Re: [chromium-discuss] Re: Dedicated browser based on chrome

[Joe andrieu]

I concur on the CEF recommendation, although I don't know how much it supports a small file size compared to your current app. You should be able to get the CEFClient demo app up and running in relatively no time and convert that into your "stripped down" browser relatively easily. You can easily restrict browsing to a white list and should be able to add the peripheral integration without touching the underlying Chrome (just tweak the CefClientHandler and CefClientV8FunctionHandler classes). I haven't tried Webkit/Nitro, but the CEF works great for us. -j On 12/23/2009 9:00 AM, dhw wrote: Regarding your main driver of speed, yes, open-source Chromium with V8 and open-source WebKit with Nitro will best fill your speed demands. And you also have free access to these projects' source code for modification. WebKit is definitely one of the fastest rendering engines, used by both Chrome/Chromium and Safari/WebKit. I wonder if your requirements are mainly for rendering speed or do you also need fast _javascript_ speed? In either case, V8 and Nitro will fulfill _javascript_ speed demands as well. If you would like a custom application build around Chromium, you can check out the Chromium Embedded Framework: http://code.google.com/p/chromiumembedded/ Otherwise, you may have to redo your work, download the Chromium sourcecode, and create a stripped down version from that. On Dec 22, 2:46 am, Cees <cees....@gmail.com> wrote: My company is currently working with a 'container' that is based on FF2. Our (web) application supports airport staff with checking in, boarding, load control etc. There are 2 main reasons why we can't use a standard web browser in these environments: 1-There are very specific peripheral devices that need to be supported. it is bit too complex to describe this in detail, but we need to support at least 4 different legacy middleware (common use) systems that run boarding pass printers, bar code scanners etc. Signals from these devices are passed on to the web server. 2-No open browsers are supported due to security regulations on the airport, and if they exist, they are set to maximum security. We resolved these issues by creating our own stripped version of FF2. This version is: -stripped (in order to limit the size of the executable -does not have an address bar. It only contains a set number of URL's (our prod system and some test systems) -able to interact with the airport peripherals (exchanging device addresses) of course this container needed to be certified by the various infrastructure providers, and it needs to be rolled out once. The above solution works. It allows us to roll out a web based application, and run it in airport environments, but rendering of FF2 is dramatic compared to any modern browser, especially Chrome. In short, we want to redo this trick and use Google chrome open source as the base for our new 'container'. Has anyone done something similar before? Are there any suggestions? The main driver is: speed. Cees. -- Joe Andrieu j...@andrieu.net +1 (805) 705-8651 -- Chromium Discussion mailing list: chromium-discuss@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss