XUL Talk:Installation Story - Revision history

Bvleur: /* Alternatives to Launch When Finished chekcbox on the last page */

2006-02-20T21:07:00Z

Alternatives to Launch When Finished chekcbox on the last page

← Older revision		Revision as of 21:07, 20 February 2006
Line 35:		Line 35:
	* Add it as an extra option next to the shortcut questions.		* Add it as an extra option next to the shortcut questions.
	* Replace the finish button by two buttons: [Launch Now] and [Close Installer]. One could probably assume that if the user picks [Launch Now] he also is done using the installer and the installer can be closed.		* Replace the finish button by two buttons: [Launch Now] and [Close Installer]. One could probably assume that if the user picks [Launch Now] he also is done using the installer and the installer can be closed.

			[[User:bvleur]] 22:06, 20 Feb 2005 (CET)

Bvleur: Alternatives to Launch When Finished chekcbox on the last page

2006-02-20T21:04:47Z

Alternatives to Launch When Finished chekcbox on the last page

← Older revision		Revision as of 21:04, 20 February 2006
Line 27:		Line 27:

	[[User:Thumperward\|Thumperward]] 14:38, 7 Feb 2006 (PST)		[[User:Thumperward\|Thumperward]] 14:38, 7 Feb 2006 (PST)

			== Alternatives to Launch When Finished chekcbox on the last page ==

			The ''[x] Launch Hexagonal Minesweeper When Finished'' is asking for an installation "option" while already installing which doesn't seem right. Furthermore it says ''When Finished'', while the actual installation may be finished already which might confuse the user.

			I can think of two alternatives:
			* Add it as an extra option next to the shortcut questions.
			* Replace the finish button by two buttons: [Launch Now] and [Close Installer]. One could probably assume that if the user picks [Launch Now] he also is done using the installer and the installer can be closed.

Thumperward: /* NSIS work */

2006-02-12T13:19:52Z

NSIS work

← Older revision		Revision as of 13:19, 12 February 2006
Line 13:		Line 13:
	== NSIS work ==		== NSIS work ==

	I've got an NSIS script which can deploy ~~XULrunner, register it and then install~~ apps. It ~~adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly~~.		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. ~~I can~~'t ~~see~~ a ~~documented~~ way of querying XULrunner to find out how many apps are installed. This means uninstall is all-or-nothing at the moment.		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. ~~Ideally the installer~~ exe ~~contains only~~ the ~~xulapp wrapped in nsis~~. ~~I haven't added the logic required~~ to ~~check for an existing system xulrunner~~ and ~~net-install one if it isn't available~~, ~~but I don't expect~~ that to ~~take more~~ than a ~~night~~.		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.

	4. 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.		[[User:Thumperward\|Thumperward]] 14:38, 7 Feb 2006 (PST)

	~~Of these, the difficulty in order from hardest is 2, 1, 3 with 4 being a technical niggle with the spec.~~ [[User:Thumperward\|Thumperward]] 14:38, 7 Feb 2006 (PST)

Thumperward: /* NSIS work */ fixing URLs

2006-02-08T19:25:12Z

NSIS work: fixing URLs

← Older revision		Revision as of 19:25, 8 February 2006
Line 15:		Line 15:
	I've got an NSIS script which can deploy XULrunner, register it and then install apps. It adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly.		I've got an NSIS script which can deploy XULrunner, register it and then install apps. It adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly.

	Installer: [http://thumper.kicks-ass.org/~~chatzilla~~-~~xulrunner~~-setup.exe]		Installer: [http://thumper.kicks-ass.org/ChatZilla-net-stub-setup.exe]
	Script: [http://thumper.kicks-ass.org/~~xulrunnerinstall~~.nsi]		Script: [http://thumper.kicks-ass.org/net-bundle-setup.nsi]

	Issues at the moment:		Issues at the moment:

Thumperward: /* NSIS work */

2006-02-07T23:16:16Z

NSIS work

← Older revision		Revision as of 23:16, 7 February 2006
Line 14:		Line 14:

	I've got an NSIS script which can deploy XULrunner, register it and then install apps. It adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly.		I've got an NSIS script which can deploy XULrunner, register it and then install apps. It adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly.

			Installer: [http://thumper.kicks-ass.org/chatzilla-xulrunner-setup.exe]
			Script: [http://thumper.kicks-ass.org/xulrunnerinstall.nsi]

	Issues at the moment:		Issues at the moment:

Thumperward: NSIS work

2006-02-07T22:38:35Z

NSIS work

← Older revision		Revision as of 22:38, 7 February 2006
Line 10:		Line 10:

	[[User:Garyvdm\|Gary]] 08:27, 23 Nov 2005 (PST)		[[User:Garyvdm\|Gary]] 08:27, 23 Nov 2005 (PST)

			== NSIS work ==

			I've got an NSIS script which can deploy XULrunner, register it and then install apps. It adds shortcuts and appropriate registry entries to get things like irc:// links working in ChatZilla, and uninstalls cleanly.

			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. I can't see a documented way of querying XULrunner to find out how many apps are installed. This means uninstall is all-or-nothing at the moment.

			3. Ideally the installer exe contains only the xulapp wrapped in nsis. I haven't added the logic required to check for an existing system xulrunner and net-install one if it isn't available, but I don't expect that to take more than a night.

			4. 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.

			Of these, the difficulty in order from hardest is 2, 1, 3 with 4 being a technical niggle with the spec. [[User:Thumperward\|Thumperward]] 14:38, 7 Feb 2006 (PST)

Garyvdm at 16:27, 23 November 2005

2005-11-23T16:27:49Z

New page

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?

[[User:Garyvdm|Gary]] 08:27, 23 Nov 2005 (PST)