Can somebody show me a View class that doesn't update itself?  What does it do? 
Are all of its properties public?

Conversely, can someone show me a controller class that does the work of both 
modifying the model and manipulating the view? Does it lead to a ton of code in 
one class?

I'm not suggesting my version of MVC is the only correct one, and while I'm not 
a fan of controller-centric mvc (like cocoa) i understand there are successful 
implementations (like iOS) That said, I have never been shown an MVC 
implementation in which anything is allowed to alter the model other than the 
controller, it's my current understanding that that's the only fundamental 
requirement of MVC no matter what flavor.

Further, I can attest to the fact that my approach has a real advantage in 
keeping display, state, and business logic highly discrete and evenly 
distributed code wise.

It is very easy to locate any code in one of my projects by ascertaining the 
domain of the code in question and looking in the appropriate branch.
Does it store data? It's in the model.
Does it interpret and display data? Try your views.
Does it manipulate data? Look in the controller.

Easy as MVC.

This separation of interests is what appeals to me about the pattern, and I've 
had great success not only creating apps with my particular approach, but I've 
also been able to pick them back after any amount of time and track down the 
code behind any feature very quickly.

If anyone doesn't mind detailing the benefits of another approach as I did 
mine, I'd love to disrupt these dogmatic feelings I'm having.

I don't need to be told I'm wrong, because clearly I'm not. I don't need more 
opinions about what 'correct' MVC looks like because my system works extremely 
well.  Im asking for concrete examples of different takes on MVC and what makes 
them advantageous. There has to be something left to learn on the matter..

I'll let you know when I get my framework up on the hub.

Ross P. Sclafani
Owner / Creative Director
Neuromantic Industries

On Feb 17, 2012, at 5:18 PM, Kevin Newman <> wrote:

> Hands down the best explanation of MVC I've ever seen anywhere, is in this 
> iTunes U series (item 43 at the bottom of the list) - you can just grab the 
> slides too, but you'll miss all the emotion and humor of the delivery :-)
> There seems to be some basic pieces that are commonly missing from most 
> descriptions of MVC:
> - Models have model data, broadcast changes to listening controllers, are 
> updated directly by the controller.
> - Views have view data, data that is specific to the view, are updated 
> directly by the controller, broadcast changes to listening controllers.
> - Models shouldn't communicate with Views (ever).
> - Views shouldn't communicate with Models (ever).
> A lot of examples of MVC I've seen take a shortcut and basically send the 
> model data to a view which renders that data, but that isn't MVC at all.
> Kevin N.
> On 2/16/12 1:43 PM, wrote:
>> Models and Views don't talk to each other.
> _______________________________________________
> Flashcoders mailing list

Flashcoders mailing list

Reply via email to