Re: model->controller messaging
Re: model->controller messaging
- Subject: Re: model->controller messaging
- From: Mike Shields <email@hidden>
- Date: Wed, 4 Jun 2003 23:24:28 -0600
Notifications. Uncouple the model from any controller. This way you can
hook up more than one controller (say for two different views of your
data) that will detect when something changes.
Mike
On Wednesday, June 4, 2003, at 10:37 PM, Sean Harding wrote:
What's the accepted best practice for communicating from a model
object to a controller object? Controller to model is easy because the
controller creates the model. Is there any reason not to pass the
model a pointer to the controller and let it freely send messages > back?
sean
--
Sean Harding -- email@hidden -- http://dogcow.org/s/ -- KD7UAY
Seattle, WA, USA
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.