Hi Alex, Not sure what this means. Does this mean we can now use jslib to package our XPI as a stand-alone application with XULRunner?
Regards, Eric Jung --- Alex Vincent <[EMAIL PROTECTED]> wrote: > Ladies and gents, for anyone who doesn't read feedhouse.mz.o or > planet.m.o, I've implemented some basic XULRunner packaging support > in > jslib and xpistubs. At the moment, the more generic code in xpistubs > only supports packaging chrome code (not components, defaults, etc.). > However, it is relatively trivial to add support for the other > directories. > > Basically, the generated .tar.bz2 files contain a > chrome/(project_name).manifest.inc file, which you unzip into your > application's directory. It should only add files, or replace files > from the same subproject already there. Application developers who > use these tarballs are supposed to merge the various .inc files into > chrome/chrome.manifest. > > I do not include application.ini, install.rdf, or any other files > specific to the master application. This is to protect application > developers from having their own files inadvertently overwritten. > So don't expect to find a complete out-of-the-box XULRunner > application in any of these tarballs. > > Let me know if you need any help with this! If you feel like testing > it and giving feedback, I'd appreciate that too. > > Alex Vincent > Santa Cruz, CA > > -- > "The first step in confirming there is a bug in someone else's work > is > confirming there are no bugs in your own." > -- Alexander J. Vincent, June 30, 2001 > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
