1、 毕业论文 (设计 ) 外 文 翻 译 原文来源 Android A Programmers Guide 中 文翻译 安卓程序员指南 学 院 数学与计算机科学学院 专 业 网络 工程 姓 名 学 号 200808204105 指导教师 Android A Programmers Guide J.F. DiMarzio New York Chicago San Francisco Lisbon London Madrid Mexico City Milan New Delhi San Juan Seoul Singapore Sydney Toronto About the Author J.F
2、. DiMarzio is a developer with over 15 years of experience in networking and application development and is the author of seven books on computing technologies. He has become a leading resource in the fields of IT consulting and development. He lives in Central Florida. About the Technical Editor Gi
3、lbert L. Polo is a software developer with over 20 years of experience working in the telecommunications, financial, and, most recently, educational industries. He has programmed in various languages including C, C+, Java, and C#. Chapter1 What Is Android? Key Skills & Concepts History of embedded d
4、evice programming Explanation of Open Handset Alliance First look at the Android home screen It can be said that, for a while, traditional desktop application developers have been spoiled. This is not to say that traditional desktop application development is easier than other forms of development.
5、However, as traditional desktop application developers, we have had the ability to create almost any kind of application we can imagine. I am including myself in this grouping because I got my start in desktop programming. One aspect that has made desktop programming more accessible is that we have
6、had the ability to interact with the desktop operating system, and thus interact with any underlying hardware, pretty freely (or at least with minimal exceptions). This kind of freedom to program independently, however, has never really been available to the small group of programmers who dared to v
7、enture into the murky waters of cell phone development. NOTE I refer to two different kinds of developers in this discussion: traditional desktop application developers, who work in almost any language and whose end product, applications, are built to run on any “desktop” operating system； and Andro
8、id developers, Java developers who develop for the Android platform. This is not for the purposes of saying one is by any means better or worse than the other. Rather, the distinction is made for purposes of comparing the development styles and tools of desktop operating system environments to the m
9、obile operating system environment, Android. Brief History of Embedded Device Programming For a long time, cell phone developers comprised a small sect of a slightly larger group of developers known as embedded device developers. Seen as a less “glamorous” sibling to desktopand later webdevelopment,
10、 embedded device development typically got the 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,
11、 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
12、 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
