We should document it; it's there and it works. There are still a few
outlets for localized text (logComment(), alert(), etc.) and people might
come up with creative uses for it.
For example, the L10n folks could create a template-like install script for
their language packs, and then slap in different properties file that
contain the name of the language and chrome jar to be registered.
-Dan Veditz
Ian Oeschger wrote:
>
> Don't mind at all.
> So what's the 1 param for loadResources(), just a string path to the
> file itself? And if (as I understand you) we don't have a facility for
> displaying the stuff from the properties file, should this go in the API
> for now or stay out?
>
> thanks
> -ian
>
> Dan Veditz wrote:
>
> > Hope you don't mind me CC'ing the newsgroup, others might have these
> > questions too.
> >
> > Ian Oeschger wrote:
> >
> >> From my notes:
> >>
> >> dveditz: What and where is the install log that gets written to in
> >> logComment()? A log doesn't seem to be explicitly created or specified
> >> in the scripts that are using it? Am I seeing some facility for
> >> displaying a web page with the log in it upon completion for web-based
> >> installs?
> >
> >
> > The install log is created in the product directory by default (where the
> > netscape executable is) if it can be, and if we don't have proper permission
> > the install log is written to the user's profile directory.
> >
> >
> >> dveditz: What does loadResources() do? What are the resources?
> >
> >
> > It loads an arbitrary properties file (same format as chrome locale
> > ..properties files) and returns a javascript object whose property names are
> > the keys from that file and the values are the strings. This was requested
> > by international so install scripts could be localized, although there is
> > very little opportunity for XPInstall to display script-generated text at
> > the moment.
> >
> > -Dan Veditz
