The main reason for using installChrome is that it's a simplified install --
you don't have to do any install scripts or anything. Unfortunately the
manifest.rdf structure it requires is a bit different than shipping modern,
which re-complicates it. In a future version we should make installChrome
smart enough to handle distributed content.rdf files.
As for "safe", it turns off an obscure scripted behaviors feature, which
none of our skins happen to use anyway.
-Dan Veditz
Ian Oeschger wrote:
>
> ...and what's the 25-words-or-less on "safe" installs again, like
> installChrome() does? It doesn't allow you to install scripts that can
> ______.
>
> Thanks, Dan
> -ian
>
> Daniel Veditz wrote:
>
> > Ian Oeschger wrote:
> >
> >> ...and does somebody has a prototype lying around for installChrome()?
> >> It looks like installChrome( flags, file, name/version), but I'd love to
> >> get some description of the params--of the available options, in
> >> particular.
> >
> >
> > installChrome( TYPE, url, name ), where
> >
> > TYPE can be InstallTrigger.SKIN or InstallTrigger.LOCALE
> >
> > url is a string containing a full or relative URL to download
> >
> > name is displayed in the dialog, but is also used to *select* the theme so
> > must match exactly the name in the internal manifest.rdf file.
> >
> > The name used for selecting a theme is pretty ugly when shown on the dialog.
> > In the future we might want to consider a fourth parameter for a dialog
> > name.
> >
> > -Dan Veditz
