[Nvda-dev] Installer/uninstaller with logging capability, seeking your thoughts

[Jason SW]

Hello,
I vote for "unattended".
Interactive is ok, but ... If you've got a lot of files not created by the 
installer, you might have to go through possibly tens or hundreds of 
confermation dialog boxes. Perhaps, if there is an option to do this, there 
could be a "yes to all" and a "no to all" button, or perhaps just make 
interactive ask whether you wanted to delete *every* file in the \nvda 
directory, or just the files created by the installer, and probably include 
a warning to go over all files and consider this question carefully, etc, 
etc, blah blah.

Jason.
----- Original Message ----- 
From: "Victor Tsaran" <vtsaran at yahoo.com>
To: "Development for NonVisual Desktop Access" <nvda-dev at lists.nvaccess.org>
Sent: Friday, May 23, 2008 5:20 PM
Subject: [Nvda-dev] Installer/uninstaller with logging capability,seeking 
your thoughts


>
>
> Hi all,
> I just implemented logging system for NVDA installer. Basically, as NVDA 
> copies files/folders during installation, the installer will keep track of 
> those files and store in a log file. During uninstallation, uninstaller 
> reads the log and deletes only those files/folders that were created 
> during installation.
> The new installer has two modes, interactive and unattended. If we decided 
> on an "interactive" mode, the user will be asked to confirm deletion of 
> every file that was created outside of installation process, i.e. you 
> manually added some app modules or other NVDA-related files. Unattended 
> mode, on the other hand, will not ask the user and only delete the files 
> that were installed during installation, leaving all other files intact.
> I think that this logging approach is a necessary way forward as users 
> will start adding or sharing modules of their own. This way we make sure 
> that uninstaller does not delete files that were not created by the 
> installer in the first place.
> Which mode do you think we should set as a default? Unfortunately, this 
> cannot be user's choice, I have to set it in the installation script.
>
> Let me know.
> Victor
>
>
>
> _______________________________________________
> Nvda-dev mailing list
> Nvda-dev at lists.nvaccess.org
> http://lists.nvaccess.org/listinfo/nvda-dev