The controller is the Grand Central station for the application. It handles requests from the user and takes care of routing data between the views and the model. Most variations of MVC change the role (and sometimes the name) of the controller, but the important thing is that it acts as the intermediary between the view and the model. Our controller object will need to hold references to the views and models used by our application and be responsible for managing interactions between them.
Examples of code you find in the controller include the following:
- Startup and shutdown logic for the application
- Callbacks for user interface events
- Creation of model and view instances
Our Application object is currently acting ...
