I've made a few games, and am getting faster and better organized each time. I'm well out of the "just make it work" phase and working on methodology and readability. I need some tips on code organization though.
I don't mean patterns - I'm having great success with MVC - but the organization of methods inside the classes themselves. I've noticed that methods in my state models can usually be grouped into four categories: (1)constructor/destructor, (2)data access (3)actions (4)events.
My controllers usually have c/d and input methods. My views usually have c/d, view updaters, and event listeners.
I feel like I'm reinventing the wheel though; someone must have spelled out "these are the common types of methods" somewhere before, right? Storage has Create, Read, Update and Delete (CRUD), so what are the equivalents for objects?
EDIT: Found some cocoa-specific advice here: http://www.mactech.com/articles/mactech/Vol.21/21.07/StyleForCocoa/
and some generic advice here: http://stackoverflow.com/questions/73045/whats-the-best-way-to-organize-code/73081#73081
I'm going to use that as a foundation, modified for game-specific stuff. More info still appreciated if you have any.