As I start to create custom cells by deriving from *Element* I need to be careful I don't start messing up the clean MVC separation works in iOS.
Is this a true and fair way to think of things: - A derived [*Element*] should contain behavioral methods that are responsible "only" for on screen manipulation of the visuals of the Element's parts. It is conceptually the "View" of MVC. - A "model" per se should never be directly passed into a derived [* Element*], rather - The relationship between a model, and the way the Element displays is (via it's behavioral method mentioned above) should ALWAYS be managed through a *UIViewController* (or *DialogViewController* as the case may be). That seems clear, and logical to me at the moment. Is it this clear cut and simple - or do you guys start to blur things (passing models into Elements)...and if so, is that OK/recommended? It's tempting to just ram some controller-like "model binding" behavior into the derived element. Is that evil? Thanks! -- *Phil *Cockfield
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
