Graphics Programs Reference
In-Depth Information
7
View Controllers
In the
Quiz
application, you wrote all of your code in a
QuizViewController
class.
An instance of this class was the controller for the
Quiz
application: It had pointers to the
labels on the screen, and the buttons sent messages to it when they were tapped. It also had
pointers to model objects that made up the data of the application.
The
Quiz
application had only one screen, so it was sufficient to have only one controller
object for that application. However, most applications have more than one screen. Having
one controller and many screens is messy because the controller has too many objects to
manage. When designing iOS applications, it is best to have a controller for every screen.
