Kevin mentions...
"...need to transform the format to fit the view, you would do that in
the controller"
Henrik mentions...
"The data changing should be done in an adapter that the controller puts
in between the model and the view."
So the problems arise because the data that isn't quite what the model
stores, or isn't quite what the views use.
At the same time the controller shouldn't know about requirements of the
model and views, but in this world of isolation and 'not knowing' about
other things we need adapters that do know the details of other parties.
Do all systems need adapters that convert data into the appropriate format?
John
On 26/02/2012 04:13, Karl DeSaulniers wrote:
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 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 need to transform the format to fit the view,
you
would do that in the controller.
Kevin N.
I disagree. The data changing should be done in an adapter that the
controller puts in between the model and the view.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Karl DeSaulniers
Design Drumm
http://designdrumm.com
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
