Known bugs and stuff I have to do
This will be fixed/added in the next release
- When uninstalling LOSI the user can end up without a shell. Go back to the previous shell when uninstalling if that .exe file still exists, otherwise go back to explorer and reset all registry entries to default.
- Running an XP system, no alt-shell ever installed, so Explorer was running during installation. I did a custom install, but selected everything to install. The only pre-req missing was the optional vc9 runtimes, and I didn't install those. I chose to install "only for current user" and chose to install no profile support. I installed to C:\shells\litestep. The default theme for LS/LOSI was running when I uninstalled. [jugg]
- Currently if a litestep.exe process is detected during the install this process is killed. This is done to make it possible to upgrade the Litestep you are currently using. However, if no litestep.exe is found in the directory the user is installing to, it isn't needed to kill litestep.exe.
- Make it clearer what the "How do you want to install LiteStep" page does. Maybe by adding some descriptive text and rewording the options.
Todo for future releases
- The uninstaller removes LS even though other users might still be using it.
- There seems to be some kind of issue regarding how many start menu folders gets created, and where they're created. [Xjill, Andymon]
- Don't kill the current shell (unless we're upgrading/updating) and don't start LS untill the very last page of the installer where there should be an option to start LS or not.
- Make the "Set as shell for all users" option actually do what it says. This is done by setting the shell in HKLM and not in HKCU and by keeping the IniFileMappings at the "SYS;..." setting. Make sure the "install without rebooting" feature doesn't break.
- Maybe $texteditor$ should be used when associating files. It needs some investigation to make sure it works in all possible cases and that there aren't any weird side effects. Fall back on the program that is registered to handle .txt files if $texteditor$ doesn't point to a valid .exe
- Investigate how well LOSI works on win9x. Is a special "9x theme" needed?
- Do something regarding the need to !recycle after updating evars. At the very least, tell the user it needs to be done. Maybe automaticly running !reload.
- Make sure there are no other instances of the installer running. http://nsis.sourceforge.net/Allow_only_one_installer_instance
- New page with settings for which files to keep when overwriting an old install. Also option to backup old personal files (this is just a messagebox right now). The default should be to back up all files and to not keep any old files.
- When backing up old files, move all the old files to the backup directory, and then install the new files. So if the user had created any files in the personal\ folder himself, these should be backed up and they should not exist in the new personal\ folder. (I.e. move the files instead of copying them.) [fractal.design]
- Append date/time to the backup folder when backing up old personal files during the install. [fractal.design]
- Include GS in the standard install and make use of it in InstDef
- GUI for editing hotkeys.
- GUI for editing popup menu.
- Some kind of LS control panel that groups all the utils.
- Add support for custom shells in SetShell.
- Add the ability to install fonts and wallpapers (user should be able to turn this feature off) (theme.ini).
- Update InstDef to latest clickonic version. Make some pretty gradients using xPaintClass. Add some kind of time display.
Low priority
- Support for silent install. This will have to wait untill I feel LOSI is more or less done.
- A "portable" install option for installing to USB sticks and the like. This will also have to wait.
- Add a theme packager.
- Make it possible to choose the default theme that the ThemeSwitcher returns to.
Meaning of the colors: This is a normal bug, This is a severe bug, This is something I'm thinking about adding