Re: CallBack method design
Re: CallBack method design
- Subject: Re: CallBack method design
- From: "Erik M. Buck" <email@hidden>
- Date: Fri, 3 May 2002 11:51:12 -0500
Consider delegates, notifications, and/or standard target/action. Also look
at how data sources work with table views etc.
----- Original Message -----
From: "Normand Perron" <email@hidden>
To: "Cocoa Dev" <email@hidden>
Sent: Friday, May 03, 2002 11:34 AM
Subject: CallBack method design
>
I am developing what will eventually become a custom framework. I need
>
to implement a system of callbacks. What would be the easiest or
>
preferred way of doing this?
>
>
I can think of a couple ways of doing this:
>
>
having a - (void)setContentHandler:(id)handlerObject
>
method:(SEL)handlerSEL method and then having the framework send the
>
appropriate message.
>
>
forcing the user to subclass my framework's contentHandler method,
>
which would be an empty shell in the framework itself.
>
>
I assume that both ways would relatively painless to implement in the
>
framework. What are the considerations which would favour one above the
>
other?
>
>
Normand
>
_______________________________________________
>
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.