Original Post
My team has made sufficient headway into our project that faults of our code structure have begun to make themselves apparent. It's very important to us (and to everyone, I'm sure) that we have a clear organization of the classes so people can be up and running quickly. I have been trying to find some information about this but other than Mike McShaffry's "Game Coding Complete" and some occasional tidbits here and there on GameDev and the web I was unsuccessful. Can you suggest some articles or books that would be informative? I am interested in being able to answer questions like "what's the correct way to split a hardware event handler between the player view and the logic layer?" I think I know the answer to that particular one, but I'd like to solidify my knowledge of the subject. We work in Python, but I don't think that should make a difference. Implementing functionality has been and continues to be reasonably easy, but we want the engine to be as maintainable as possible in the long haul. We'd rather invest extra time now than towards the end when it's crunch time (again, an obvious statement). Thanks in advance!
