This bug will be used to track the development of the new version of JoLauncher.
At this point, JoLauncher works, but I have no idea how stable it is under
pressure, because of my idiodic use of static variables, and because the
launcher itself relies on the contents of the JTable itself instead of using a
central data structure to hold everything.
I'm going to need to determine how best to structure the new version of
JoLauncher, and I still need to figure a few things out. Experience and advice
from other, more experienced java programmers would be very much appriciated as
Due to two developments...
1. Talk of a built in launcher to Odamex
2. Russell's building of a Windows native C++ launcher
I do not think that JoLauncher's existance is necissary. This may change later,but if I start on a launcher at all, it won't use Java. However, it's probably for the best, so I can keep up with the development of the Odamex CTF map pack.