Marius Gedminas wrote:
I never fully understood the "controller" part of it;
Me neither. I *think* in the original Smalltalk terminology, the view handled output and the controller handled input. But I find that input and output are usually so closely coupled that it's not worth having two separate objects, so I just talk about a View and a Model. In Cocoa, they seem to use the word "controller" to refer to an intermediate object that sits between the model and a collection of user interface objects and coordinates them. In my code, I usually use a subclass of Window for this, so again it's not a separate object. -- Greg
