Custom Finish Page - Revision history

150.101.113.163: /* INI file structure */

2006-11-15T00:25:15Z

INI file structure

â† Older revision		Revision as of 00:25, 15 November 2006
Line 117:		Line 117:
	== INI file structure ==		== INI file structure ==

	I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format HM NIS Edit creates		I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format [http://hmne.sourceforge.net/ HM NIS Edit] creates
	This example has 2 text boxes, its easy enough to make out what each of the settings are.		This example has 2 text boxes, its easy enough to make out what each of the settings are.
	This is the finishfull_all.ini file. For the different components, change the contents of field 2 and then save them as the appropriate filename.		This is the finishfull_all.ini file. For the different components, change the contents of field 2 and then save them as the appropriate filename.

	; Ini file generated by the ~~[http://hmne.sourceforge.net/~~ HM NIS Edit] IO designer.		; Ini file generated by the HM NIS Edit IO designer.
	[Settings]		[Settings]
	NumFields=2		NumFields=2

150.101.113.163: /* NSIS Script */

2006-11-15T00:19:17Z

NSIS Script

â† Older revision		Revision as of 00:19, 15 November 2006
Line 20:		Line 20:
	<highlight-nsis>		<highlight-nsis>
	Var netcf		Var netcf
	~~</highlight-nsis>~~
	~~<highlight-nsis>~~
	Var app		Var app
	~~</highlight-nsis>~~
	~~<highlight-nsis>~~
	Var map		Var map
	</highlight-nsis>		</highlight-nsis>
Line 32:		Line 28:
	# Process installing netcf component		# Process installing netcf component
	StrCpy "netcf" "installed"		StrCpy "netcf" "installed"
			</highlight-nsis>
			<highlight-nsis>
	# Process installing app		# Process installing app
	StrCpy "app" "installed"		StrCpy "app" "installed"
			</highlight-nsis>
			<highlight-nsis>
	# Process installing map		# Process installing map
	StrCpy "map" "installed"		StrCpy "map" "installed"

150.101.113.163: /* NSIS Script */

2006-11-15T00:18:34Z

NSIS Script

â† Older revision		Revision as of 00:18, 15 November 2006
Line 20:		Line 20:
	<highlight-nsis>		<highlight-nsis>
	Var netcf		Var netcf
			</highlight-nsis>
			<highlight-nsis>
	Var app		Var app
			</highlight-nsis>
			<highlight-nsis>
	Var map		Var map
	</highlight-nsis>		</highlight-nsis>

150.101.113.163: /* NSIS Script */

2006-11-15T00:17:09Z

NSIS Script

â† Older revision		Revision as of 00:17, 15 November 2006
Line 12:		Line 12:

	When setting the pages in the order you want, replace the default finish page with		When setting the pages in the order you want, replace the default finish page with
			<highlight-nsis>
	# Custom finish page to show what was installed		# Custom finish page to show what was installed
	Page custom finishfull		Page custom finishfull
			</highlight-nsis>

	You need to set variables for each component, in this case i have 3, the .net compact framework, my app, and the map used by the app		You need to set variables for each component, in this case i have 3, the .net compact framework, my app, and the map used by the app
			<highlight-nsis>
	Var netcf		Var netcf
	Var app		Var app
	Var map		Var map
			</highlight-nsis>

	When you are installing the component, write the value "installed" (can be anything) to the components variable.		When you are installing the component, write the value "installed" (can be anything) to the components variable.
			<highlight-nsis>
	# Process installing netcf component		# Process installing netcf component
	StrCpy "netcf" "installed"		StrCpy "netcf" "installed"
Line 33:		Line 34:
	# Process installing map		# Process installing map
	StrCpy "map" "installed"		StrCpy "map" "installed"
			</highlight-nsis>
	This is the function that the custom finish page calls		This is the function that the custom finish page calls
			<highlight-nsis>
	Function finishfull		Function finishfull
	${If} $netcf == ""		${If} $netcf == ""
Line 95:		Line 96:
	${EndIf}		${EndIf}
	FunctionEnd		FunctionEnd
			</highlight-nsis>

	These are the ini files for the different combinations of components that can be installed		These are the ini files for the different combinations of components that can be installed
	they need to be extracted on the installers initialization		they need to be extracted on the installers initialization
			<highlight-nsis>
	Function .onInit		Function .onInit
	!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_none.ini" "finishfull_none"		!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_none.ini" "finishfull_none"
Line 110:		Line 111:
	!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_all.ini" "finishfull_all"		!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_all.ini" "finishfull_all"
	FunctionEnd		FunctionEnd
			</highlight-nsis>

	== INI file structure ==		== INI file structure ==

150.101.113.163: /* NSIS Script */

2006-11-15T00:16:15Z

NSIS Script

â† Older revision		Revision as of 00:16, 15 November 2006
Line 7:		Line 7:

	You need to include LogicLib to use ${If} ${Else} etc..		You need to include LogicLib to use ${If} ${Else} etc..
			<highlight-nsis>
	!include "LogicLib.nsh"		!include "LogicLib.nsh"
			</highlight-nsis>

	When setting the pages in the order you want, replace the default finish page with		When setting the pages in the order you want, replace the default finish page with
Line 110:		Line 110:
	!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_all.ini" "finishfull_all"		!insertmacro MUI_INSTALLOPTIONS_EXTRACT_AS "assets\finishfull_all.ini" "finishfull_all"
	FunctionEnd		FunctionEnd


	== INI file structure ==		== INI file structure ==

Zeb: /* INI file structure */

2006-11-14T23:35:46Z

INI file structure

â† Older revision		Revision as of 23:35, 14 November 2006
Line 116:		Line 116:
	I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format HM NIS Edit creates		I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format HM NIS Edit creates
	This example has 2 text boxes, its easy enough to make out what each of the settings are.		This example has 2 text boxes, its easy enough to make out what each of the settings are.
	This is the finishfull_all.ini file		This is the finishfull_all.ini file. For the different components, change the contents of field 2 and then save them as the appropriate filename.

	; Ini file generated by the [http://hmne.sourceforge.net/ HM NIS Edit] IO designer.		; Ini file generated by the [http://hmne.sourceforge.net/ HM NIS Edit] IO designer.

Zeb: /* Creating custom finish page displaying components installed */

2006-11-14T23:34:10Z

Creating custom finish page displaying components installed

â† Older revision		Revision as of 23:34, 14 November 2006
Line 1:		Line 1:
	== Creating custom finish page displaying components installed ==		== Creating custom finish page displaying components installed ==

	You will need to add code to your nsi script and there is INI files to be created too		You will need to add code to your nsi script and there is INI files to be created too.
			The basic theory is, you have a variable for each component. When you install each component, you set its variable, then when it comes to the finish page, depending on the combination of variables set, it will display the appropriate finish page.

	== NSIS Script ==		== NSIS Script ==

Zeb: /* INI file structure */

2006-11-14T23:32:12Z

INI file structure

â† Older revision		Revision as of 23:32, 14 November 2006
Line 112:		Line 112:

	== INI file structure ==		== INI file structure ==
	~~----~~
	I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format HM NIS Edit creates		I strongly recommend using [http://hmne.sourceforge.net/ HM NIS Edit] to create these files. It is very difficult to get an idea of what it will look like when just writing text, but here's the format HM NIS Edit creates
	This example has 2 text boxes, its easy enough to make out what each of the settings are.		This example has 2 text boxes, its easy enough to make out what each of the settings are.

Zeb: /* Creating custom finish page displaying components installed */

2006-11-14T23:23:27Z

Creating custom finish page displaying components installed

â† Older revision		Revision as of 23:23, 14 November 2006
Line 1:		Line 1:
	== Creating custom finish page displaying components installed ==		== Creating custom finish page displaying components installed ==

	You will need to add code to your nsi script and there is [[INI files]] to be created too		You will need to add code to your nsi script and there is INI files to be created too

	== NSIS Script ==		== NSIS Script ==

Zeb: /* Creating custom finish page displaying components installed */

2006-11-14T23:22:50Z

Creating custom finish page displaying components installed

â† Older revision		Revision as of 23:22, 14 November 2006
Line 1:		Line 1:
	== Creating custom finish page displaying components installed ==		== Creating custom finish page displaying components installed ==

	You will need to add code to your nsi script and there is INI files to be created too		You will need to add code to your nsi script and there is [[INI files]] to be created too

	== NSIS Script ==		== NSIS Script ==