I have really appreciated this thread too.
The basic ideas of MVC seem straight forward enough, but the problems
arise in implementing it.
Disagreements about the roles inside MVC can really help us understand
it. So if anyone has a specific example in which they struggled to
determine the
On 24/02/2012 15:15, Merrill, Jason wrote:
Maybe I'm off, but I don't think the controller should manipulate data.
Who is then?
Jason Merrill
Instructional Technology Architect II
Bank of America Global Learning
___
-Original Message-
From:
On 2/25/2012 8:00 PM, Paul Andrews wrote:
Who is then?
The model - but it depends on what you really mean by manipulate - if
you are storing it (such as in a database) to be retrieved by the model
at a later time, the model should do it. If you are channeling the data
to a generic view, and
Kevin Newman skriver:
On 2/25/2012 8:00 PM, Paul Andrews wrote:
Who is then?
The model - but it depends on what you really mean by manipulate - if
you are storing it (such as in a database) to be retrieved by the model
at a later time, the model should do it. If you are channeling the data
Why the extra step? Shouldn't the controller be that adaptor that is
already between the model and the view?
It's a MVC not a MVAC?? :)
Karl
On Feb 25, 2012, at 7:44 PM, Henrik Andersson wrote:
Kevin Newman skriver:
On 2/25/2012 8:00 PM, Paul Andrews wrote:
Who is then?
The model - but
Different frameworks have different tweaks to the conventions. It's usually
best to have a specific framework in mind when working on this.
Eg. We do things differently in RubyonRails to RobotLegs. I've worked with
Django in the past as well. It has hard blockers to keep logic getting into
the
6 matches
Mail list logo
