Android程序员实战指南：从基础到高级应用开发

android

程序员指南

需积分: 7 63 浏览量更新于2024-07-18 收藏 7.23MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Introduction

elcome to Android: A Programmer’s Guide. This book has been designed to give

you the best first step toward the exciting new frontier of open source mobile

development. Android is the newest mobile device operating system, and this is one

of the first books to help the average programmer become a fearless Android developer.

Through the course of this book, you will be introduced to the fundamentals of mobile

device application development using the Open Handset Alliance’s Android platform.

By the end of this book, you will be able to confidently create your own mobile device

programs.

The format of this book is such that it will take you through Android application

development in a logical manner. The book begins by examining the architecture of

Android as a platform, looking at how it was developed, what it can run on, and what

tools are required to develop programs for it. After discussing and installing the

development tools, Android SDK, and the Eclipse development environment

(Chapters 2, 3, and 4), the book dives directly into designing and creating Android

applications (Chapter 5). The book concludes with instructions on tying your applications

to existing Google tools such as Google Maps (Chapters 9 and 11) and GTalk (Chapter

10). A quick reference guide is also included in Chapter 12.

This book is a programmer’s guide, not a beginner’s guide, meaning that you do need

to possess some programming skills to get the most from it. Foremost among these skills

is a working knowledge of Java programming fundamentals. Android applications are

Chapter 1: What Is Android? 3

proverbial short end of the stick as far as hardware and operating system features, because

embedded device manufacturers were notoriously stingy on feature support. Embedded

device manufacturers typically needed to guard their hardware secrets closely, so they

gave embedded device developers few libraries to call when trying to interact with a

specific device.

Embedded devices differ from desktops in that an embedded device is typically a

“computer on a chip.” For example, consider your standard television remote control; it is

not really seen as an overwhelming achievement of technological complexity. When any

button is pressed, a chip interprets the signal in a way that has been programmed into the

device. This allows the device to know what to expect from the input device (key pad),

and how to respond to those commands (for example, turn on the television). This is a

simple form of embedded device programming. However, believe it or not, simple

devices such as these are definitely related to the roots of early cell phone devices and

development.

Most embedded devices ran (and in some cases still run) proprietary operating

systems. The reason for choosing to create a proprietary operating system rather than use

any consumer system was really a product of necessity. Simple devices did not need very

robust and optimized operating systems.

As a product of device evolution, many of the more complex embedded devices, such

as early PDAs, household security systems, and GPSs, moved to somewhat standardized

operating system platforms about five years ago. Small-footprint operating systems such

as Linux, or even an embedded version of Microsoft Windows, have become more

prevalent on many embedded devices. Around this time in device evolution, cell phones

branched from other embedded devices onto their own path. This branching is evident

when you examine their architecture.

Nearly since their inception, cell phones have been fringe devices insofar as they run

on proprietary software—software that is owned and controlled by the manufacturer, and

is almost always considered to be a “closed” system. The practice of manufacturers using

proprietary operating systems began more out of necessity than any other reason. That is,

cell phone manufacturers typically used hardware that was completely developed in-house,

or at least hardware that was specifically developed for the purposes of running cell phone

equipment. As a result, there were no openly available, off-the-shelf software packages

or solutions that would reliably interact with their hardware. Since the manufacturers

also wanted to guard very closely their hardware trade secrets, some of which could be

revealed by allowing access to the software level of the device, the common practice

剩余335页未读，继续阅读

derek_lee

粉丝: 0
资源: 2

Android程序员实战指南：从基础到高级应用开发

Android程序员指南[1]

Android程序员指南-- Android A Programmers'Guide[中文版]

[Publish]Android程序员指南-J.F.

Android程序员如何年薪100万

vxworks程序员指南pdf

windows 程序员指南3 pdf

android程序员面试笔试宝典 pdf 网盘

ansys uidl程序员指南

visual c++ 程序员指南

visual c++程序员指南

scsi程序员指南.pdf

jni程序员指南与规范.pdf

Android程序员 未来总过方向和目标

uml java程序员指南

android studio 程序员计算器

android studio 程序员计算器代码

c/c++程序员面试指南 杨国祥pdf

你是一名android程序员，userdata reserve前后版本大小不一致ota升级失败的原因是什么

Android 人工智能

黑马程序员的Android studio的书

最新资源

Android程序员未来总过方向和目标

c/c++程序员面试指南杨国祥pdf