Pro.Android 4 PDF英版：从入门到高级开发指南

5星 · 超过95%的资源需积分: 10 116 浏览量更新于2024-07-27 收藏 30.8MB PDF 举报

"《Pro.Android.4.pdf》是一本全面深入讲解Android开发的英文版专业书籍，旨在帮助读者理解和掌握Android平台的关键技术。本书结构严谨，内容涵盖了从入门到高级的主题，为开发者提供了丰富的学习资源。首先，第一章"Introducing the Android Computing Platform"介绍了Android的核心理念和架构，让读者对整个平台有一个总体的认识。接着，第二章至第十六章分别围绕开发环境设置、资源管理、内容提供者（Content Providers）、意图（Intents）与用户界面设计、菜单功能、Fragment的使用、对话框操作、Action Bar的探索、高级调试和分析、配置变化处理、偏好设置与状态保存、安全与权限管理、服务构建与消费以及包管理、Handler机制等核心主题进行详细讲解。在每个章节中，作者深入浅出地阐述了关键技术，例如如何创建和使用Content Providers来实现数据共享，如何设计用户友好的界面和交互，以及如何通过Action Bar提升应用的用户体验。此外，还涉及了调试技巧和性能优化，确保开发者能够有效地解决实际开发中的问题。对于开发平板应用和响应屏幕尺寸变化的特殊需求，第八章专门讨论了Fragment技术的应用。在处理用户输入和隐私保护方面，第十四章深入探讨了Android的安全机制和权限管理，这对于构建符合Google Play Store要求的应用至关重要。最后，第十五章至第十七章着重于服务的构建与管理，以及通信机制如Handler的使用，这些内容有助于开发者构建更复杂、功能强大的应用程序。《Pro.Android.4.pdf》是一本不可多得的Android开发指南，适合所有层次的开发者，无论是初学者还是经验丰富的开发者，都能从中找到所需的深入知识和实用技巧。通过阅读和实践书中的内容，读者将能提升自己的Android编程能力，更好地应对现代移动应用开发的挑战。"

CHAPTER 1: Introducing the Android Computing Platform

loaded as XML files and because resource IDs for those menus are auto-generated.

Here’s how you would declare menus in an XML file:

<item android:id="@+id/menu_clear"

android:orderInCategory="10"

android:title="clear" />

<item android:id="@+id/menu_show_browser"

android:orderInCategory="5"

android:title="show browser" />

</group>

</menu>

Android supports dialogs, and all dialogs in Android are asynchronous. These

asynchronous dialogs present a special challenge to developers accustomed to the

synchronous modal dialogs in some windowing frameworks. We’ll address menus in

Chapter 7 and dialogs in Chapter 9.

Android offers extensive support for animation. There are three fundamental ways to

accomplish animation. You can do frame-by-frame animation. Or you can provide

tweening animation by changing view transformation matrices (position, scale, rotation,

and alpha). Or you can also do tweening animation by changing properties of objects.

The property-based animation is introduced in 3.0 and is the most flexible and

recommended way to accomplish animation. All of these animations are covered in

Chapter 21.

Moreover, Android allows you to define these animations in an XML resource file. Check

out this example, in which a series of numbered images is played in frame-by-frame

animation:

<animation-list xmlns:android="http://schemas.android.com/apk/res/android"

android:oneshot="false">

……

</animation-list>

Android also supports 3D graphics through its implementation of the OpenGL ES 1.0

and 2.0 standards. OpenGL ES, like OpenGL, is a C-based flat API. The Android SDK,

because it’s a Java-based programming API, needs to use Java binding to access the

OpenGL ES. Java ME has already defined this binding through Java Specification

Request (JSR) 239 for OpenGL ES, and Android uses the same Java binding for

OpenGL ES in its implementation. If you are not familiar with OpenGL programming, the

learning curve is steep. Due to space limitations, we are not able to include the OpenGL

coverage in the fourth edition of the book. However we have over 100 pages of

coverage in our third edition.

Android has a number of new concepts that revolve around information at your fingertips

using the home screen. The first of these is live folders. Using live folders, you can

publish a collection of items as a folder on the homepage. The contents of this collection

change as the underlying data changes. This changing data could be either on the

CHAPTER 1: Introducing the Android Computing Platform

device or from the Internet. Due to space limitations, we are not able to cover live folders

in the fourth edition of the book. However, the third edition includes extensive coverage.

The second homepage-based idea is the home screen widget. Home screen widgets are

used to paint information on the homepage using a UI widget. This information can

change at regular intervals. An example could be the number of e-mail messages in your

e-mail store. We describe home screen widgets in Chapter 25. The home screen

widgets are enhanced in 3.0 to include list views that can get updated when their

underlying data changes. These enhancements are covered in Chapter 26.

Integrated Android Search is the third homepage-based idea. Using integrated search,

you can search for content both on the device and also across the Internet. Android

search goes beyond search and allows you to fire off commands through the search

control. Due to space limitations, we can’t include coverage of the search API in the

fourth edition of the book. However, it is covered in the third edition.

Android also supports touchscreen and gestures based on finger movements on the

device. Android allows you to record any random motion on the screen as a named

gesture. This gesture can then be used by applications to indicate specific actions. We

cover touchscreens and gestures in Chapter 27.

Sensors are now becoming a significant part of the mobile experience. We cover

sensors in Chapter 29.

Another necessary innovation required for a mobile device is the dynamic nature of its

configurations. For instance, it is very easy to change the viewing mode of a handheld

between portrait and landscape. Or you may dock your handheld to become a laptop.

Android 3.0 has introduced a concept called fragments to deal with these variations

effectively. Chapter 8 is dedicated to fragments, and Chapter 12 talks about how to deal

with configuration changes.

We also cover the 3.0 feature (which is much enhanced in 4.0) of action bars in Chapter 10.

Action bars bring Android up to par with a desktop menu bar paradigm.

Drag-and-drop is introduced for tablets in 3.0. This feature is now available to phones as

well. We cover drag-and-drop in Chapter 28.

Handheld devices are fully aware of a cloud-based environment. To make server-side

HTTP calls, it is important to understand the threading model to avoid Application Not

Responding messages. We cover the mechanisms available for asynchronous

processing in Chapter 18.

Outside of the Android SDK, there are a number of independent innovations taking place

to make development exciting and easy. Some examples are XML/VM, PhoneGap, and

Titanium. Titanium allows you to use HTML technologies to program the WebKit-based

Android browser. We covered Titanium in the second edition of this book. However, due

to time and space limitations, we are not covering Titanium in this edition.

CHAPTER 1: Introducing the Android Computing Platform

Android Service Components

Security is a fundamental part of the Android platform. In Android, security spans all

phases of the application life cycle—from design-time policy considerations to runtime

boundary checks. We cover security and permissions in Chapter 14.

In Chapter 15, we’ll show you how to build and consume services in Android,

specifically HTTP services. This chapter will also cover interprocess communication

(communication between applications on the same device).

Location-based service is another of the more exciting components of the Android SDK.

This portion of the SDK provides application developers with APIs to display and

manipulate maps, as well as obtain real-time device-location information. We’ll cover

these ideas in detail in Chapter 22.

Android Media and Telephony Components

Android has APIs that cover audio, video, and telephony components. Chapter 23 will

address the telephony API. We’ll cover the audio and video APIs extensively in

Chapter 24.

Starting with Android 2.0, Android includes the Pico Text-to-Speech engine. Due to

space limitations, we are not able to include Text-to-Speech coverage in the fourth

edition of the book. The third edition does cover the Text-to-Speech API.

Last but not least, Android ties all these concepts into an application by creating a single

XML file that defines what an application package is. This file is called the application’s

manifest file (AndroidManifest.xml). Here is an example:

<?xml version="1.0" encoding="utf-8"?>

<manifest xmlns:android="http://schemas.android.com/apk/res/android"

package="com.ai.android.HelloWorld"

android:versionCode="1"

android:versionName="1.0.0">

<activity android:name=".HelloWorld"

android:label="@string/app_name">

<intent-filter>

</intent-filter>

</activity>

</application>

</manifest>

The Android manifest file is where activities are defined, where services and content

providers are registered, and where permissions are declared. Details about the

manifest file will emerge throughout the book as we develop each idea.

CHAPTER 1: Introducing the Android Computing Platform

Android Java Packages

One way to get a quick snapshot of the Android platform is to look at the structure of

Java packages. Because Android deviates from the standard JDK distribution, it is

important to know what is supported and what is not. Here’s a brief description of the

important packages that are included in the Android SDK:

android.app: Implements the Application model for Android. Primary

classes include Application, representing the start and stop

semantics, as well as a number of activity-related classes, fragments,

controls, dialogs, alerts, and notifications. We work with most of these

classes through out this book.

android.app.admin: Provides the ability to control the device by folks

such as enterprise administrators.

android.accounts: Provides classes to manage accounts such as

Google, Facebook, and so on. The primary classes are

AccountManager and Account. We cover this API briefly in Chapter 30

when we discuss the Contacts API.

android.animation: Hosts all the new property animation classes.

These clases are extensively covered in Chapter 21.

android.app.backup: Provides hooks for applications to back up and

restore their data when folks switch their devices.

android.appwidget: Provides functionality for home screen widgets.

This package is covered extensively in Chapter 25 and Chapter 26

when we talk about home screen widgets, including list-based

widgets.

android.bluetooth: Provides a number of classes to work with

Bluetooth functionality. The main classes include BluetoothAdapter,

BluetoothDevice, BluetoothSocket, BluetoothServerSocket, and

BluetoothClass. You can use BluetoothAdapter to control the locally

installed Bluetooth adapter. For example, you can enable it, disable it,

and start the discovery process. BluetoothDevice represents the

remote Bluetooth device that you are connecting with. The two

Bluetooth sockets are used to establish communication between the

devices. A Bluetooth class represents the type of Bluetooth device you

are connecting to.

android.content: Implements the concepts of content providers.

Content providers abstract out data access from data stores. This

package also implements the central ideas around intents and Android

Uniform Resource Identifiers (URIs). These classes are covered in

Chapter 4.

CHAPTER 1: Introducing the Android Computing Platform

android.content.pm: Implements package manager–related classes. A

package manager knows about permissions, installed packages,

installed providers, installed services, installed components such as

activities, and installed applications.

android.content.res: Provides access to resource files, both

structured and unstructured. The primary classes are AssetManager

(for unstructured resources) and Resources. Some of the classes from

this package are covered in Chapter 3.

android.database: Implements the idea of an abstract database. The

primary interface is the Cursor interface. Some of the classes from this

package are covered in Chapter 4.

android.database.sqlite: Implements the concepts from the

android.database package using SQLite as the physical database.

Primary classes are SQLiteCursor, SQLiteDatabase, SQLiteQuery,

SQLiteQueryBuilder, and SQLiteStatement. However, most of your

interaction is going to be with classes from the abstract

android.database package.

android.drm: Classes related to Digital Rights Management.

android.gesture: Houses all the classes and interfaces necessary to

work with user-defined gestures. Primary classes are Gesture,

GestureLibrary, GestureOverlayView, GestureStore, GestureStroke,

and GesturePoint. A Gesture is a collection of GestureStrokes and

GesturePoints. Gestures are collected in a GestureLibrary. Gesture

libraries are stored in a GestureStore. Gestures are named so that they

can be identified as actions. Some of the classes from this package

are covered in Chapter 27.

android.graphics: Contains the classes Bitmap, Canvas, Camera, Color,

Matrix, Movie, Paint, Path, Rasterizer, Shader, SweepGradient, and

TypeFace.

android.graphics.drawable: Implements drawing protocols and

background images, and allows animation of drawable objects.

android.graphics.drawable.shapes: Implements shapes including

ArcShape, OvalShape, PathShape, RectShape, and RoundRectShape.

android.hardware: Implements the physical Camera-related classes.

The Camera represents the hardware camera, whereas

android.graphics.Camera represents a graphical concept that’s not

to a physical camera at all.

android.hardware.usb: Lets you talk to USB devices from Android.

剩余1007页未读，继续阅读

abcd9532abcd

粉丝: 38
资源: 7

Pro.Android 4 PDF英版：从入门到高级开发指南

Apress.Pro.Android.Games.2Ed.2012

[android.开发书籍].Apress.Pro.Android.Media.Dec.2010.pdf

Beginning.Android.4.Application.Development.pdf

如何手动在 build.gradle 文件中应用 com.android.application 或 com.android.library 插件

world.letsgo.booster.android.pro

D8: java.lang.ClassCastException: com.android.tools.r8.graph.R0 incompatible with com.android.tools.r8.graph.q0

pdf fixer pro.rar

pb 调用foxitpdfsdk_ax_pro.ocx读取pbf

最新资源