Comments on: Understanding the MVC pattern http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern Extreme Software Engineering Wed, 08 Sep 2010 06:45:34 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: mosh http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-141 mosh Tue, 25 Aug 2009 09:54:43 +0000 http://www.heavyworks.net/?p=67#comment-141 hi, good article, its my 5 today about MVC :) its little hard do understood logic.. but im starting cristalize the problem :) hi, good article, its my 5 today about MVC :)
its little hard do understood logic.. but im starting cristalize the problem :)

]]> By: Gabriel Svennerberg http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-39 Gabriel Svennerberg Thu, 08 Jan 2009 14:43:48 +0000 http://www.heavyworks.net/?p=67#comment-39 That sounds interesting. Please send it to me. That sounds interesting. Please send it to me.

]]> By: Jan Seidl http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-36 Jan Seidl Wed, 07 Jan 2009 18:45:48 +0000 http://www.heavyworks.net/?p=67#comment-36 I think CakePHP's learning curve is quite simple but I had few contact with it. Some friends already done some works with it and I've seen several issues generated by its structure making you a little hand-tied. I've started writing my own based on several practices (lots from Rails) because I wanted to run Smarty for View layer and PHP Doctrine as model. I can send you to take a look if you want. Its totally unobstrusive, MVC, DBAL/ORM and has some neat features (and others still under implementation). I think CakePHP’s learning curve is quite simple but I had few contact with it. Some friends already done some works with it and I’ve seen several issues generated by its structure making you a little hand-tied. I’ve started writing my own based on several practices (lots from Rails) because I wanted to run Smarty for View layer and PHP Doctrine as model. I can send you to take a look if you want. Its totally unobstrusive, MVC, DBAL/ORM and has some neat features (and others still under implementation).

]]> By: Gabriel Svennerberg http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-35 Gabriel Svennerberg Wed, 07 Jan 2009 09:26:44 +0000 http://www.heavyworks.net/?p=67#comment-35 I'm using the <a href="http://www.asp.net/mvc/">ASP.NET MVC Framework</a> for a project I'm currently working on and that what's finally made me really like ASP.NET. I think the MVC pattern really makes a lot of sense once you get into it. I've tried <a href="http://codeigniter.com/">CodeIgniter</a>, a MVC framework for PHP, but I didn't really got over the initial threshold so I abandoned it. I have thought about having a go at CakePHP instead. What would you say about it's learning curve? Does it take a lot of effort to get into it? I’m using the ASP.NET MVC Framework for a project I’m currently working on and that what’s finally made me really like ASP.NET. I think the MVC pattern really makes a lot of sense once you get into it.

I’ve tried CodeIgniter, a MVC framework for PHP, but I didn’t really got over the initial threshold so I abandoned it. I have thought about having a go at CakePHP instead. What would you say about it’s learning curve? Does it take a lot of effort to get into it?

]]> By: Paul W. Homer http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-18 Paul W. Homer Mon, 22 Dec 2008 21:31:42 +0000 http://www.heavyworks.net/?p=67#comment-18 I've always thought of the C in MVC as just being a keyboard/mouse 'interface' to the user; a very thin controller. The strength of MVC was touted as a way to contain multiple synchronized yet different views of the same underlying model (which is why MVC2 in a place like struts seems so bizarre). The controller was just a 'behavioral' tie. But I really like your perspective: the model is the pure data for the app, the view is the presentation layer and the controller is the human in-between that directing the behavior. I'd have to agree with one of the earlier comments that said the business logic should be in the model, however the ability to drive it belongs to the user (controller). So a fat controller would contain all of the application context, preferences, etc. allowing the model (and the view) to be completely stateless (but contain all of the possible functionality of interest). As a paradigm that makes more sense to me than a thin controller (I always end up separating state anyways, just not in the controller). Paul. I’ve always thought of the C in MVC as just being a keyboard/mouse ‘interface’ to the user; a very thin controller. The strength of MVC was touted as a way to contain multiple synchronized yet different views of the same underlying model (which is why MVC2 in a place like struts seems so bizarre). The controller was just a ‘behavioral’ tie.

But I really like your perspective: the model is the pure data for the app, the view is the presentation layer and the controller is the human in-between that directing the behavior. I’d have to agree with one of the earlier comments that said the business logic should be in the model, however the ability to drive it belongs to the user (controller). So a fat controller would contain all of the application context, preferences, etc. allowing the model (and the view) to be completely stateless (but contain all of the possible functionality of interest). As a paradigm that makes more sense to me than a thin controller (I always end up separating state anyways, just not in the controller).

Paul.

]]> By: Peteris Krumins http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-17 Peteris Krumins Mon, 22 Dec 2008 15:22:19 +0000 http://www.heavyworks.net/?p=67#comment-17 The <a href="http://www.catonmat.net/blog/musical-geek-friday-model-view-controller-song/">Model View Controller Song</a> will also help you understand MVC! ;) The Model View Controller Song will also help you understand MVC! ;)

]]> By: Jan Seidl http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-16 Jan Seidl Sun, 21 Dec 2008 20:42:34 +0000 http://www.heavyworks.net/?p=67#comment-16 Hi Adam! I'm glad you've enjoyed the article! The credits for the illustration are: Tool: Adobe Photoshop CS2 Icons: http://www.iconspedia.com Font: Lucida Sans Concept: Myself \o/ Have a nice day too! Jan. Hi Adam!

I’m glad you’ve enjoyed the article!

The credits for the illustration are:
Tool: Adobe Photoshop CS2
Icons: http://www.iconspedia.com
Font: Lucida Sans
Concept: Myself \o/

Have a nice day too!
Jan.

]]> By: adam http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-15 adam Sun, 21 Dec 2008 20:33:52 +0000 http://www.heavyworks.net/?p=67#comment-15 oups I meant MVC paradigm not MVC framework ;-) oups I meant MVC paradigm not MVC framework ;-)

]]> By: adam http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-14 adam Sun, 21 Dec 2008 20:33:16 +0000 http://www.heavyworks.net/?p=67#comment-14 Hi Alavaro! It is a good introduction to the MVC framework ... I will certainly refer my students to your blob post. One question, what tool have you used to design the illustration image? Have a nice day. Adam Hi Alavaro!

It is a good introduction to the MVC framework … I will certainly refer my students to your blob post.

One question, what tool have you used to design the illustration image?

Have a nice day.

Adam

]]> By: Jan Seidl http://www.heavyworks.net/blog/posts/understanding-the-mvc-pattern/comment-page-1#comment-13 Jan Seidl Sun, 21 Dec 2008 19:04:41 +0000 http://www.heavyworks.net/?p=67#comment-13 Thanks Alavaro! I've always questioned where the business logic should reside. The Skinny Model, Fat Controllers seems a great answer for that. It really makes more sense and puts the Controller definitely under his paper. Thanks for the tip, I've updated the article with the "correct" procedure. Thanks Alavaro! I’ve always questioned where the business logic should reside. The Skinny Model, Fat Controllers seems a great answer for that. It really makes more sense and puts the Controller definitely under his paper. Thanks for the tip, I’ve updated the article with the “correct” procedure.

]]>