Well, the idea that the controller sits between th...
Anonymous · 2010-12-05T16:55:50.240000
Well, the idea that the controller sits between the view and the model is a Java/Ruby thing, not an MVC thing.
(In the original design, the view pulls data from the model and renders it, while the controller interprets user events and updates the view and model accordingly. So for a readonly view, Django's view is an MVC view, using the template renderer and the browser as the presentation layer.)
As far as I recall, the developers understood MVC ...
Unknown · 2010-12-07T11:49:59.106000
As far as I recall, the developers understood MVC perfectly, but just intentionally didn't apply it. It was only after years of kicking and screaming that they more or less accepted the MVC analogy.
Well, the idea that the controller sits between th...
Anonymous · 2010-12-05T16:55:50.240000
Well, the idea that the controller sits between the view and the model is a Java/Ruby thing, not an MVC thing.(In the original design, the view pulls data from the model and renders it, while the controller interprets user events and updates the view and model accordingly. So for a readonly view, Django's view is an MVC view, using the template renderer and the browser as the presentation layer.)
As far as I recall, the developers understood MVC ...
Unknown · 2010-12-07T11:49:59.106000
As far as I recall, the developers understood MVC perfectly, but just intentionally didn't apply it. It was only after years of kicking and screaming that they more or less accepted the MVC analogy.Page 1 of 1
Back to post