More iOS 6 Development: Further Explorations of the iOS SDK

More iOS 6 Development: Further Explorations of the iOS SDK

Jeff LaMarche, Alex Horovitz

Language: English

Pages: 552

ISBN: 1430238070

Format: PDF / Kindle (mobi) / ePub

Interested in iPhone and iPad apps development? Want to learn more? Whether you’re a self-taught iPhone and iPad apps development genius or have just made your way through the pages of Beginning iOS 6 Development, we have the perfect book for you.

More iOS 6 Development: Further Explorations of the iOS SDK digs deeper into Apple’s latest iOS 6 SDK. Bestselling authors Dave Mark, Alex Horovitz, Kevin Kim and Jeff LaMarche explain concepts as only they can―covering topics like Core Data, peer-to-peer networking using GameKit and network streams, working with data from the web, MapKit, in-application e-mail, and more. All the concepts and APIs are clearly presented with code snippets you can customize and use, as you like, in your own apps.

If you are going to write a professional iPhone or iPad app, you’ll want to get your arms around Core Data, and there’s no better place to do so than in the pages of this book. The book continues right where Beginning iOS 6 Development leaves off, with a series of chapters devoted to Core Data, the standard for Apple persistence. Dave, Alex, Kevin and Jeff carefully step through each Core Data concept and show techniques and tips specifically for writing larger apps―offering a breadth of coverage you won't find anywhere else.

The Core Data coverage alone is worth the price of admission. But there's so much more! More iOS 6 Development covers a variety of networking mechanisms, from GameKit’s relatively simple BlueTooth peer-to-peer model, to the addition of Bonjour discovery and network streams, through the complexity of accessing files via the web.

Dave, Alex, Kevin, and Jeff will also take you through coverage of concurrent programming and some advanced techniques for debugging your applications. The enhanced multitasking, threading, memory management and more are important. Apps are getting more and more complex, including sophisticated game apps that offer virtual or augmented reality experiences and new mapping views that take advantage of sensors and other APIs in the newest iOS 6 SDK.

Whether you are a relative newcomer to iPhone and iPad or iOS development or an old hand looking to expand your horizons, there’s something for everyone in More iOS 6 Development.


Foundations of Object-Oriented Languages Types and Semantics

More Than Genes: What Science Can Tell Us About Toxic Chemicals, Development, and the Risk to Our Children

Learn to Program with Scratch: A Visual Introduction to Programming with Games, Art, Science, and Math

Learning Cocoa with Objective-C: Developing for the Mac and iOS App Stores (3rd Edition)

China Experiments: From Local Innovations to National Reform





















nil; if (![context save:&error]) { II Replace this implementation with code to handle the error appropriately. II abort() causes the application to generate a crash log and terminate. You should not use this II function in a shipping application, although it may be useful during development. NSlog(@"Unresolved error %@, %@", error, [error userlnfo]); abortO; } No need to admonish you again about the call to abort, as we discussed this previously. And that's all there is to deleting managed

objects. .f Unde ned Integer 16 Inlege( 32 Integer 64 [}(>c ima Dollb'e no.n SIr "9 Boolean Date Binary dahl Tran~ ortrao e Figure 3-38. The data types supported by Core Data The Integer Data Types Integer 16, Integer 32, and Integer 64 all hold signed integers (whole numbers). The only difference between these three number types is the minimum and maximum size of the values they are capable of storing. In general, you should pick the smallest-size integer that you are certain will work

(one and three, respectively) where each row represents a specific attribute of your managed object. Additionally, each row also has a label, which tells you what value is being displayed. To start, you represent the table as an array, with each item in the array representing a section of the table. Each section, in turn, will be represented by a dictionary. You have a header key in the section dictionary, which stores the string value of the header. Note that the first section of the table does

takes a handle to an NSError as an argument. Notice that when you create the NSError instance, you use the two constants you defined earlier, kHeroValidationDomainand kHeroValidationBirthdateCode: NSError *error = [[NSError alloe] initWithDomain:kHeroValidationDomain eode:kHeroValidationBirthdateCode userlnfo:userlnfoDiet]j Tip Notice that you don't call super in the single-attribute validation methods. It's not that these methods are defined as abstract, it's that they simply don't exist.

the entity. To-Many Relationships To-many relationships allow you to use a relationship to associate multiple managed objects to a particular managed object. This is equivalent to using composition with a collection class such as NSMutableArray or NSMutableSet in Objective-C, as with the children instance variable in the Person class you looked at earlier. In that example, you used an NSMutableArray, which is an editable, ordered collection of objects. That array allows you to add and remove

Download sample