On May 12, 4:55 pm, herc <[EMAIL PROTECTED]> wrote:
> 1: Password protecting the closing of the browser.
This is relatively easy to do w/ changes to navigator.js. Except, I
think in general it's trivial for a user to kill the app (see below).
> 2: Preventing the user from swapping to another application (<Alt> +
> <Tab> on Windows).
on windows, the easiest thing to do is make your app *be* the shell.
if it quits, the os will generally respawn it. i don't really remember
if nt precludes task switching, but if it's the shell, then it hardly
matters.
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion
\Winlogon]
Shell=REG_SZ(""path_to_xul_runner" args")
something like that.
> As I stated above, this is a packaged solution. In other words, I am
> selling the software package to folks that don't know a ton about
> computers. I want to simplify things as much as possible for my
> customer (and me if it is possible). I want to distribute my own
> custom install for this kiosk browser. There are two reason: I don't
> want to have to worry about compatibility issues with all the
> different versions of Firefox, and I don't want to muck with the
> users
> Firefox, if they have one installed on the target machine.
Modern versions of firefox allow a command line that can specify a
path to a profile, even one that wouldn't appear in profile manager.
so you can do that if you want.
> My first thought is that, in theory, it should be real simple to take
> the existing Firefox and simply tweak the install to my liking,
> installing one of the already existing kiosk plug-ins and using my
> own
> custom executable to launch as to resolve the two features lacking.
> Can anyone point me to documentation on how to tweak the install in
> such a fashion?
You can easily give your app a different name, but I think you and
your customer are better served by a specific kiosk user that you
create. Advantages should include being able to whitelist which apps
the user can actually run.
> If the first is not practical or possible, then I was thinking of
> possibly writing my own little kiosk system using XULRunner.
>
> Of course, I have a felling there is yet another, better options. I
> am all eyes for any suggestions and tips on how to do it.
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
