Architectural considerations / MVC – How to improve FightVnC

[ymyke]

• MVC: Could I have the basic FightVnC, which takes a Controller object, that does the
  playcard stuff etc. and an Animator object that makes all the animations available
  that are necessary?
  • QQ: How many of the controller-related functions in FightVnC are actually
    subclassed? How much subclassing is necessary there?
  • How many methods could really be moved to the Animator class? I.e., how many methods
    use information from the model?
  • Is the differentiation between methods that have r/o access to the model and ones
    that have r/w access?

[ymyke]

From a comment:

# QQ: What use cases for `vnc` are there in this class? And how could those be untangled
# further? (E.g., information access (round number), pure view calls, controller calls,
# things that should be controller calls(deck updates)?, ...?)