Archive for Hydrocon

Hydrocon Session Log, 1242780616

Posted in smalltalk with tags , , on May 20, 2009 by moffdub

Development of the Hydrocon is slow but steady. Though still in its prototype form, the Hydrocon will, in one dramatic move, forever end all shortages–er wrong window, sorry.

Quick blogging note, my friends: Nowhere To Run may or may not happen due to Memorial Day weekend.

I pensively started refactoring the BuildingTest class. I started by finding out what messages the FakeRoom has to respond to, and I tried to make it as simple as possible so as to not include very much logic.

One thing I stopped to think about is that FakeRoom needs a class method newInstanceWithName:aName andID:anID. The real Room takes a RoomName and RoomID for these objects. Should I fake these out too for FakeRoom?

Continue reading

Hydrocon Session Log, 1242262213

Posted in smalltalk with tags , , on May 13, 2009 by moffdub

Development of the Hydrocon is slow but steady. Though still in its prototype form, the Hydrocon will, in one dramatic move, forever end all shortages–er wrong window, sorry.

The problem with Smalltalk’s lack of constructors is coming home to roost as I began writing the BuildingAddress object. This object has six attributes and each has a hasBeenSet analog so that I can restrict their (private) setters from changing attribute values multiple times. It’s fine, I’ll use a Dictionary. This is also the first time I will be using “constants” in Smalltalk, which will essentially be class methods in ALL CAPS:

Continue reading

Hydrocon Session Log, 1241655767

Posted in smalltalk with tags , , on May 6, 2009 by moffdub

Development of the Hydrocon is slow but steady. Though still in its prototype form, the Hydrocon will, in one dramatic move, forever end all shortages–er wrong window, sorry.

I updated the = and hash methods of Room to only look at the RoomID. Room is an Entity and should be treated as such. If I need to do an attribute-based comparison, I will write a separate method for that.

As I was writing some tests, I realized I needed a method on Building to access the Set of Rooms. That test revealed an unimplemented method on Room, unavailableForNewInventory. I added it and added an accessor on Room to find out if the Room is accepting new inventory. I added a hash method for RoomName since I implemented = as well. It’s interesting how = doesn’t require a : after it when specifying the argument. I wonder if that can be done for other method names besides =.

Continue reading

Follow

Get every new post delivered to your Inbox.