I've been a Java Developer for several years and about a year ago moved onto Android development. After tackling Android, I then attempted to test my luck with iOS. So far so good, but I'm still very hazy on the ideas of "Delegates." I've read several articles on here and still don't have the best idea on them. To me, they seem similar to Inheritance in Java, such as using an interface or an abstract class.
Can anyone clarify in a view that I may understand?
Thanks in Advance.
No, that's not the same concept of inheritance.
I would say that it's like the listener approach used in AWT/Swing. Eg:
class MyActionListener implements ActionListener {
public void actionPerformed(ActionEvent e) { ... }
}
myComponent.addActionListener(new MyActionListener);
This with a delegate approach in ObjC would look like:
@class MyActionListener : NSObject<NSActionListener>
-(void) actionPerformed:(NSEvent*)event;
@end
myComponent.delegate = [[[MyActionListener alloc] init] autorelease];
In practice you delegate some of the behavior of a class to a specific other object used by composition (and NOT by inheritance) so that the delegate methods will be called when needed (either for callback, either to provide specific implementations and whatever)
When using an object, you can inherit some callback methods from its class. Basically, you can respond when that object has an event.
The object class is "delegating" that event to your class instance.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With