I was asked if I could add a command line arg to toggle "Load desktop before install". It is no big deal to add it. But why stop there? Would you want to see all (or nearly all) options be changable via a command line arg?
WPI.hta options=myoptions.js ShowExtraButtons=true InstallByCategory=false ShowCommandLineInInstaller=true
This would temporarily override your saved settings.
Whatcha think?
Page 1 of 1
Command line args Change all/most options
#2
Posted 30 December 2008 - 07:31 PM
mritter, I'm sure it would be useful, but I have never used switches and think I am OK with what I have. Some may feel strongly that they would be useful. Enjoy, John.
#3
Posted 30 December 2008 - 08:10 PM
OMG wow...
I personally think thats overkill m8.
config, options, and time should be plenty...
I personally think thats overkill m8.
config, options, and time should be plenty...
#4
Posted 01 January 2009 - 10:45 AM
Happy new Year!!!
I think this is a good idea. :-)
Some options are really necessary - some maybe not.
So we could vote for options we want to have also available on commandline.
But: Maybe there is a user which needs an option for a very specific case which is not in the list. So why not implement something like a Map (or Dictionary in JS?) which holds all config-settings (key = config-key, value = config-value) and is initialized with default-values and can be overwritten with command-line-arguments.
e.g. settings['options'] = './WPIScripts/config.js';
if [command_line_has_options_argument] settings['options'] = get_argument_from_command_line
So you have
- all settings at one place
- can easily extend it
- can easily overwrite all settings with command-line-arguments
Al
I think this is a good idea. :-)
Some options are really necessary - some maybe not.
So we could vote for options we want to have also available on commandline.
But: Maybe there is a user which needs an option for a very specific case which is not in the list. So why not implement something like a Map (or Dictionary in JS?) which holds all config-settings (key = config-key, value = config-value) and is initialized with default-values and can be overwritten with command-line-arguments.
e.g. settings['options'] = './WPIScripts/config.js';
if [command_line_has_options_argument] settings['options'] = get_argument_from_command_line
So you have
- all settings at one place
- can easily extend it
- can easily overwrite all settings with command-line-arguments
Al
- ← WPI for Legacy OS'es thread location and discussion!
- Windows Post-Install Wizard (WPI)
- Save Options/Config paths →
Share this topic:
Page 1 of 1



Help
Back to top









