Create a TransitionController type about transitions-objc HOT 2 CLOSED

🎊 My diff is ready for review at http://codereview.cc/D1259

from transitions-objc.

From the discussion at http://codereview.cc/D1259:

Why'd we need to use associated objects?

Primarily because transitioningDelegate is a weak property. Because of this, somebody needs to hold a strong reference to the instance. There are many answers to "who should own this object?" and we've chosen one that appeared to balance convenience with expressivity.

Background

We want our transitionController to customize both the present and dismiss transitions. Using an associated object is a convenient way to ensure that our controller lives at least as long as the controller whose transitions it is customizing.

Some other ways that we'd considered building this API:

• Having a global transition coordinator singleton that has a lookup table of VC1/VC2 => Director. This has the advantage of allowing transitions to be customized without diving in to view controller code. It has the disadvantage of making the call-site code of present/dismiss less clear as to which director will govern the transition. Note: we can still support this approach even with this associated object API.
• Making the calling view controller store the transitionController instance. This introduces some overhead into every calling controller in that they must now store a transitionController instance any time they want to present a view controller.

from transitions-objc.