560781 - the SDK should support development of standalone xulrunner applications

Status: RESOLVED WONTFIX

(Add-on SDK Graveyard :: General, enhancement)

Description

[Dietrich Ayala (:dietrich)]

i poked around the code and found some apparent references to this, but really didn't see where it was pulled together.

afaict, the bare minimum needed to support this is:

1. a way in the manifest for a package to say it's a xulrunner app

2. automatically set up the equivalent of a chrome manifest entry to point to a content directory (which could be the data dir in the `self` module?)

3. a way for packages to specify the xul file in that content dir to use as the value for toolkit.defaultChromeURI.

Comment 1

[James Hartig]

Any update, on what the status of getting chrome registrations? Is there planned support for something like: http://xulforge.com/blog/2010/05/add-on-packaging-spec-2/

Chrome.manifest files work with Firefox 3.x but starting with Firefox 4.x chrome.manifest files are no longer read on bootstrapped addons [1]

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=581862

Comment 2

[Myk Melez [:myk] [@mykmelez]]

The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Duplicate of another bug we wontfixed, don't recall the bug number right now.