The Current KORA Installer suffers from several flaws:
1) It requires a root database connection (which most people don't have)
2) It insists on creating a new database instead of allowing installs into an existing one
3) If an administrator password is deemed not complex enough, it goes ahead with the installation, selecting a random password, which is notified in text in an area of the page few users read. Ideally, it should not start installing until a user provides a complex enough password
4) It shoudl check if it's able to write to the config file BEFORE it starts creating the database and throw an error (and not create the DB yet) if it cannot.
While the actual installing functionality works fine, these UI points should be addressed.
Current SVN version of installer has "Help! extra install directions can go here..." in the left column. Also, it asks for a sysadmin password in a password box but needs a second box to confirm the password.
Also, it might be better to hide the completed list of table creation from the user since they don't really give a crap what the tables are named. "## of ## tables installed successfully" is probably enough, perhaps naming any that FAILED to create. This is a more minor point, as it's aesthetic rather than functional, but first appearances count for a lot with software. If we're throwing debug messages and programmer lingo everywhere, will the user think the software is usable by someone of their level of knowledge?
Actually, I've got a picture in my head of how this might work. I may write up a functional spec and run it by you before I try to start coding something.