Have you gotten anywhere with this?   This would not be how I would do
it.  You need to think of the view and the controller as a cohesive
unit.  I think it makes sense to create a separate controller class
for each view in the system.  Then, after you see your system come
together a bit more, you can create a class hierarchy of controllers
if you find yourself implementing the same behavior in more than one
controller class.  (Keep in mind that Data in the system is stored in
State, not by the controllers themselves.   The controller should be
thought of as "behavior" not "data".)

For example, suppose I'm going to create a system with 2 views (View_A
and View_B).  I would initially create a separate controller, one for
each view (Controller_A and Controller_B).   In the course of
implementing the system, if you discover that there is some common
behavior that you need to share between Controller_A and Controller_B,
then create a common base class that both Controller_A and
Controller_B would inherit from.

If, in fact, you find that your design requires the same view to run
with more than one controller, then I would create an interface that
defines what the common behavior is between all the controllers that
the view will work with.   In the view, I would then type-case the
Controller into the common interface, and all should be well.

Just a thought.

--steve