Argh. Why did someone at MS find it necessary to bury config files like
that? C:\Documents and Settings\username.VASSAL would have been much
nicer.
You know, we could include a link in VASSAL’s folder in the start menu
which opens the errorLog in notepad—that would solve the problem of
people not being able to find it.
Because we encounter so many people who (1) don’t understand how to
use zip files, (2) need help but have no idea where they’ve installed
VASSAL, (3) expect apps to come with an installer, (4) want something
which will automatically clean up previous installs, (5) want
shortcuts on their destop, but don’t want to or don’t know how to make
them themselves, and (6) etc.
We’re not going to stop distributing the zip archive—it’s needed for
cases where a user can’t or doesn’t want to use an installer, and it’s
also the only install method right now for non-MacOS-X unices. I’m
glad the zip archive works well for you—the existence of a Windows
installer in addition to the zip archive shouldn’t affect you at all.
They’ll need access to the actual file I think Joel, most won’t want to look at the contents when it throws an error. As long as they can find the file easily and upload it to the forum or attach to an e-mail they should be happy. It would be nice if we eventually gave them the errorLog path when an exception is thrown. It may also be an idea to start calling errorLog errorLog.txt instead, spam filters may go haywire if they come across an attachment with unknown content. It also means they could attach it to messages here in the forum.
I’m happy with the decision to go with the “Advanced” install option by the way.
The introduction of a manual distribution has had an unexpected but very positive effect on testing; It’s so easy to unzip Joel’s builds then run and test.
I’d be the first one crying without the zipped distribution!