Head First iPhone and iPad Development. A Learner's Guide to Creating Objective-C Applications for the iPhone and iPad. 2nd Edition

Spis treści książki

• Head First iPhone and iPad Development
• Dedication
• A Note Regarding Supplemental Files
• Advance Praise for Head First iPhone and iPad Development
• Praise for other Head First books
• Authors of Head First iPhone and iPad Development
• How to use this Book: Intro
  • Who is this book for?
  • Who should probably back away from this book?
    • We know what youre thinking
    • And we know what your brain is thinking
  • Metacognition: thinking about thinking
    • Heres what WE did
  • Heres what YOU can do to bend your brain into submission
  • Read me
    • System requirements
  • The technical review team
  • Acknowledgments
  • Safari Books Online
• 1. Getting Started: Going Mobile with iOS
  • So, you want to build an iOS app...
  • ...cause everyone wants one!
    • Just look at the app store
  • Apps live in an iTunes universe
  • Time to make a decision
  • It all starts with the iOS SDK
  • Take a look around
  • Xcode includes app templates to help you get started
  • Xcode is a full-featured IDE
  • Xcode is the hub of your iOS project
  • Build your interface within Xcode
  • Add the button to your view
  • The iOS simulator lets you test your app on your Mac
  • iDecides logic
  • Changing the button text
  • Youre using the Model View Controller pattern
  • iDecide is actually a little simpler
    • This pattern is the secret to iOS development
  • What happened?
    • Unless the UI components are hooked up to the code, nothing is going to happen
  • Use the GUI editor to connect UI controls to code
  • A component can trigger certain events
    • Components dispatch events when things happen to them
  • Connect your events to methods
  • Youve built your first iPhone app!
  • Your iOS Toolbox
    • Views are constructed in Interface Builder.
    • Then, you write the code that makes the views work...
    • ...and connect component events to the code.
    • The Simulator runs your app virtually.
• 2. iOS App Patterns: Hello, Renee!
  • First, we need to figure out what Mike (really) wants
  • App design rulesthe iOS HIG
    • Application types
  • HIG guidelines for pickers and buttons
  • Create a new View-based project for InstaEmail
  • The life of a root view
  • We need data
  • Use pickers when you want controlled input
  • Pickers get their data from a datasource...
    • ...and tell their delegates when something happens
  • That pattern is back
    • Controls have their own specific datasources and delegates
    • Protocols tell you what methods (messages) you need to implement
  • First, declare that the controller conforms to both protocols
    • Next, add Mikes activities and feelings to the implementation file
  • The datasource protocol has two required methods
  • Connect the datasource just like actions and outlets
  • Theres just one method for the delegate protocol
  • Actions, outlets, and events
  • Connect the event to the action
  • Add the IBOutlet and property to your view controller
  • Next, synthesize the property...
    • ...and clean up after yourself
  • Connect the picker to our outlet
  • Use your picker reference to pull the selected values
  • Your iOS Toolbox
• 3. Objective-C for iOS: Email needs variety
  • Renee is catching on....
  • Make room for custom input
  • Header files describe the interface to your class
  • Auto-generated accessors also handle memory management
  • To keep your memory straight, you need to remember just two things
  • But when Mikes finished typing...
  • Customize your UITextField
    • Change the label on the return key
  • Components that use the keyboard ask it to appear...
    • ...and you ask for things by passing messages to other objects
  • Ask the UITextField to give up focus
  • Messages in Objective-C use named arguments
  • Use message passing to tell our View Controller when the Done button is pressed
  • Wheres the custom note?
    • Build the email with strings
  • Your Objective-C Toolbox
• 4. Multiple Views: A table with a view
  • So, how do these views fit together?
  • The navigation template pulls multiple views together
  • The table view is built in
  • A table is a collection of cells
    • Each drink gets its own temporary cell
  • Just a few more drinks...
  • Plists are an easy way to save and load data
    • Built-in types can save and load from plists automatically
  • Arrays (and more) have built-in support for plists
  • Use a detail view to drill down into data
  • A closer look at the detail view
  • Use the Navigation Controller to switch between views
  • Navigation Controllers maintain a stack of View Controllers
    • Instantiate a View Controller like any other class
  • Dictionaries store information as key-value pairs
  • Debuggingthe dark side of iOS development
    • Warnings can help find problems first
  • First stop on your debugging adventure: the console
  • Interact with your application while its running
    • And when its about to stop running
  • Xcode supports you after your app breaks, too
  • The Xcode debugger shows you the state of your application
    • What the heck is going on?
  • Your iOS Toolbox
• 5. Plists and Modal Views: Refining your app
  • It all started with Sam...
  • Use the debugger to investigate the crash
    • Were trying to stuff a dictionary into a string
  • Update your code to handle a plist of dictionaries
  • The Detail View needs data
  • The other keys are key
  • We have a usability problem
  • Use a disclosure button to show that there are more details available
  • Sales were going strong
  • Use Navigation Controller buttons to add drinks
  • The button should create a new view
  • We need a view...but not necessarily a new view
  • The View Controller defines the behavior for the view
  • A nib file contains the UI components and connections...
    • ...and information about the nibs Files Owner
  • You can subclass and extend view controllers like any other class
    • Use Xcode to create a View Controller without a nib
  • Modal views focus the user on the task at hand...
    • ...like adding or editing items
  • Any view can present a modal view
  • Our modal view doesnt have a navigation bar
  • Create the Save and Cancel buttons
  • Write the Save and Cancel actions
  • Your iOS Toolbox
• 6. Saving, Editing, and Sorting Data: Everyones an editor...
  • Sam is ready to add a Red-Headed School Girl...
  • ...but the keyboard is in the way
  • Wrap your content in a scroll view
  • The scroll view is the same size as the screen
  • The keyboard changes the visible area
  • iOS notifies you about the keyboard
  • Register with the default notification center for events
    • Then unregister when youre done
  • Keyboard events tell you the keyboard state and size
  • The table view doesnt know its data has changed
    • You need to ask the table view to reload its data
  • The array is out of order, too
    • Sort your array using NSSortDescriptor
  • Table views have built-in support for editing and deleting
  • Your iOS Development Toolbox
    • Sam has another project in mind...
• 7. Migrating to iPad: We need more room
  • DrinkMixer on the iPad
  • The iPad simulator
  • The HIG covers iPads, too
  • Use Xcode to build your Universal app
  • Check your devices
  • Rotation is key with iPad
  • A persistent view problem
  • Dont forget the tableview
    • Present the popover!
  • Your iOS Development Toolbox
• 8. Tab Bars and Core Data: Enterprise apps
  • HF bounty hunting
  • A new iPhone control
  • Choose a template to start iBountyHunter
  • Theres a different structure for universal apps
  • Drawing how iBountyHunter iPhone works...
  • ...and how it fits with the universal app
  • Build the fugitive list view
  • Next up: the Captured view
  • A views contents are actually subviews
  • After a quick meeting with Bob...
  • Core Data lets you focus on your app
    • But wait, theres more!
  • Core Data needs to know what to load
    • We need to define our types
  • Core Data describes entities with a Managed Object Model
  • Build your Fugitive entity
    • Your generated Fugitive class matches the Managed Object Model
    • NSManagedObject handles storage and memory for generated properties
    • NSManagedObject also implements the properties
  • Use an NSFetchRequest to describe your search
    • Ask the Managed Object Context to fetch data using your NSFetchRequest
  • Bobs database is a resource
  • Back to the Core Data stack
  • The template sets things up for a SQLite DB
  • iOS Apps are read-only
  • The iPhones application structure defines where you can read and write
    • Use the Documents directory to store user data
  • Copy the database to the Documents directory
  • Your Core Data Toolbox
• 9. Migrating and Optimizing with Core Data: Things are changing
  • Bob needs documentation
  • Everything stems from our object model
  • The data hasnt been updated
    • Core Data caught a mismatch between our DB and our model
  • Data migration is a common problem
  • Migrate the old data into the new model
    • Our two models need different versions
  • Xcode makes it easy to version your data model
  • Core Data can lightly migrate data
  • Heres what youve done so far...
  • Bob has some design input
  • Your app has a lifecycle all its own...
  • Multitasking rules of engagement
    • The Managed Object Context saves new or changed items
  • A quick demo with Bob
  • Use predicates for filtering data
    • NSFetchRequest concepts are nearly identical to SQL
  • We need to set a predicate on our NSFetchRequest
  • Core Data controller classes provide efficient results handling
    • Table views and NSFetchedResultsControllers are made for each other
  • Time for some high-efficiency streamlining
  • Create the new FetchedResultsController getter method
  • We need to refresh the data
    • NSFetchedResultsController can check for changes
  • Your Data Toolbox
• 10. Camera, Map Kit, and Core Location: Proof in the real world
  • For Bob, payment requires proof
    • Flip over for the detail view
  • The way to the camera...
    • The iPhone isnt the only device using apps
  • Theres a method for checking
  • Prompt the user with action sheets
    • Use action sheets to let the user pick the image source
  • Bob needs the where, in addition to the when
  • Core Location can find you in a few ways
    • Core Location relies on the LocationManager
  • Add a new framework
    • Then update the header file
  • Just latitude and longitude wont work for Bob
  • Map Kit comes with iOS
  • A little custom setup for the map
  • Annotations require a little more work finesse
  • Fully implement the annotation protocol
  • Your Location Toolbox
• 11. iPad UI: Natural interfaces
  • Bob needs that iPad app, too...
    • Natural user interfaces make things more real (and easier)
  • iOS HIG user experience guidelines
    • Its about realism and details
  • Iterate your interface, too
  • BountyHunterHD is based on a Split View Controller
    • Pull it all together
  • Unifying the custom stuff
  • It seems we have a problem...
    • ...you can only change things for the entire field!
  • UIWebview has lots of options
  • HTML, CSS, and Objective-C
  • Using UIWebView
    • Use CSS for the remaining formatting
  • Your NUI Toolbox
• A. Leftovers: The top 4 things (we didnt cover)
  • #1. Internationalization and Localization
    • Localizing nibs
  • Localizing string resources
    • Generating your strings file
  • #2. View animations
    • Animating table view updates
    • Animating view and control changes
  • #3. Accelerometer
    • All you need is the UIAccelerometer
  • Understanding device acceleration
  • #4. A word or two about gaming...
    • Multi-touch
  • Quartz and OpenGL
    • Quartz
    • OpenGL
    • Game Kit
• B. Preparing an App for Distribution: Get ready for the App Store
  • Apple has rules
    • Start at the Apple Developer Portal
    • First, get your Development Certificate
  • The Provisioning Profile pulls it all together
  • Keep track in the Organizer
    • A few final tips...
• Index
• About the Authors
• Copyright

pokaż cały spis treści

ukryj recenzje