UIView와 UIViewController

Welcome to building iOS interfaces! Every visual element you see in an iOS app, from buttons to entire screens, is built using two core components: UIView and UIViewController.

These are the fundamental building blocks that allow you to display content and manage user interactions in your Objective-C applications.

A UIView is the basic rectangular region that draws content and handles events on the screen. Think of it as a canvas where you can draw shapes, display text, or show images.

• It's the base class for all visual elements.
• It defines the content's position, size, and appearance.
• It can contain other views, creating a view hierarchy.

UIViews have important properties that control their appearance and layout. Here are a few common ones:

• frame: Defines the view's size and position relative to its superview.
• bounds: Defines the view's size and position relative to its own coordinate system.
• backgroundColor: Sets the view's background color.
• alpha: Controls the view's transparency (0.0 is fully transparent, 1.0 is fully opaque).

You can create and configure a UIView programmatically. Here's how you might set up a simple red square view:

A UIViewController is a crucial component that manages a hierarchy of views (often just one main view) and coordinates the flow of information between the views and your app's data model.

It acts as the brain for a specific screen or section of your app, handling user input, updating the view, and responding to system events.

Every UIViewController has a primary view property, which is an instance of UIView. This view acts as the root of the view hierarchy that the view controller manages.

You typically add all other UI elements (like buttons, labels, etc.) as subviews to this main view.

UIViewControllers have a lifecycle with methods that are called at different stages. One of the most important is viewDidLoad.

• It's called once after the controller's view has been loaded into memory.
• This is the perfect place to perform initial setup for your views, like adding subviews, setting up constraints, or loading initial data.
• It's called only once during the lifetime of the view controller.

Here's how you might override viewDidLoad in your custom view controller to add some initial UI setup:

Besides viewDidLoad, two other common lifecycle methods relate to a view appearing on screen:

• viewWillAppear:: Called just before the view controller's view is added to the view hierarchy and about to be displayed. Good for updating UI that might change frequently.
• viewDidAppear:: Called after the view controller's view has been fully presented on screen. Good for starting animations or fetching data that requires the view to be visible.

Which of the following statements best describes the primary responsibility of a UIViewController?

You've learned about the fundamental building blocks of iOS user interfaces!

• UIView is the basic rectangular area for drawing and event handling.
• UIViewController manages a view hierarchy and coordinates the interaction between views and data.
• The view property of a UIViewController is the root of its managed UI.
• Lifecycle methods like viewDidLoad, viewWillAppear, and viewDidAppear are key for setting up and updating your UI at different stages.

Next, we'll explore common UI controls and how to handle user events!