Well, Mohamed's patch is *way* simpler and portable.
On Fri, Sep 25, 2009 at 12:40 PM, Amit Joshi <a...@chromium.org> wrote:
> Sorry for not being clear. What I meant was that you could create your own
> kiosk shell and embed Chrome Frame as ActiveX control to render the pages
> you want in it. That way you could customize different features up to your
> own satisfaction.
>
> On Fri, Sep 25, 2009 at 5:30 AM, Mohamed Mansour <m...@chromium.org> wrote:
>>
>> I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode
>> flag is set. If the Kiosk mode is set ( iexplorer.exe -k
>> http://www.google.com ) it renders it as IE Renderer. It renders it fine in
>> a Chrome Frame if its not in Kiosk mode. That must be a bug :)
>> For IE, kiosk mode has a context menu, but people usually apply the
>> registry tweak to remove context menu from IE if they need to.
>> For Chromium, it would be nice if stuff like this would be an extension,
>> an extension should allow us to show/hide various parts of the UI. In the
>> meantime, I quickly compiled a custom Chromium so that my CEO and VP could
>> see the benefits of using Chrome instead of IE on some of our web products.
>>
>> Stuff that would be cool and would be very lightweight to include for
>> kiosk mode would be:
>> - No Status Bar
>> - Full Screen (with no exit, only alt+f4 should work)
>> - No Context Menus (should be an option)
>> - Disable downloading of files.
>> - No tabs
>> - No opening files
>> - many more
>> I would rather that be an extension (but there are currently no way to
>> actually block users to remove extensions, maybe blocking users entering a
>> url would suffice) but not possible currently.
>> -Mohamed
>>
>>
>> On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi <a...@chromium.org> wrote:
>>>
>>>
>>> On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher <da...@chromium.org>
>>> wrote:
>>>>
>>>> Chrome Frame is a good option, but you'd still need a way to turn off
>>>> some features. For example, a kiosk probably doesn't want to have a
>>>> context
>>>> menu.
>>>
>>> Chrome Frame can/will offer control over the context menu. This is
>>> exactly the kind of customization Chrome Frame can offer. Too bad we don't
>>> have Linux, Mac versions yet, but we are open source now so patches welcome
>>> :)
>>>>
>>>> -Darin
>>>>
>>>> On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi <a...@chromium.org> wrote:
>>>>>
>>>>> I think you should really consider embedding chrome frame ActiveX in
>>>>> your own simple shell. That will not only enable the application to be
>>>>> started with desired real estate and get rid of status bubble but allow
>>>>> you
>>>>> to customize it further if needed.
>>>>>
>>>>> On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher <da...@chromium.org>
>>>>> wrote:
>>>>>>
>>>>>> On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour <m...@chromium.org>
>>>>>> wrote:
>>>>>>>
>>>>>>> At work today, I talked to the CEO of my company to ship Chrome
>>>>>>> browser with all our Kiosk's and recommended Chrome to be our default
>>>>>>> browser for our web products. I bench marked our current web
>>>>>>> applications
>>>>>>> with Chrome (ToT) vs IE 7, and our applications run at average 10 times
>>>>>>> faster. (For windows, Mac speed differed)
>>>>>>> There are some stuff that he didn't like:
>>>>>>>
>>>>>>> Status Bubble: for a cashiering application, it keeps popping up
>>>>>>> every second since buttons are all over the place. It was distracting
>>>>>>> him
>>>>>>> from the main product.
>>>>>>> Full screen mode "always" => Kiosk Mode. He wants the web app to stay
>>>>>>> full screen, in IE, there is kiosk mode command line switch. In FF
>>>>>>> there is
>>>>>>> a plugin.
>>>>>>> JavaScript errors kept appearing intermittently (on the Mac), would
>>>>>>> work on initial deploy but require a "Clear browsing data" on subsequent
>>>>>>> runs. Works great on windows (chrome). I guess we would be using
>>>>>>> linux/windows for kiosk anyhow.
>>>>>>>
>>>>>>> Will there be plans for us to introduce Kiosk Mode in Chrome? It
>>>>>>> seems the current audience is just targeted towards home users and
>>>>>>> there is
>>>>>>> no way to use Google Chrome for other usages.
>>>>>>> Sure we could compile our own Chromium version, but many people
>>>>>>> (Chrome forums and elsewhere) would like to use Chrome commercially. In
>>>>>>> the
>>>>>>> meantime, I am going to compile a version with no status bar, but I
>>>>>>> believe
>>>>>>> it would be nice to include it in future versions.
>>>>>>> Maybe we could allow extensions to control (hide/show) different
>>>>>>> areas in chrome.
>>>>>>
>>>>>>
>>>>>> Maybe I'm in the minority, but it doesn't sound that unreasonable to
>>>>>> support command line options for disabling the status bubble and
>>>>>> starting in
>>>>>> full screen mode. We could lump these together into a --kiosk-mode
>>>>>> command
>>>>>> line flag. This seems like something that could be done in a fairly
>>>>>> lightweight manner.
>>>>>> Maybe others object?
>>>>>> -Darin
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
