Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #3696 > unrolled thread

Model–view–controller pattern

Back to article view | Back to comp.programming

Contents

  Model–view–controller pattern bob <bob@coolfone.net> - 2013-09-06 12:07 -0700
    Re: Model–view–controller pattern "Julio Di Egidio" <julio@diegidio.name> - 2013-09-06 22:34 +0100
      Re: Model–view–controller pattern Rui Maciel <rui.maciel@gmail.com> - 2013-09-08 10:07 +0100
        Re: Model–view–controller pattern "Julio Di Egidio" <julio@diegidio.name> - 2013-09-08 12:56 +0100
    Re: Model–view–controller pattern Geoff <geoff@invalid.invalid> - 2013-09-06 14:57 -0700
      Re: Model–view–controller pattern Geoff <geoff@invalid.invalid> - 2013-09-06 14:59 -0700
        Re: Model–view–controller pattern bob <bob@coolfone.net> - 2013-09-07 13:57 -0700

#3696 — Model–view–controller pattern

I keep getting asked about the Model–view–controller pattern in interviews.  I've looked at the Wikipedia article on it, but I still have to resort to hand-waving when trying to explain it.

Can someone help me understand it better in layman's terms?  For instance what are the benefits of using it?

Thanks.

[toc] | [next] | [standalone]

#3697

"bob" <bob@coolfone.net> wrote in message 
news:0d59988b-c4d1-4be0-a922-d5666f352695@googlegroups.com...
>
> I keep getting asked about the Model–view–controller pattern in 
> interviews.  I've looked at the Wikipedia article on it, but I still have 
> to resort to hand-waving when trying to explain it.
>
> Can someone help me understand it better in layman's terms?  For instance 
> what are the benefits of using it?

Alas, the article on Wikipedia is misguided (as many articles in the area of 
software development).  To begin with, MVC is rather a design pattern. 
Anyway, these are referenced:

<http://www.itu.dk/courses/VOP/E2005/VOP2005E/8_mvc_krasner_and_pope.pdf>
<http://blog.iandavis.com/2008/12/09/what-are-the-benefits-of-mvc/>

From the second link, a quote from GoF, Design Patterns:
<< MVC consists of three kinds of objects. The Model is the application 
object, the View is its screen presentation, and the Controller defines the 
way the user interface reacts to user input. Before MVC, user interface 
designs tended to lump these objects together. MVC decouples them to 
increase flexibility and reuse. >>

And to decrease complexity, as the very first reason for MVC was that of 
breaking circular dependencies.

Julio
 

[toc] | [prev] | [next] | [standalone]

#3706

Julio Di Egidio wrote:

> And to decrease complexity, as the very first reason for MVC was that of
> breaking circular dependencies.

The term "circular dependency"[1] has a precise meaning which isn't related with the MVC 
pattern's purpose.

The main motivation for the MVC pattern is to decouple the data from its presentation, and vice-
versa, in order to simplify the job of implementing and reimplementing ways to represent data 
through a GUI.  Any benefit in breaking any circular dependency which might arise is only a nice 
side-effect of the whole ordeal.


Rui Maciel

[1] https://en.wikipedia.org/wiki/Circular_dependency

[toc] | [prev] | [next] | [standalone]

#3707

"Rui Maciel" <rui.maciel@gmail.com> wrote in message 
news:l0henv$53c$1@dont-email.me...
> Julio Di Egidio wrote:
>
>> And to decrease complexity, as the very first reason for MVC was that of
>> breaking circular dependencies.
>
> The term "circular dependency"[1] has a precise meaning which isn't 
> related with the MVC
> pattern's purpose.
>
> The main motivation for the MVC pattern is to decouple the data from its 
> presentation, and vice-
> versa, in order to simplify the job of implementing and reimplementing 
> ways to represent data
> through a GUI.  Any benefit in breaking any circular dependency which 
> might arise is only a nice
> side-effect of the whole ordeal.

You don't know what you are talking about.

Julio
 

[toc] | [prev] | [next] | [standalone]

#3698 — Re: Model–view–controller pattern

On Fri, 6 Sep 2013 12:07:07 -0700 (PDT), bob <bob@coolfone.net> wrote:

>I keep getting asked about the Model–view–controller pattern in interviews.  I've looked at the Wikipedia article on it, but I still have to resort to hand-waving when trying to explain it.
>
>Can someone help me understand it better in layman's terms?  For instance what are the benefits of using it?
>
>Thanks.

http://www.youtube.com/watch?v=_CBpdhGPOUQ

[toc] | [prev] | [next] | [standalone]

#3699 — Re: Model–view–controller pattern

On Fri, 06 Sep 2013 14:57:38 -0700, Geoff <geoff@invalid.invalid>
wrote:

>On Fri, 6 Sep 2013 12:07:07 -0700 (PDT), bob <bob@coolfone.net> wrote:
>
>>I keep getting asked about the Model–view–controller pattern in interviews.  I've looked at the Wikipedia article on it, but I still have to resort to hand-waving when trying to explain it.
>>
>>Can someone help me understand it better in layman's terms?  For instance what are the benefits of using it?
>>
>>Thanks.
>
>http://www.youtube.com/watch?v=_CBpdhGPOUQ

Skip to about 18 minutes into the video.

[toc] | [prev] | [next] | [standalone]

#3702

On Friday, September 6, 2013 4:59:02 PM UTC-5, Geoff wrote:
> On Fri, 06 Sep 2013 14:57:38 -0700, Geoff <geoff@invalid.invalid>
> 
> wrote:
> 
> 
> 
> >On Fri, 6 Sep 2013 12:07:07 -0700 (PDT), bob <bob@coolfone.net> wrote:
> 
> >
> 
> >>I keep getting asked about the Model–view–controller pattern in interviews.  I've looked at the Wikipedia article on it, but I still have to resort to hand-waving when trying to explain it.
> 
> >>
> 
> >>Can someone help me understand it better in layman's terms?  For instance what are the benefits of using it?
> 
> >>
> 
> >>Thanks.
> 
> >
> 
> >http://www.youtube.com/watch?v=_CBpdhGPOUQ
> 
> 
> 
> Skip to about 18 minutes into the video.

I like that video.  Thanks.

The MVC controller pattern is a little more complicated than I anticipated though.  Does anyone know of a really good concrete example of this that I could study?

Thanks.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.programming

csiph-web