I thought that it would be good if WIHU could build the tree of applications to install at runtime (not hard coded in the INI file).
Here is my reasoning:
To make a small tree with only 2 applications (and 2 add-ons) like this:
. [x] Main . \- [x] Common Applications . |- [x] Textpad 4.7.3 . \- [x] Opera 7.23 . |- [x] ASpell 0.50.3.3 . \- [x] ASpell English Dictionary
Currently your install.ini would contain something like this:
command.0.0=.\Applications\Textpad\txpeng473.exe /S /v/qn /Reboot=Suppress
description.0.1.1=ASpell English Dictionary
If your going to keep your install files in subdirectory why not keep the ini section needed to run the install file in the same folder... And use the existing hierarchy in the file system can be used to help build the tree... that way you can delete, add or rearrange applications in your
Install folder without having to keep the install.ini up to date..
So you could have your install.ini (with the users and environment etc) and have a small ini files located with each application.
With my change you could have files arranged like this:
Contains the normal users and environment configuration and a separate section to trigger search. eg:
; Search Sub folders for wihu.ini files
Only the name for displaying in tree as a header eg:
Note: if this ini file was missing Textpad and Opera would be moved up the tree.
Contains just enough to specify install of textpad eg:
command=txpeng473.exe /S /v/qn /Reboot=Suppress
Contains just enough to specify install of opera and using the current nested syntax the spell checker and dictionary eg:
description.1=ASpell English Dictionary
Do you store installs in a tree of folders ? if so, how many folders/subfolders do you have ? (I need to get an idea of how much I would have to search)
Do you think you it would be good if you could move, delete, add or rename files in your install folder and not need to update the install.ini?