Book Image

Mac Application Development by Example: Beginner's Guide

By : Robert Wiebe
Book Image

Mac Application Development by Example: Beginner's Guide

By: Robert Wiebe

Overview of this book

It's never been more important to have the ability to develop an App for Mac OS X. Whether it's a System Preference, a business app that accesses information in the Cloud, or an application that uses multi-touch or uses a camera, you will have a solid foundation in app development to get the job done.Mac Application Development by Example takes you through all the aspects of using the Xcode development tool to produce complete working apps that cover a broad range of topics. This comprehensive book on developing applications covers everything a beginner needs to know and demonstrates the concepts using examples that take advantage of some of the most interesting hardware and software features available.You will discover the fundamental aspects of OS X development while investigating innovative platform features to create a final product which take advantage of the unique aspects of OS X.Learn how to use Xcode tools to create and share Mac OS X apps. Explore numerous OS X features including iCloud, multi-touch trackpad, and the iSight camera.This book provides you with an illustrated and annotated guide to bring your idea to life using fundamental concepts that work on Mac.
Table of Contents (17 chapters)
Mac Application Development by Example Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

What is code signing?


Code signing is about identifying who created code and resources and that they have not been modified by an unauthorized third party—nothing more and nothing less.

The code signing mechanism wraps executable images and resources, using a cryptographic seal, so that they can be reliably recognized, and any modifications made after the items are sealed can be detected.

Since code is signed, and it could be signed by anybody, the code signing mechanism also needs some way to know who signed the code.

In a nutshell, the code signing mechanism takes our developer identity (which resides in our Keychain), combines it with our final App code bundle, and produces signed code. The important thing about signed code is that it does not change. It is this signed code that we deliver to the end user. We can deliver the signed code to the end user via the Mac App store, via direct download, on a USB dongle, on a CD or DVD. The method of delivery is not important, it is only the fact...