I was wondering if anyone objects to the following change of behavior to the Main.Launch() method.
If a module file has been specified as an argument to VASSAL.launch.Main then it bypasses the startup Wizard entirely. I’m going by the assumption that if a user is savvy enough to pass the module name as an argument to Vassal, then he/she probably wants to bypass the launch Wizard.
The only code change is near line 163 of Main.java:
The only essential function the Welcome Wizard performs is making sure the user has entered a username and password. If you just remove it as you’ve suggested, you’ll get people playing with null passwords, which ends up causing ownership confusion.
While I like the Game Setup Wizard, I have to admit I’m not so crazy about the Welcome Wizard. I’m thinking of only keeping it around for the username/password prompt. Or maybe just getting rid of it and moving the username/password prompt to the Game Setup wizard.
Ah OK, so what ideally needs to happen is Welcome Wizard only gets invoked when a user loads a module for which they do not yet have a username and password?
Here’s the current state of things w/r/t making the Welcome Wizard
toggleable and integrating everything from the initial console window
into the main app window:
Is this compiled to be compatible with Java 5? I get UnsupportedClassVersionError when launching with JDK 1.5.
Also, is the entry point VASSAL.launch.Launcher or VASSAL.launch.Main? The scripts use Launcher, but I thought you went back to Main after you figured out the different mechanism for setting the heap size.
This is compiled for Java 6, because this branch it comes from isn’t
up-to-date with my general working branch or the trunk.
Same reason. The scripts in this build aren’t current. It’s fine if you
launch this with VASSAL.launch.Main as the entry point—it just won’t
pick up your heap settings.