Book Image

Swift 2 By Example

By : Giordano Scalzo
Book Image

Swift 2 By Example

By: Giordano Scalzo

Overview of this book

Swift is no longer the unripe language it was when launched by Apple at WWDC14, now it’s a powerful and ready-for-production programming language that has empowered most new released apps. Swift is a user-friendly language with a smooth learning curve; it is safe, robust, and really flexible. Swift 2 is more powerful than ever; it introduces new ways to solve old problems, more robust error handling, and a new programming paradigm that favours composition over inheritance. Swift 2 by Example is a fast-paced, practical guide to help you learn how to develop iOS apps using Swift. Through the development of seven different iOS apps and one server app, you’ll find out how to use either the right feature of the language or the right tool to solve a given problem. We begin by introducing you to the latest features of Swift 2, further kick-starting your app development journey by building a guessing game app, followed by a memory game. It doesn’t end there, with a few more apps in store for you: a to-do list, a beautiful weather app, two games: Flappy Swift and Cube Runner, and finally an ecommerce app to top everything off. By the end of the book, you’ll be able to build well-designed apps, effectively use AutoLayout, develop videogames, and build server apps.
Table of Contents (18 chapters)
Swift 2 By Example
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Free Chapter
1
Welcome to the World of Swift
2
Building a Guess the Number App
Index

Connecting the dataSource and the delegate


You have probably noticed that when we created collectionview, we set View Controller itself as dataSource and delegate:

collectionView.dataSource = self
collectionView.delegate = self

A common pattern found in Cocoa in many components is the delegate pattern, where part of the behavior is delegated to another object, and that object must implement a particular protocol.

In the case of UICollectionView, and likewise for UITableView, we have to delegate one of the class references to provide the content for the view, dataSource, and the other to react to events from the view itself. In this way, the presentation level is completely decoupled from the data and the business logic, which reside in two specialized objects.

So, we need to implement the required methods of the protocols:

// MARK: UICollectionViewDataSource
extension MemoryViewController: UICollectionViewDataSource {
    func collectionView(collectionView: UICollectionView,
        numberOfItemsInSection...