XUL Talk:Installation Story: Difference between revisions
Thumperward (talk | contribs) (→NSIS work: fixing URLs) |
Thumperward (talk | contribs) |
||
| Line 13: | Line 13: | ||
== NSIS work == | == NSIS work == | ||
I've got an NSIS script which can deploy | I've got an NSIS wrapper script which can deploy XULRunner apps. It fulfils most of the Microsoft-lover use case. | ||
Installer: [http://thumper.kicks-ass.org/ChatZilla-net-stub-setup.exe] | ChatZilla / XULRunner Installer: [http://thumper.kicks-ass.org/ChatZilla-net-stub-setup.exe] | ||
Script: [http://thumper.kicks-ass.org/net-bundle-setup.nsi] | Script: [http://thumper.kicks-ass.org/net-bundle-setup.nsi] | ||
| Line 22: | Line 22: | ||
1. Because -install-apping something doesn't add shortcuts at the moment, I'm doing it myself in NSIS. This only means setting a variable in the install script, but it means that it isn't fully generalised. This should really change. | 1. Because -install-apping something doesn't add shortcuts at the moment, I'm doing it myself in NSIS. This only means setting a variable in the install script, but it means that it isn't fully generalised. This should really change. | ||
2. | 2. There isn't currently a way of querying XULrunner to find out how many apps are installed. This means uninstall is all-or-nothing at the moment. | ||
3. | 3. The "install an XPI if you're using Firefox and an exe if not" thing seems really awkward to me. XULrunner apps are independent of the browser anyway. It means that XULrunner will have to go around generating its own uninstallers and so on, and that sites will have to keep two downloads (an xpi and an exe) and use a js install trigger rather than just providing download links. This is really a niggle with the spec. | ||
[[User:Thumperward|Thumperward]] 14:38, 7 Feb 2006 (PST) | |||
Revision as of 13:19, 12 February 2006
Benjamin:
I think what you have specified here is excellent.
What would happen if the user is using a Mozilla browser that dose not use XULRunner. I assume that it would fallback to the exe?
We also need to think about, what if the user is using Firefox on XULRunner 1.8 and he clicks on an app that needs XULRunner 1.9. We need to then prompt him that he needs to install the new version.
Where would the list of apps installed for XULRunner reside?
Gary 08:27, 23 Nov 2005 (PST)
NSIS work
I've got an NSIS wrapper script which can deploy XULRunner apps. It fulfils most of the Microsoft-lover use case.
ChatZilla / XULRunner Installer: [1] Script: [2]
Issues at the moment:
1. Because -install-apping something doesn't add shortcuts at the moment, I'm doing it myself in NSIS. This only means setting a variable in the install script, but it means that it isn't fully generalised. This should really change.
2. There isn't currently a way of querying XULrunner to find out how many apps are installed. This means uninstall is all-or-nothing at the moment.
3. The "install an XPI if you're using Firefox and an exe if not" thing seems really awkward to me. XULrunner apps are independent of the browser anyway. It means that XULrunner will have to go around generating its own uninstallers and so on, and that sites will have to keep two downloads (an xpi and an exe) and use a js install trigger rather than just providing download links. This is really a niggle with the spec.
Thumperward 14:38, 7 Feb 2006 (PST)