Book Image

Mastering macOS Programming.

By : Stuart Grimshaw, Gregory Casamento
Book Image

Mastering macOS Programming.

By: Stuart Grimshaw, Gregory Casamento

Overview of this book

macOS continues to lead the way in desktop operating systems, with its tight integration across the Apple ecosystem of platforms and devices. With this book, you will get an in-depth knowledge of working on macOS, enabling you to unleash the full potential of the latest version using Swift 3 to build applications. This book will help you broaden your horizons by taking your programming skills to next level. The initial chapters will show you all about the environment that surrounds a developer at the start of a project. It introduces you to the new features that Swift 3 and Xcode 8 offers and also covers the common design patterns that you need to know for planning anything more than trivial projects. You will then learn the advanced Swift programming concepts, including memory management, generics, protocol orientated and functional programming and with this knowledge you will be able to tackle the next several chapters that deal with Apple’s own Cocoa frameworks. It also covers AppKit, Foundation, and Core Data in detail which is a part of the Cocoa umbrella framework. The rest of the book will cover the challenges posed by asynchronous programming, error handling, debugging, and many other areas that are an indispensable part of producing software in a professional environment. By the end of this book, you will be well acquainted with Swift, Cocoa, and AppKit, as well as a plethora of other essential tools, and you will be ready to tackle much more complex and advanced software projects.
Table of Contents (28 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
18
LLDB and the Command Line

Import statements


Your .swift files must import frameworks in order to use them, but we don't necessarily need to import the whole of Cocoa.

If you have, for example, a model class that has no need of interacting with any UI elements (and a model class should certainly not be interacting with UI elements), you don't need to import Cocoa, Foundation will suffice:

import Foundation 
class MyFoundationClass: NSObject 
{ 
 var someDate = Date() 
} 

So here, MyFoundationClass is using the NSObject class and the Date class, both of which require Foundation. If you comment out the import statement, you'll get two errors, with the compiler complaining it doesn't know what those two classes are:

This is in contrast to the MySwiftClass we created previously. That class declared only an Int property, which is part of Swift, not Foundation, and also declared no Foundation superclass. So there was no need to import Foundation.

If our class needs to use user interface classes, which are not included in Foundation...