7DRL3 - Day 2 and 3

Day 2 was pretty uneventful. More thinking and planning than actual coding. In fact, I felt pretty bad about lack of progress after day 2. Interestingly enough, we didn't really get to coding until after some beer. I think maybe being too wired (coffee) can have a negative impact on productivity if you're still in the decision making phase. For example, I spent probably 4 hours reading, reading, and reading about different ways to do what we're doing, and what is more "standard". Wondering if we should use std::string instead of char[]. Exploring every alternative for the message system. Whether C++0x would make anything we're doing easier. Good reading, but time that could have been spent actually TRYING some of these methods. There is merit to careful planning, but at some point you get diminishing returns and you need to just jump in. Apparently beer does the trick ;)

I'm sorta bummed about our message system that different parts of the engine use to communicate. I hoped to minimize the amount of memory allocating/deallocating/copying we have to do manually, but the idea fell short and we're back to the same old memcpy fun. If I have time (haha) I'll revisit the message system and attempt to make it less hideous.

Day 3 was a lot better. We have most of the 'major' decisions made and a good framework to deal with. We ALMOST have a basic battle up. Hopefully tomorrow we get a battle going and can have some screenshots to post :)