使用Eclipse开发Android应用指南

需积分: 0 155 浏览量更新于2024-07-23 收藏 17.85MB PDF 举报

"Android Apps with Eclipse" 本书"Android Apps with Eclipse"是针对Android应用程序开发的一本指南，特别强调了使用Eclipse集成开发环境进行开发的方法。虽然书籍是英文版，但内容表述清晰，非常适合初学者阅读，被认为比某些中文教材更易理解和深入。作者通过章节结构系统地介绍了Android开发的核心知识点： 1. **Chapter 1: Android Primer** - 这一章为读者提供了Android的基础知识，包括Android的历史、生态系统以及它在移动市场中的地位。这里会讲解操作系统的基本概念，如Linux内核和Dalvik虚拟机。 2. **Chapter 2: Application Architecture** - 这部分深入探讨了Android应用的架构，包括组件（Activity、Service、BroadcastReceiver和ContentProvider）的概念和它们如何相互协作。还会涉及AndroidManifest.xml文件的重要性和作用。 3. **Chapter 3: Eclipse Primer** - 介绍Eclipse IDE的使用，包括如何安装Eclipse，设置Android开发者工具（ADT），以及创建和管理Android项目的基本步骤。 4. **Chapter 4: Mastering Eclipse** - 进一步深化Eclipse的使用技巧，涵盖调试、版本控制、代码重构和优化项目组织结构等内容。 5. **Chapter 5: Android Development Tools for Eclipse** - 专门讲解ADT插件的功能，包括布局编辑器、图形化资源管理以及性能分析工具的使用。 6. **Chapter 6-10: Project: Movie Player** - 这些章节通过构建一个电影播放器应用来实践所学知识，涉及多媒体处理、用户界面设计、网络通信等多个方面。其中，第7章引入了原生开发，第8章扩展到支持AVI格式，第9章讨论了使用脚本语言进行Android开发，第10章则展示了如何用HTML和JavaScript实现类似功能。 7. **Appendix A: Testing Android Applications** - 提供了关于测试Android应用的指导，包括单元测试、UI测试和自动化测试框架的使用。 8. **Index** - 完整的索引方便读者查找特定主题。通过对这本书的学习，读者不仅可以掌握Android应用开发的基础，还能熟练运用Eclipse进行高效开发，并了解如何利用Eclipse的扩展功能和工具来提高生产力。此外，书中包含的实际项目案例有助于将理论知识转化为实践经验，对提升开发者解决实际问题的能力大有裨益。对于想进入Android开发领域的初学者或希望增强Eclipse使用技能的开发者来说，这是一本非常有价值的资源。

CHAPTER 1: Android Primer

Figure 1-3. Binder kernel module allowing two applications to communicate

Binder’s user-space code maintains a pool of threads in each process, and

these threads are used to process incoming Binder requests as local events.

Binder is also responsible for tracking the object references across processes.

Additionally, Binder provides an extra level of security, by transmitting the user

and group ID of the calling process with each Binder request.

Binder is a key construct in the Android platform. It is the central messaging

channel across the entire Android platform. Android applications communicate

with the system, services, and each other through the Binder interface.

Although Binder is implemented as a low-level service, application developers

are not expected to directly interact with it. The Android runtime provides the

android.os.IBinder interface as the API to communicate with other processes

through Binder. Android provides the Android Interface Definition Language

(AIDL), which is tuned for Binder.

AIDL allows you to define the programming interface that the client and server

will use to communicate with each other. As with many other operating systems,

on Android, the processes are not allowed to access the memory of another

process directly. AIDL provides the functionality to decompose the objects into

primitives that Binder can understand and use across project boundaries.

CHAPTER 1: Android Primer

Threading is one of the most important parts of interacting with Binder:

 Calls made from the local process are executed in the calling

thread. Binder calls are synchronous and will block the current

thread until the request is processed. If the request is

expected to take a long time to complete, the request should

not be made from the application’s main thread. This would

make the application hang, and may result in the application

being terminated by the Android platform. Binder also

supports nonblocking requests through the oneway attribute.

 Calls from a remote process are dispatched from the thread

pool provided by the local process. The service code is

expected to be thread-safe, since the requests can be

executed by any of these threads.

Android SDK provides the necessary code generators to translate programming

interfaces that are defined in AIDL into actual Java classes. Application

developers are only expected to provide the implementation for the generated

interface and the Android service that will provide the interface to the clients.

Wakelocks

Android is designed to operate on mobile platforms with scarce resources.

Because of this, Android devices go into sleep mode very frequently. Although

this allows the system to use the available resources efficiently, it is not

preferable for the device to go into sleep mode while the kernel or an application

is in the middle of an important process. Wakelocks were introduced as a kernel

patch in order to allow an application to prevent the system from going into

sleep mode while it is performing a task.

Two types of wakelocks are supported by the Android platform:

 An idle wakelock prevents the system from entering a low-

power idle state.

 A suspend wakelock prevents the system from entering a full-

system suspend state.

Application developers interact with wakelocks through the

android.os.PowerManager.WakeLock interface. To use this interface, the

application should request android.permission.WAKE_LOCK in advance.

Wakelocks should be used with caution. Preventing the device from going into

sleep mode will increase the power consumption, which will eventually cause it

to run out of battery power. An application should hold the wakelock during

CHAPTER 1: Android Primer

simplify this procedure, the Android logging system groups the log messages

into four separate log buffers:



Main:

Main application log messages



Events:

System events



Radio:

Radio-related log messages



System:

Low-level system debug messages for debugging

These four buffers are kept as pseudo-devices under the /dev/log system

directory. Since input and output (I/O) operations on mobile platforms are very

costly, the log messages are not saved in persistent storage; instead, they are

kept in memory. In order to keep the memory utilization of the log messages

under control, the logger module puts them in fixed-sized buffers. Main, radio,

and system logs are kept as free-form text messages in 64KB log buffers. The

event log messages carry additional information in binary format, and they are

kept in a 256KB log buffer.

A set of user-level applications is also provided to view and filter these logs,

such as the logcat and the Dalvik Debug Monitor Server

(DDMS) tools, which we

will examine in chapter 5.

The Android runtime provides a set of API calls to allow applications to easily

send their log messages to the logger. Application log messages are sent

through the following classes:

 android.util.Log: This class is used to send application log

messages. It provides a set of methods to specify the priority

of the message, as well as a tag to indicate which application

is generating this log message.

 android.util.EventLog: This class is used to send event log

messages in binary format.

 android.util.Slog: This class is used by the Android runtime

components to send system log messages. It is not part of the

Android API, and it is not accessible from the applications.

Zygote

On most UNIX-like operating systems, the application that is known as Init is

considered as the parent of all processes. Init gets started after the kernel

successfully boots. Its primary role is to start a set of other processes based on

the system configuration.

剩余367页未读，继续阅读

hpf880812

粉丝: 0
资源: 2

使用Eclipse开发Android应用指南

在Eclipse中进行Android编程（Apress.Android.Apps.with.Eclipse.Jun.2012.pdf）

Android Apps with Eclipse

Android Apps with Eclipse.pdf

Gradle.for.Android.1783986824

履带式拖拉机Creo2.0_三维3D设计图纸.zip

SSM+JSP高校毕业生就业满意度调查统计系统答辩PPT.pptx

SSM+JSP冰淇淋在线购买网站答辩PPT.ppt

SSM+JSP医护系统答辩PPT.pptx

Shapely-1.6.4.post2-cp35-cp35m-win_amd64.whl

SSM+JSP农场信息化管理系统答辩PPT.pptx

最新资源