Register your product to gain access to bonus material or receive a coupon.
Swift for Beginners: Develop and Design, 2nd Edition
- By Boisy G. Pitre
- Published Nov 30, 2015 by Peachpit Press.
eBook
- Your Price: $30.39
- List Price: $37.99
- Includes EPUB and PDF
- About eBook Formats
This eBook includes the following formats, accessible from your Account page after purchase:
EPUB
The open industry format known for its reflowable content and usability on supported mobile devices.
PDF
The popular standard, used most often with the free Acrobat® Reader® software.
This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.
Description
- Copyright 2016
- Dimensions: 7-3/8" x 9-1/8"
- Pages: 336
- Edition: 2nd
- eBook
- ISBN-10: 0-13-428980-3
- ISBN-13: 978-0-13-428980-9
LEARNING A NEW PROGRAMMING LANGUAGE can be daunting. With Swift, Apple has lowered the barrier of entry for developing iOS and OS X apps by giving developers an innovative programming language for Cocoa and Cocoa Touch. Now in its second edition, Swift for Beginners has been updated to accommodate the evolving features of this rapidly adopted language.
If you are new to Swift, this book is for you. If you have never used C, C++, or Objective-C, this book is definitely for you. With this handson guide, you’ll quickly be writing Swift code, using Playgrounds to instantly see the results of your work. Author Boisy G. Pitre gives you a solid grounding in key Swift language concepts—including variables, constants, types, arrays, and dictionaries—before he shows you how to use Swift’s innovative Xcode integrated development environment to create apps for iOS and OS X.
THIS BOOK INCLUDES:
- Detailed instruction, ample illustrations, and clear examples
- Best practices from an experienced Mac and iOS developer
- Emphasis on how to use Xcode, Playgrounds, and the REPL
COMPANION WEBSITE:
www.peachpit.com/swiftbeginners2 includes additional resources.
Updates
Errata
pg. 18, first paragraph:
The variable referred to as 'myConvertedInt' should be 'w'.
pg. 51:
The shorthand notation ( [:] ) for declaring a dictionary is not shown. The note box at the bottom of the page makes reference to the short form declaration of a dictionary. Such short form is never shown in the chapter. e.g var myDictionary = [String : String]()
pg. 76, bottom of page:
The ";" following the while keyword in the repeat-while is not necessary.
pg. 134:
Possible issue - last paragraph before "Using the Right Combination" - "You've followed the code and you understand how the methods inside your new superclass override the same named methods above." The word "superclass" should be "subclass."
pg. 189:
Figure 7.27 shows 6.25 entered as the interest rate percentage.
pg.199:
Figures 8.8 and 8.9 show 6 entered as the interest rate percentage. Using a NSNumberFormatter from Interface Builder does not allow for decimal positions for the percentage style. 6.25 truncates to just 6. Using decimal positions with NSNumberFormatter percentage style must be done in code.
pg. 233, top of page:
case.Green should be case .Green, case.Blue should be case .Blue, case.Yellow should be case .Yellow .
pg. 237:
The code comments "// view-related objects and variables" and "// model-related objects and variables", are shown here with a hyphen, but in the original code they did not have the hyphen.
pg. 238:
Section title "Overridable methods" should be "Overriding Methods".
pg. 238, bottom of page:
case.Red should be case .Red, case.Green should be case .Green .
pg. 242:
UIAlertView appears to be deprecated in iOS 9.0+. To address the warning, you can set the project deployment target in the Xcode project to iOS 8.4.
pg. 243:
There is a discrepancy with the method signature; on p.234 it is func alertView(alertView: UIAlertView, clickedButtonAtIndex buttonIndex: Int) {}, but on p.243 it is func alertView(alertView: UIAlertView, clickedButtonAtIndex: Int) {}.
pg. 265:
The symbol between the two 2x2 matrices being multiplied at the top of the page should be an * (asterisk), not a + (plus sign).