Comments on: Intermediate Rails: Understanding Models, Views and Controllers http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/ Learning shouldn't hurt. Let's share the insights that made difficult ideas click. Sun, 14 Mar 2010 04:08:56 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Kalid http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-272630 Kalid Wed, 17 Feb 2010 02:01:40 +0000 http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-272630 @Andrew: Awesome, really glad it helped! Exactly, so many articles make gigantic assumptions about what you already know, it can be hard to see it from the beginning. I'm thrilled this was able to help :). @Andrew: Awesome, really glad it helped! Exactly, so many articles make gigantic assumptions about what you already know, it can be hard to see it from the beginning. I’m thrilled this was able to help :) .

]]> By: Andrew http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-272461 Andrew Fri, 12 Feb 2010 05:50:24 +0000 http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-272461 Thank you so very very much for this article. I've been beating my head against a wall for the last three months trying to find info that reads more clearly than gibberease (meaning that it's supposed to be educational...as long as you've been doing web design since the beginning and are completely familiar...no, intimate with all the principles that lead to RoR) and this is one certain gem amongst the rubble. I've only gotten thru ~1/4 of the doc so far, but I can understand the way you think. Here I'm trying to learn the Rails way, but I also have daily work I have to get done to keep our fledgling site running and resolving outstanding issues the original dev left undone...I just wish I had found this months ago. Almost as much as I wish I had gotten a ream of paper for my printer today while I was out so I could print a copy right now... ;) so, thank you thank you thank you. This is going to help so much! Thank you so very very much for this article. I’ve been beating my head against a wall for the last three months trying to find info that reads more clearly than gibberease (meaning that it’s supposed to be educational…as long as you’ve been doing web design since the beginning and are completely familiar…no, intimate with all the principles that lead to RoR) and this is one certain gem amongst the rubble. I’ve only gotten thru ~1/4 of the doc so far, but I can understand the way you think.

Here I’m trying to learn the Rails way, but I also have daily work I have to get done to keep our fledgling site running and resolving outstanding issues the original dev left undone…I just wish I had found this months ago. Almost as much as I wish I had gotten a ream of paper for my printer today while I was out so I could print a copy right now… ;) so, thank you thank you thank you. This is going to help so much!

]]> By: Zyx http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-271921 Zyx Fri, 29 Jan 2010 17:32:26 +0000 http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/#comment-271921 A small clarification: actually the guys designing Rails made a mistake. The design pattern in the diagram is not MVC, but MVP (Model-View-Presenter), a derivative of MVC. In real MVC, views are supposed to communicate directly with models, and the controller only selects what model and what view to use. This does not happen neither in RoR nor in 99% of web frameworks that cloned the same mistake. And most of all, templates != views; database != models. They should lie under them. A small clarification: actually the guys designing Rails made a mistake. The design pattern in the diagram is not MVC, but MVP (Model-View-Presenter), a derivative of MVC. In real MVC, views are supposed to communicate directly with models, and the controller only selects what model and what view to use. This does not happen neither in RoR nor in 99% of web frameworks that cloned the same mistake. And most of all, templates != views; database != models. They should lie under them.

]]>