Unit 01 of 03
View Controllers
The view controller as a per-screen responsibility, lifecycle methods across the loading, appearing and disappearing stages, stack-based navigation controllers, modal and push presentation styles, a comparison of building interfaces with a visual editor and in code, and the outlets and actions that link the interface to code.
Published Updated
Lessons
- 01 The View Controller Concept How a view controller carries a screen between the model and the view, and an introduction to the measurement that classifies whether a screen agrees with the model as matching, stale, missing or leftover. 12 min read
- 02 Lifecycle Methods Measuring which lifecycle method a value is written in, whether that leaves the screen matching the model or stale, and what moving the write does. 13 min read
- 03 Navigation Controllers Measuring that when a screen is pushed and popped in a navigation controller, a selection removed from the model stays on the list as leftover, and that the pushed screen matches the model. 13 min read
- 04 Presentation Styles Measuring that a value entered on a note screen presented modally over another screen is written to the model but never reaches the screen beneath, and stays missing there. 12 min read
- 05 The Visual Editor and Code-Built Interfaces Measuring that a label with a broken outlet stays stale with its placeholder text on a screen drawn in the visual editor, that a code-built label matches, and that the placeholder text the editor saves stays as leftover. 14 min read
- 06 Outlets and Actions Measuring that an action that only updates the model and forgets the label leaves the screen stale, and that formatted text compared with the raw value counts as stale. 13 min read