Heh, don't thank me yet. I've been waiting for this kind of game for a long time, too, and I'd been alternately wanting and trying to do it off and on for the past five years. And once it's working, it's almost guaranteed to be unsatisfying to everyone (including me) in many ways. But ah well. This appears to be the most flexible and modular yet simple design yet, so there's hope.
Status
The pre-alpha test release is getting closer. The list stands thus:
1. build the tactical control
The controller is in place, but I still have to translate mouse actions into ship actions in a reasonable way. Using keyboard events would probably be easier, if I can get JPanels to listen for key events.
2. build the login window
Done and working.
3. deploy with JNLP
I learned how to do that yesterday. I'll probably have to tinker more with it to get it working over the internet with Apache.
Design
For those interested, I'm using a Model-View-Controller pattern to manage complexity. The Model talks to the server -- currently just a database connection -- and spawns Views. The Views, in turn, each spawn one Controller. Movement is almost guaranteed to be horribly jumpy, so I'll have to compensate by not trying to do "smooth" spaceflight, but something rather more like 1-second-interval positional updating. We'll see. The database hit is bound to be the bottleneck. Of course, that can be largely fixed by creating a server-side listener that caches positional data and broadcasts it by UDP. But there's no way I'm going to introduce yet another layer of complexity at this point.
Status
The pre-alpha test release is getting closer. The list stands thus:
1. build the tactical control
The controller is in place, but I still have to translate mouse actions into ship actions in a reasonable way. Using keyboard events would probably be easier, if I can get JPanels to listen for key events.
2. build the login window
Done and working.
3. deploy with JNLP
I learned how to do that yesterday. I'll probably have to tinker more with it to get it working over the internet with Apache.
Design
For those interested, I'm using a Model-View-Controller pattern to manage complexity. The Model talks to the server -- currently just a database connection -- and spawns Views. The Views, in turn, each spawn one Controller. Movement is almost guaranteed to be horribly jumpy, so I'll have to compensate by not trying to do "smooth" spaceflight, but something rather more like 1-second-interval positional updating. We'll see. The database hit is bound to be the bottleneck. Of course, that can be largely fixed by creating a server-side listener that caches positional data and broadcasts it by UDP. But there's no way I'm going to introduce yet another layer of complexity at this point.