Wednesday, 18 January 2012

Oh shit...

Okay, so, the thing that made me cut down to 2 posts a week? Kind of a (way) bigger deal than I thought. I'm going to have to go on hiatus for a....while. But at least if you're subscribed, you'll know exactly when I'm back?

I'm sorry, but I barely get 5 free minutes to myself every day, let alone the 30-60 I need to work on the code then post it.

Thursday, 12 January 2012

Java: Texas Hold Em - Debugging (3)

Okay, so, super super busy of late, going to have to significantly cut down my post-output to like, 2 a week on Tue/Thu. Just a heads up. So this'll be the last post this week.

Here, I'll give you a link to the files needed, and you can run the file for yourself!

Wednesday, 11 January 2012

No Post

Sorry, cannot complete a post for today. See you tomorrow.

Tuesday, 10 January 2012

Java: Texas Hold Em - Debugging (2)

Woo, change to the titling, because I kept losing track of what number we were on, and I can't count past 40 anyway. Okay, so we looked at the folding, and that seems to work. We should still see if we can stop the New Hand message appearing twice, so let's do that, then tomorrow we can move on to testing another action.

Monday, 9 January 2012

Java: Texas Hold Em (36) - Debugging the client

Okay, folks, going to keep it short. Today, I'll show you some screens of how the client works inside the IDE and point out some stuff that might need fixing. This'll not only give you the opportunity to thing about how it's going on, but what I might have missed so you can suggest a fix of your own!

Here we go:

Friday, 6 January 2012

Java: Texas Hold Em (35)

Almost there, folks! Today we get to the point where the functionality only needs to be debugged, and thus is pretty much done! So next week is debugging, and if we have time, depending on how riddled with errors the code is, get to the GUI.

Let's stop talking about getting to tat point now, and actually get there!

Thursday, 5 January 2012

Java: Texas Hold Em (34)

Ah, for those unaware, debugging is the process of finding/identifying errors (bugs) and removing them from some program. Doing this is mostly uninteresting, and in the case of the ConsoleClient, just involves me running the entire class and seeing what it does, then trying to find out why it does that.

I was going to document the debugging, but only after we were done with the class, since errors crop up in the form of methods we've not covered, and it'd get confusing :)

For now, though, lets get to finishing the ConsoleClient. Looking at the Client interface, there's 7 or so more methods to go! Here we go:

Wednesday, 4 January 2012

Java: Texas Hold Em (33) - The Console Client

Hullo again! I meant to make this post in advance to get up here so I could have today off, but then I didn't, so I'm stuck here :(

Today we start on our ConsoleClient, which should be the final piece to our functionality. Maybe, I honestly don't quite get either of the clients, so there will probably be a load of debugging to do. Probably some which I won't be able to do. But that's enough optimism, let's get down to the client!

Tuesday, 3 January 2012

Java: The Map Interface

Hi again! I'll be going through the Map interface today in a little more detail, just so you know how it works. It's pretty cool. If you've done other programming, you might know this interface as a dictionary, which is what I likened it to before.

Monday, 2 January 2012

Java: Texas Hold Em (32)

Hullo! Finishing off the table class today so tomorrow we can go through a tutorial of the Map class. After that, we'll be messing with the ConsoleClient to complete our functionality, then put aside a few days to test it all out so we can be confident that we're set to move onto the GUI and so on and so forth!