Comments on: Simple Explanation of Model View Controller (MVC) http://jordanhall.co.uk/programming/simple-explanation-of-model-view-controller-mvc-2206990/ Jordan Hall - programmer and geek Sun, 22 Jan 2012 17:46:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jeff http://jordanhall.co.uk/programming/simple-explanation-of-model-view-controller-mvc-2206990/comment-page-1/#comment-39141 Jeff Mon, 17 Oct 2011 21:47:01 +0000 http://jordanhall.co.uk/?p=990#comment-39141 According to your (and pretty much all explanations out there) diagram is wrong, or explanation of MVC is wrong - one or the other - they are not compatible. According to your explanation MVC works more like tower, not triangle: View (on top) gets input and transfers to Controller which gets model Model to e.g adjust DB, then upon response from model (fail/success), it transforms and applies input received from View (and model status) to adjust View Thats not triangle! So either your (and most) explanations are wrong, or diagram is wrong. It's like with E=MC2. Everyone knows what it is all about, but when it comes to explaining it, no one knows how. According to your (and pretty much all explanations out there) diagram is wrong, or explanation of MVC is wrong – one or the other – they are not compatible.

According to your explanation MVC works more like tower, not triangle: View (on top) gets input and transfers to Controller which gets model Model to e.g adjust DB, then upon response from model (fail/success), it transforms and applies input received from View (and model status) to adjust View

Thats not triangle!

So either your (and most) explanations are wrong, or diagram is wrong.

It’s like with E=MC2.
Everyone knows what it is all about, but when it comes to explaining it, no one knows how.

]]> By: Alexander http://jordanhall.co.uk/programming/simple-explanation-of-model-view-controller-mvc-2206990/comment-page-1/#comment-4081 Alexander Fri, 04 Jun 2010 12:41:44 +0000 http://jordanhall.co.uk/?p=990#comment-4081 In more complex applications, the models are used in a different way. It's too hard to manage the complexity when one model class has a lot of responsibilities. That is why a lot of mvc applications use the model as dumb data transfer object, without any behavior. The viewmodel contains the data to view. The domain model in a different part of the application contains the business logic. In more complex applications, the models are used in a different way. It’s too hard to manage the complexity when one model class has a lot of responsibilities. That is why a lot of mvc applications use the model as dumb data transfer object, without any behavior. The viewmodel contains the data to view. The domain model in a different part of the application contains the business logic.

]]>