Messages, Notifications or Protocols?
Messages, Notifications or Protocols?
- Subject: Messages, Notifications or Protocols?
- From: "Jordan Evans" <email@hidden>
- Date: Thu, 12 Oct 2006 21:51:21 -0700
I'm working on a class that manages that amount of images and/or text
that will display in a view. I.e, when the controller class sends a
scroll message, it handles the image/text/other data that is
repositioned, allocated or deallocated, and displayed. I'm looking
for ideas on how to best create a generic type connection, since I
intend to reuse this class for other implementations which will
certainly have different data types and sizes, as well as multiple
sources that will be chosen to be displayed in a view.
I have a draft of the memory managment part written, but I'm still
brainstorming the best way to make the class communicate between the
controller and view class.
What is the best what to create the connections, so it can be re-used
in the future easily: messages, notifications, protocols, ?
Any suggestions appreciated.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden