Vending Machinnn

//
//  VendingItemCell.swift
//  VendingMachine
//
//  Created by Pasan Premaratne on 1/19/16.
//  Copyright © 2016 Treehouse. All rights reserved.
//

import UIKit

class VendingItemCell: UICollectionViewCell {

    @IBOutlet weak var iconView: UIImageView!

}


// @IBOutlet is an Outlet
https://developer.apple.com/library/prerelease/tvos/documentation/General/Conceptual/Devpedia-CocoaApp/Outlet.html#//apple_ref/doc/uid/TP40009071-CH4

An outlet is a property that is annotated with the symbol IBOutlet and whose value you can set graphically in a nib file or a storyboard.
@property (nonatomic, weak) IBOutlet UITextField *nameField;


The symbol IBOutlet is used only by Xcode, to determine when a property is an outlet; it has no actual value.




From
https://developer.apple.com/library/prerelease/tvos/featuredarticles/ViewControllerPGforiPhoneOS/DefiningYourSubclass.html

Delete all below to get to get to get to run code.
Handling User Interactions

An app’s responder objects process incoming events and take appropriate actions. Although view controllers are responder objects, they rarely process touch events directly. Instead, view controllers typically handle events in the following ways.

    View controllers define action methods for handling higher-level events. Action methods respond to:

        Specific actions. Controls and some views call an action method to report specific interactions.

        Gesture recognizers. Gesture recognizers call an action method to report the current status of a gesture. Use your view controller to process status changes or respond to the completed gesture.

    View controllers observe notifications sent by the system or other objects. Notifications report changes and are a way for the view controller to update its state.

    View controllers act as a data source or delegate for another object. View controllers are often used to manage the data for tables, and collection views. You can also use them as a delegate for an object such as a CLLocationManager object, which sends updated location values to its delegate.

Responding to events often involves updating the content of views, which requires having references to those views. Your view controller is a good place to define outlets for any views that you need to modify later. Declare your outlets as properties using the syntax shown in Listing 4-1. The custom class in the listing defines two outlets (designated by the IBOutlet keyword) and a single action method (designated by the IBAction return type). The outlets store references to a button and a text field in the storyboard, while the action method responds to taps in the button.
Listing 4-1Defining outlets and actions in a view controller class

Objective-C

    @interface MyViewController : UIViewController
    @property (weak, nonatomic) IBOutlet UIButton *myButton;
    @property (weak, nonatomic) IBOutlet UITextField *myTextField;

    - (IBAction)myButtonAction:(id)sender;

    @end

Swift

    class MyViewController: UIViewController {
        @IBOutlet weak var myButton : UIButton!
        @IBOutlet weak var myTextField : UITextField!

        @IBAction func myButtonAction(sender: id)
    }

In your storyboard, remember to connect your view controller’s outlets and actions to the corresponding views. Connecting outlets and actions in your storyboard file ensures that they are configured when the views are loaded. For information about how to create outlet and action connections in Interface Builder, see Interface Builder Connections Help. For information about how to handle events in your app, see Event Handling Guide for iOS.