You could write an NPAPI extension that interfaces with the peripherals and run stock chrome in kiosk mode (Pass chrome the flag --kiosk when starting it). That should get you most of the way there without requiring changes to chrome's code.
If that actually works depends on if the extension system lets you do what you want. On Wed, Dec 23, 2009 at 10:53 AM, Nico Weber <[email protected]> wrote: > You could write an NPAPI extension that interfaces with the > peripherals and run stock chrome in kiosk mode (Pass chrome the flag > --kiosk when starting it). That should get you most of the way there > without requiring changes to chrome's code. > > If that actually works depends on if the extension system lets you do > what you want. > > On Tue, Dec 22, 2009 at 2:46 AM, Cees <[email protected]> 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. >> >> -- >> Chromium Discussion mailing list: [email protected] >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-discuss >> > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
