Re: Where in the MVC should my code go?
Re: Where in the MVC should my code go?
- Subject: Re: Where in the MVC should my code go?
- From: Matthew Lindfield Seager <email@hidden>
- Date: Sun, 28 Feb 2010 18:23:33 +1100
On Sunday, February 28, 2010, Jean-Henri Duteau <email@hidden> wrote:
> I don't have a good reason to not put it into the view other than pragmatic. I can give the controller a bunch of attributes and bind the view's controls to those attributes, as opposed to programatically creating the strings in the view.
For small applications or simple situations it is not uncommon to
combine two roles into the one object (e.g. combining controller &
view functions or controller & model functions into one object).
That being said, small projects sometimes become larger ones so it may
be worth splitting roles earlier rather than later.
> Advice?
Read Cocoa Design Patterns by Buck & Yacktman... It's excellent
reading (& not just for its treatment of MVC).
Matt
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden