Re: Xulrunner upgrade from 1.9 to 6.0.2

On Sep 24, 4:15 am, Philipp Wagner <[email protected]> wrote:
> Am 21.09.2011 02:06, reverendlinux wrote:
>
>
>
>
>
>
>
>
>
> > On Sep 20, 5:56 am, Pernot Christian<[email protected]>  wrote:
> >> Le 20/09/2011 08:43, Rohit Sarpotdar a écrit :
>
> >>> After I enabled -jsconsole, I got following message on console.
>
> >>> Could not read chrome manifest file '/home/user/application/version/appclient/chrome.manifest'.
>
> >>> Is there any structure wide changes from 4.0 version? If any, where I can find documentation about it?
>
> >> some important detail : create a chrome.manifest file at the root of
> >> yout app, containing "manifest chrome/chrome.manifest".
>
> >> see :https://developer.mozilla.org/en/Firefox_4_for_developers#Other_chang...
> >> slow or unavailable at this time)
>
> > @Rohit - Tried the -jconsole option.  Neither it nor my application
> > appeared.
>
> Just to make sure you don't have a typo: it's -jsconsole
>
> > @Pernot - Also tried adding a chrome.manifest file to the root dir of
> > my app ( ie - /home/<user>/bin/<xulapp>/chrome.manifest ).  No change.
>
> You need a chrome.manifest in this dir, yes. And you need to include all
> other manifests using the manifest keyword or merge them all into the
> chrome.manifest at your application directory.
>
> If you still have problems, please post some relevant parts of your code
> (e.g. the manifest files).
>
> Philipp

Yup, the post above was a typo.  I was using -jsconsole.  I really
need to stop working so late at night on this stuff.

I finally fixed the problem.  After reading through the Getting
Started with XULRunner page again, I triple checked my manfiests.  I
created a new chrome.manifest in my application root with this as the
contents:
     manifest chrome/chrome.manifest

Next I made sure my other chrome.manifest was in /<approot>/chrome and
had the following content (note that scdb is my app name):
     content scdb file:content/

I then removed a manifest called scdb.manifest from my /approot/chrome
dir.

Finally, I made sure there were no other legacy manifest files laying
around.

With these changes, my app started.  So it looks like I was a victim
of changing dir/file structures and not keeping up to date on the
changes made to XULRunner.  One nit to pick though.  I do hope this is
the last time they make significant changes of this nature.  I'd hate
to have to do this sort of fix with every major release.