Tired and underpaid.

So it's late, and 3/4 of the group are at Mitch's house. We are nearing completion of the game, but still have work to do, so we decided to meet at Mitch's house and work on it together. Sitting near me (Jared) are Mitch and Nate. Ben is to be getting here in about 8.5 hours. ((Oh, Ben just called and apparently he will actually be here in about half an hour)).

I have made a list of what we still must complete, and the list is somewhat long-ish. It's not overly long, however, and although a number of the tasks are somewhat time-consuming, none of them are really all that difficult. So after that list, I feel somewhat reassured. Crunch-time is slightly less crunchy. Like an Oreo in milk.

Also, the computer I am using is HORRIBLE. Yes, it is even worse than my own. The video card can reach nothing better than 640x480 resolution, and the colour quality can not best 16 bit. The mouse is completely screwed, and if I move it, it goes wonky all over the screen and starts selecting things. So I use the keyboard. In JCreator, I cannot actually type, so I must type things into Notepad and then copy them. The ONLY reason I am willing to use this machine is because I need to code and it is the only thing available. :/

Anyway, we stil have work to do. But we are nearing our goal, and taking a break. We are all very tired at this point in time, and decided that we can get no productive work done and will therefore rest for some time, then get back to work when our minds are refreshed. And thus shall end.

*falls asleep*
~Genome

I are teh l33t.

Data transmission works. Checked over two computers, tomorrow I shall try three in the beginning of the class.

w00t.

Success! And problematic findings. :(

Socketman here. With my Thread of Truth I shall conquer evil. (I really hope that somebody realizes that blatant Wonder Woman reference.)

Anyway, here's the update in the world of networking: As I said earlier, I believe, I have read and understood everything concerning multi-threaded "servering" and all was well. Now, I have completed the Server program (rather, the classes that will receive and interpret information from networked computers) and it works like unambiguity incarnate. Unfortunately, I had to include Swing to make it work. So in lieu of this, after testing is complete, I will simply include the component that requires Swing in Nate's section, as it is essentially just the part that calls my sockets and threads into existence. So it is easily transferable.

Tonight I plan on working steadily on the Client program (or, the classes that are intended to send information over the network to Server applications on receiving terminals) and hopefully I shall complete it tonight. After that, all that I must do is clean it up, determine which pieces of data must be sent through the network, and then finally determine how to specifically connect the computers.

The problem inherent in connecting the computers is a simple one, but with a seemingly difficult solution. Originally, my main problem was how to connect -all- the computers in every way. For instance, each computer must be connected to every other computer in order to transmit its data. I almost decided to have the information travel in a ring-like sequence, with each system connecting to only one, which in turn connected to another, etc. This would allow all information to be shoved around. However, it is terribly inefficient as the first computer's variables will take longer than necessary to get to the last computer. So I have now decided to have 4 Clients per terminal connecting to the Server running on each other computer. This is a much easier and quicker approach to my original problem.

However! My new issue arises out of this decision. For the way that sockets interact is using the Computer Name defined in network properties. Therefore, either the Client that is currently being run must KNOW the Computer Name of the Server it's connecting to, or the end-user must so that they can type it in. If need be, I can simply do that, and have a function to read the name so that each user can read it to the others to type in, but that is both horribly inefficient and somewhat dangerous if this game is ever to be introduced to those who are not so adept in the workings of computers. For this reason I must exert much contemplation on how to do this... Although I don't know of any other way.

We shall see what will come of this. I will speak with the others about it. Farewell for now.

*a string of a sticky web-like substance shoots down and pulls him away*
~Genome

The Many Faces of Pak_man

On friday I completed the 16 models of pak_man sized, colourized and ready for use. I have the normal pak_man's 8 different models; up, down, left and right for open and closed mouth positions. Also we decided to make, instead of the ghosts changing, pak_man changes when he eats the pill. So all 8 models for the "on the pill pak_man" are done as well. So the next task which I attempted on friday is to find a high-res format and low size (which shouldn't be a problem on a 22x22 object) to export it as. I have yet to find a file type that keeps the resolution but my quest continues.
~fruitsnacks

Swing

Swing is evil.

I am still attempting to learn it. EVIL. I have learned that I need to make a JPanel before using image icons, and I'm currently examining some swing code I found on-line to try to go back through it and see what makes it tick. I've been looking on-line and in the Java books in the classroom.

But I despise Swing already.

Until next time,
Wombat? What wombat?
~Kataron

Following a Different Thread

So I have spent much time poring over the code that I acquired from that good friend of mine, and I understood it. The problem was that it was source with a purpose. It interacted with numerous other classes, ones which I did not have. That wasn't such a big deal, but it made it more difficult to understand the basics of sockets.

So I started from scratch (while still remembering what I understood) and found a tutorial on Sun's website. I have just been going through it, and am understanding wonderfully. The best part, I find, is that I have been analysing and compiling example code and I have now learned how to interact over a network with sockets perfectly fine. The thing is, I have only learned sockets. Not threads. So I can only interact between two computers at a time.

Not to worry, however. I have already begun learning multi-threaded sockets, and I do not believe it will be very much more difficult than single-threaded. Expect another new post from me very soon. In the mean-time...

*distracts you as he escapes behind a RETURN statement*
~Genome

The network is getting there...

So I've worked on the network code a bit. Not much, yet... I am still working on understanding completely. I've also been trying to think of a port to run this on, at least for testing. Right now my mind is set upon 510, but that is not yet final. I recall adding the IP of my computer in the classroom (10.5.16.175) into the ConnectionManager, and I will add Ben's (10.5.16.144) into the playerConnection, to test connecting into the game from Ben's. I have yet to do this testing, for the classes are not ready... But I am setting it up. Anyway, I believe I can readily send information through the network... All I need to do is complete the actual connecting part, and then figure out how to run Threads so that lots of data can be sent and received simultaneously. Oh, the excitement.