NonObligatoricPages: Difference between revisions

From NSIS Wiki
Jump to navigationJump to search
No edit summary
 
m ("Wikified" the headers, and removed the starting "#" characters.)
Line 1: Line 1:
# NonObligatoricPages
{{PageAuthor|Saivert}}
# Written by Saivert <saivert@gmail.com>
 
# Homepage:  http://saivert.inthegray.com/
== Links ==
#
Download 7z archive with script and pre-compiled example here:<br>
# Description:
[http://saivert.inthegray.com/download.php?get=Li91cGxvYWRzL25zaXMvTm9uT2JsaWdhdG9yaWNQYWdlcy43eg==%20NonObligatoricPages.7z NonObligatoricPages.7z] (40 KB)
# Demonstrates how to present a menu to the wizard pages so people don't
 
# have to click Next so many times if they only are going to accept the
== Description ==
# defaults anyway. I'm also one of those who blindly clicks (usually)
Demonstrates how to present a menu to the wizard pages so people don't
# Next button until installer actually extracts files and such.
have to click Next so many times if they only are going to accept the
#
defaults anyway. I'm also one of those who blindly clicks (usually)
# Notes:
Next button until installer actually extracts files and such.
# I call this script NonObligatoricPages as it hides obligatoric pages.
 
# I also only made this script with Modern UI as this is the interface
== Notes ==
# most installers will use anyway. You shouldn't have too much trouble
I call this script NonObligatoricPages as it hides obligatoric pages.
# adapting it to the classic user interface.
I also only made this script with Modern UI as this is the interface
# LogicLob was used as it is a great library which simplifies script
most installers will use anyway. You shouldn't have too much trouble
# writing a great deal.
adapting it to the classic user interface.
# The hope is to integrate NonObligatoricPages with the Modern UI macros
 
# so one can define something and this will be compiled in.
[[LogicLib]] was used as it is a great library which simplifies script
# Another idea I have is to integrate the NonObligatoricPages page with
writing a great deal.
# the Welcome page so you get the buttons below the welcome text.
 
# Maybe use the Link control instead of the buttons so it fits.
The hope is to integrate NonObligatoricPages with the [[Modern UI]] macros
# The License page is also made optional in this example, but you can replace
so one can define something and this will be compiled in.
# this with something else (readme type License Page or perhaps your own IO page).
 
# ---
Another idea I have is to integrate the NonObligatoricPages page with
# Download 7z archive with script and pre-compiled example here:
the Welcome page so you get the buttons below the welcome text.
# [http://saivert.inthegray.com/download.php?get=Li91cGxvYWRzL25zaXMvTm9uT2JsaWdhdG9yaWNQYWdlcy43eg== NonObligatoricPages.7z]
 
Maybe use the Link control instead of the buttons so it fits.
 
The License page is also made optional in this example, but you can replace
this with something else (readme type License Page or perhaps your own IO page).

Revision as of 12:16, 30 June 2005

Author: Saivert (talk, contrib)


Links

Download 7z archive with script and pre-compiled example here:
NonObligatoricPages.7z (40 KB)

Description

Demonstrates how to present a menu to the wizard pages so people don't have to click Next so many times if they only are going to accept the defaults anyway. I'm also one of those who blindly clicks (usually) Next button until installer actually extracts files and such.

Notes

I call this script NonObligatoricPages as it hides obligatoric pages. I also only made this script with Modern UI as this is the interface most installers will use anyway. You shouldn't have too much trouble adapting it to the classic user interface.

LogicLib was used as it is a great library which simplifies script writing a great deal.

The hope is to integrate NonObligatoricPages with the Modern UI macros so one can define something and this will be compiled in.

Another idea I have is to integrate the NonObligatoricPages page with the Welcome page so you get the buttons below the welcome text.

Maybe use the Link control instead of the buttons so it fits.

The License page is also made optional in this example, but you can replace this with something else (readme type License Page or perhaps your own IO page).