iOS开发权威指南：iPhone SDK应用开发

需积分: 10 145 浏览量更新于2024-07-27 收藏 6.87MB PDF 举报

"13[iPhone开发书籍大全].iPhone.SDK.Application.Development(Reilly.2009-1)" 这本书，《iPhone SDK Application Development》是 Jonathan Zdziarski 的作品，由 O'Reilly Media, Inc. 在2009年出版。本书主要针对想要学习和掌握iPhone应用开发的读者，是iOS开发领域的一本基础学习资料。书中详细介绍了如何使用iPhone SDK进行应用程序开发，涵盖了从入门到进阶的各种主题。iPhone SDK（Software Development Kit）是苹果公司为开发者提供的工具集，它包含了一套完整的开发环境，用于创建可以在iPhone、iPad以及iPod touch上运行的应用程序。在内容方面，读者可以期待学习到以下知识点： 1. **Objective-C编程基础**：Objective-C是开发iOS应用的主要语言，书中可能详细讲解了语言的基本语法、类、对象、消息传递等概念。 2. **Cocoa Touch框架**：Cocoa Touch是iOS开发的核心部分，包括UI设计、事件处理、动画等，书中应该会详细介绍如何利用它来构建用户界面。 3. **Xcode集成开发环境**：作为iOS开发的标准工具，Xcode的使用方法，包括项目管理、代码编辑、调试等，都会被涵盖。 4. **iOS应用生命周期**：从应用启动到退出的整个过程，包括视图控制器、内存管理、后台模式等。 5. **网络编程**：如何在iOS应用中实现网络通信，如HTTP请求、JSON解析等。 6. **多媒体支持**：如何处理音频、视频、图像等多媒体资源，以及利用Core Animation进行高级图形操作。 7. **地理位置服务**：利用GPS和其他传感器获取用户位置，并进行地图集成和导航功能的开发。 8. **推送通知**：如何集成Apple Push Notification Service，为用户提供实时信息更新。 9. **测试与发布**：应用的测试策略、App Store提交流程、App审核规则等。 10. **性能优化**：提高应用效率，包括内存优化、CPU使用率控制、动画流畅度提升等。此外，书中的示例代码和实战练习将帮助读者更好地理解和应用所学知识。对于刚开始接触iOS开发或者希望深化技能的开发者来说，这本书提供了一个全面的学习路径。同时，O'Reilly Media 的出版品质保证了内容的专业性和实用性，读者可以从中获得有价值的指导和经验分享。

Download at WoweBook.Com

Foreword

As a longtime participant in the iPhone hacking community, I have often been asked

just what I think about the iPhone SDK. I’ll take a moment to reward those of you who

have purchased this book with an answer. In short, Apple’s iPhone SDK adds some

very nice high-level functionality to clean up an otherwise hideous mess. Deep under-

neath the SDK’s comfy pillows rests a very disorganized and poorly designed set of

frameworks, but some of that ugly was also very functional in areas where the SDK is

not. The SDK is certainly good enough to write a high-quality, functional application

for the AppStore (if it weren’t, I wouldn’t be writing about it). The interfaces provided

by the SDK are written well enough for most good developers to design good software,

but most people are unaware of the functionality that isn’t available to them. For those

who cut their teeth in the open source world, the iPhone SDK is still a point of

contention.

If you’re unfamiliar with the politics surrounding the SDK, there are two sets of devel-

oper interfaces: those provided by the SDK, and those that Apple uses. While there is

some overlap between the two, I wrote about many classes and frameworks you’ve

never heard of in my book iPhone Open Application Development (O’Reilly). You’ve

never heard of them because they are not available in the SDK. Many of us in the early

iPhone hacking community discovered them by breaking into the iPhone’s operating

system directly. Throughout many weeks of dumping symbol tables, classes, and ex-

perimenting by trial and error, we mapped out the genome for the iPhone’s user inter-

face kit as well as many other frameworks, including many that are now private. It is

these low-level APIs that developers use when building iPhone software with the open

source tool chain, and the same low-level APIs that we found many of Apple’s appli-

cations taking advantage of to do things the SDK didn’t quite allow for.

These low-level APIs are what give open tool chain developers an edge over SDK de-

velopers, and in my opinion, offer a better development framework than Apple’s SDK.

Many of the frameworks on the device have been quietly privatized, making their func-

tionality unavailable to AppStore developers. Not coincidentally, much of this

functionality appears to be what is crucial for building applications that Apple might

consider to be competitive with their own preloaded software. Of these, the greatest

offenses include restricting the Core Surface framework, which would have given SDK

developers the ability to render raw pixels directly to a screen layer and incorporate the

Download at WoweBook.Com

use of graphics accelerators. Without this framework available, you’ll have a difficult

time squeezing performance out of applications that require 2D rendering, such as

custom movie players, video recorders, or high performance 2D games like my free

Nintendo emulator. This is also a key framework needed in order to write applications

such as Flash or Java™ with any degree of performance. Another set of APIs you’ll find

missing is the ability to interface with iTunes music. This is why the SDK version of

Nate True’s Tap Tap Revolution no longer picks songs from your iTunes library, and

why you’ll only find cool music applications like SynchStep (which plays music to the

rhythm of your steps) in a third-party repository. Even simple functionality, such as

the ability to run in the background or display status bar icons, exists only when using

APIs that are restricted from the AppStore. Needless to say, the open source iPhone

compiler lets you do many things that the SDK cannot, which some would speculate

is designed to ensure Apple will forever have the competitive edge in the iPhone soft-

ware market.

On the other side of things, the SDK offers something that open source was never much

good at accruing: large wads of cash. Developers seem to be able to swallow their

distaste for Apple’s policies after considering the obscene amount of money there is to

be had from an audience as large as that of iTunes. The AppStore financially rewards

innovators who are willing to drink the Kool-Aid. The potential for revenue provided

by the AppStore gives developers a significant advantage over the open development

community, even if your application does turn out slightly crippled.

From a solely technical perspective, the open source compiler can build applications

using either the SDK interfaces or the low-level “private” interfaces, depending on

which set of headers you care to use. The same is true of Xcode: the private, undocu-

mented interfaces can be easily imported into your project by simply pointing the SDK

at the right headers. This gives you four possible combinations for developing

applications.

What it really comes down to is this: if you are looking to deploy applications in the

AppStore, you must play by Apple’s rules. Apple will not accept an application that

uses private interfaces or frameworks. Apple has reportedly even rejected flashlight

applications that overstepped their bounds and had the nerve to try to adjust the dis-

play’s brightness on their own. If you’re a commercial developer or designing software

to deploy on your enterprise, there really is only one viable path for you, and that’s to

use the sanctioned APIs documented in this book. If, however, you’re reading this book

as an open source enthusiast, and consider your code to be more of an art form, you

may be more interested in writing software as it was intended to be written—without

shackles and sandboxes. In this case, I recommend you consider using not only the

APIs you’ll find in this book, but to further expand your knowledge into the many

undocumented APIs and frameworks available. The open source community was the

first to build a public compiler and over-the-air, online community software repository

for the iPhone, and it welcomes beautiful, full-featured applications.

xvi | Foreword

Download at WoweBook.Com

剩余393页未读，继续阅读

曾宪华

粉丝: 9
资源: 4

iOS开发权威指南：iPhone SDK应用开发

2009年iPhone游戏开发指南：O'Reilly《iPhone Game Development》

2009版O'Reilly《iPhone SDK应用开发指南》：打造顶尖移动应用

全面指南：2009年O'Reilly版iPhone应用开发宝典

iPhone SDK Application Development, 1st Edition

iPhone Open Application Development

iPhone Game Development

iPhone.rar_iPhone/iOS_Objective-C_

iPhone Game Development (epub 格式)

最权威的iphone开发资料

Head First iPhone and iPad Development, 3rd Edition

最新资源