Question about delegating from ComponentController to ViewController

[facebook]

Question about delegating from ComponentController to ViewController

[adamjernst]

Would it be kosher to include a weak reference to a delegate (i.e. a ViewController) in the context so that the component can set its controller's delegate?

Yes (although I'd prefer having the controller read the component's weak reference and set it on itself, rather than having the component do it).

Are there better ways to route events?

The way we do it at Facebook: we pass down a "navigator" object as part of the context. A simplified version:

@protocol Navigator
- (void)pushViewController:(UIViewController *)vc animated:(BOOL)animated;
@end

Behind the scenes, the actual implementation holds a weak reference to the parent view controller. On demand it looks up the view controller's navigation controller and pushes a view controller, etc.

We find this hides the actual view controller away from the components, making them more reusable.

[cfcommando]

Very enlightening. I had assumed until now that the context was intended mainly as a conduit for data rather than connecting events.

Thanks for the clarity!