基于Android开发的外文文献

Android

Android, as a system, is a Java-based operating system that runs on the Linux 2.6 kernel. The system is very lightweight and full featured. Android applications are developed using Java and can be ported rather easily to the new platform. If you have not yet downloaded Java or are unsure about which version you need, I detail the installation of the development environment in Chapter 2. Other features of Android include an accelerated 3-D graphics engine (based on hardware support), database support powered by SQLite, and an integrated web browser.

If you are familiar with Java programming or are an OOP developer of any sort, you are likely used to programmatic user interface (UI) development—that is, UI placement which is handled directly within the program code. Android, while recognizing and allowing for programmatic UI development, also supports the newer, XML-based UI layout. XML UI layout is a fairly new concept to the average desktop developer. I will cover both the XML UI layout and the programmatic UI development in the supporting chapters of this book.

One of the more exciting and compelling features of Android is that, because of its architecture, third-party applications—including those that are “home grown”—are executed with the same system priority as those that are bundled with the core system. This is a major departure from most systems, which give embedded system apps a greater execution priority than the thread priority available to apps created by third-party developers. Also, each application is executed within its own thread using a very lightweight virtual machine.

Aside from the very generous SDK and the well-formed libraries that are available to us to develop with, the most exciting feature for Android developers is that we now have access to anything the operating system has access to. In other words, if you want to create an application that dials the phone, you have access to the phone’s dialer; if you want to create an application that utilizes the phone’s internal GPS (if equipped), you have access to it. The potential for developers to create dynamic and intriguing applications is now wide open.

On top of all the features that are available from the Android side of the equation, Google has thrown in some very tantalizing features of its own. Developers of Android applications will be able to tie their applications into existing Google offerings such as Google Maps and the omnipresent Google Search. Suppose you want to write an application that pulls up a Google map of where an incoming call is emanating from, or you want to be able to store common search results with your contacts; the doors of possibility have been flung wide open with Android.

Chapter 2 begins your journey to Android development. You will learn the how’s and why’s o f using specific development environments or integrated development environments (IDE), and you will download and install the Java IDE Eclipse.

Application Components

A central feature of Android is that one application can make use of elements of other applications (provided those applications permit it). For example, if your application needs to display a scrolling list of images and another application has developed a suitable scroller and made it available to others, you can call upon that scroller to do the work, rather than develop your own. Your application doesn't incorporate the code of the other application or link to it. Rather, it simply starts up that piece of the other application when the need arises.

For this to work, the system must be able to start an application process when any part of it is needed, and instantiate the Java objects for that part. Therefore, unlike applications on most other systems, Android applications don't have a single entry point for everything in the application (no main() function, for example). Rather, they have essential components that the system can instantiate and run as needed. There are four types of components:

Activities

An activity presents a visual user interface for one focused endeavor the user can undertake. For example, an activity might present a list of menu items users can choose from or it might display photographs along with their captions. A text messaging application might have one activity that shows a list of contacts to send messages to, a second activity to write the message to the chosen contact, and other

activities to review old messages or change settings. Though they work together to form a cohesive user interface, each activity is independent of the others. Each one is implemented as a subclass of the Activity base class.

An application might consist of just one activity or, like the text messaging application just mentioned, it may contain several. What the activities are, and how many there are depends, of course, on the application and its design. Typically, one of the activities is marked as the first one that should be presented to the user when the application is launched. Moving from one activity to another is accomplished by having the current activity start the next one.

Each activity is given a default window to draw in. Typically, the window fills the screen, but it might be smaller than the screen and float on top of other windows. An activity can also make use of additional windows — for example, a pop-up dialog that calls for a user response in the midst of the activity, or a window that presents users with vital information when they select a particular item on-screen.

The visual content of the window is provided by a hierarchy of views — objects derived from the base View class. Each view controls a particular rectangular space within the window. Parent views contain and organize the layout of their children. Leaf views (those at the bottom of the hierarchy) draw in the rectangles they control and respond to user actions directed at that space. Thus, views are where the activity's interaction with the user takes place.

For example, a view might display a small image and initiate an action when the user taps that image. Android has a number of ready-made views that you can use —including buttons, text fields, scroll bars, menu items, check boxes, and more.

A view hierarchy is placed within an activity's window by the Activity.setContentView() method. The content view is the View object at the root of the hierarchy. (See the separate User Interface document for more information on views and the hierarchy.)

Services

A service doesn't have a visual user interface, but rather runs in the background for an indefinite period of time. For example, a service might play background music

as the user attends to other matters, or it might fetch data over the network or calculate something and provide the result to activities that need it. Each service extends the Service base class.

A prime example is a media player playing songs from a play list. The player application would probably have one or more activities that allow the user to choose songs and start playing them. However, the music playback itself would not be handled by an activity because users will expect the music to keep playing even after they leave the player and begin something different. To keep the music going, the media player activity could start a service to run in the background. The system would then keep the music playback service running even after the activity that started it leaves the screen.

It's possible to connect to (bind to) an ongoing service (and start the service if it's not already running). While connected, you can communicate with the service through an interface that the service exposes. For the music service, this interface might allow users to pause, rewind, stop, and restart the playback.

Like activities and the other components, services run in the main thread of the application process. So that they won't block other components or the user interface, they often spawn another thread for time-consuming tasks (like music playback). See Processes and Threads, later.

Broadcast receivers

A broadcast receiver is a component that does nothing but receive and react to broadcast announcements. Many broadcasts originate in system code — for example, announcements that the timezone has changed, that the battery is low, that a picture has been taken, or that the user changed a language preference. Applications can also initiate broadcasts — for example, to let other applications know that some data has been downloaded to the device and is available for them to use.

An application can have any number of broadcast receivers to respond to any announcements it considers important. All receivers extend the BroadcastReceiver base class.

Broadcast receivers do not display a user interface. However, they may start an

activity in response to the information they receive, or they may use the NotificationManager to alert the user. Notifications can get the user's attention in various ways — flashing the backlight, vibrating the device, playing a sound, and so on. They typically place a persistent icon in the status bar, which users can open to get the message.

Content providers

A content provider makes a specific set of the application's data available to other applications. The data can be stored in the file system, in an SQLite database, or in any other manner that makes sense. The content provider extends the ContentProvider base class to implement a standard set of methods that enable other applications to retrieve and store data of the type it controls. However, applications do not call these methods directly. Rather they use a ContentResolver object and call its methods instead. A ContentResolver can talk to any content provider; it cooperates with the provider to manage any interprocess communication that's involved.

See the separate Content Providers document for more information on using content providers.

Whenever there's a request that should be handled by a particular component, Android makes sure that the application process of the component is running, starting it if necessary, and that an appropriate instance of the component is available, creating the instance if necessary.

Key Skills & Concepts

●Creating new Android projects

●Working with Views

●Using a TextView

●Modifying the main.xml file

Creating Your First Android Project in Eclipse

To start your first Android project, open Eclipse. When you open Eclipse for the first time, it opens to an empty development environment (see Figure 5-1), which is where you want to begin. Your first task is to set up and name the workspace for your application. Choose File | New | Android Project, which will launch the New Android

Project wizard.

CAUTION Do not select Java Project from the New menu. While Android applications are written in Java, and you are doing all of your development in Java projects, this option will create a standard Java application. Selecting Android Project enables you to create Android-specific applications.If you do not see the option for Android Project, this indicates that the Android plugin for Eclipse was not fully or correctly installed. Review the procedure in Chapter 3 for installing the Android plugin for Eclipse to correct this.

The New Android Project wizard creates two things for you

A shell application that ties into the Android SDK, using the android.jar file, and ties the project into the Android Emulator. This allows you to code using all of the Android libraries and packages, and also lets you debug your applications in the proper environment.

Your first shell files for the new project. These shell files contain some of the vital application blocks upon which you will be building your programs. In much the same way as creating a Microsoft .NET application in Visual Studio generates some Windows-created program code in your files, using the Android Project wizard in Eclipse generates your initial program files and some Android-created code. In addition, the New Android Project wizard contains a few options, shown next, that you must set to initiate your Android project. For the Project Name field, for purposes of this example, use the title HelloWorldText. This name sufficiently distinguishes this Hello World! project from the others that you will be creating in this chapter.In the Contents area, keep the default selections: the Create New Project in Workspace radio button should be selected and the Use Default Location check box should be checked. This will allow Eclipse to create your project in your default workspace directory. The advantage of keeping the default options is that your projects are kept in a central location, which makes ordering, managing, and finding these projects quite easy. For example, if you are working in a Unix-based environment, this path points to your $HOME directory.

If you are working in a Microsoft Windows environment, the workspace path

will be C:/Users//workspace, as shown in the previous illustration. However, for any number of reasons, you may want to uncheck the Use Default Location check box and select a different location for your project. One reason you may want to specify a different location here is simply if you want to choose a location for this specific project that is separate from other Android projects. For example, you may want to keep the projects that you create in this book in a different location from projects that you create in the future on your own. If so, simply override the Location option to specify your own custom location directory for this project.

外文翻译-基于Android智能家居系统

通信工程学院 毕业设计外文翻译 毕业设计题目基于ANDRIO的智能家居 系统的设计与实现 外文题目UBIQUITOUS SMART HOME SYSTEM USING ANDROID APPLICATION 专业：通信工程 学号： 学生姓名： 指导教师姓名： 指导教师职称：副教授 日期：2015 年 1 月10 日

International Journal of Computer Networks & Communications (IJCNC) V ol.6, No.1, January 2014 基于Android应用的无处不在的智能家居系统 Shiu Kumar Department of Information Electronics Engineering, Mokpo National University, 534-729, Mokpo, South Korea 摘要 本文提出了一种灵活独立的，低成本的智能家居系统，它是基于Android应用与微web服务器通信，不仅仅提供交换功能。Arduino以太网的使用是为了避免使用个人电脑从而保证整个系统成本最低，语音激活时用来实现切换功能的。光开关，电源插头，温度传感器，湿度传感器，电流传感器，入侵检测传感器，烟雾/气体传感器和警报器等这些设备集成在系统中，表明了所提出的智能家居系统的有效性和可行性。经过检测，智能家居应用程序可以成功地进行智能家居操作，例如开关功能，自动环境监测，和入侵监测，在监测到有不法入侵后，系统会自动发送一个邮件，并响警笛。 关键字： Android智能手机，智能家居，物联网（loTs），远程控制 1.引言 随着移动设备受欢迎程度的不断增长和人们日常生活中对无处不在的先进的移动应用的功能需求不断增加，利用Web服务是提供远程访问服务的最开放和可互操作的方式，并且使应用程序能够彼此通信。一个有吸引力的市场产品自动化和网络化是忙碌的家庭和有生理缺陷的个人的代表。 loTs可以被描述为连接智能手机，网络电视，传感器等到互联网，实现人们之间沟通的新形势。过去几年中loTs的发展，创造了一个新层面的世界。这使得人们可以在任何时间，任何地点，联通任何期望的东西。物联网技术可用于为智能家居创建新的概念和广阔的空间，以提供智能，舒适的发展空间和完善生活质量。 智能家居是一个非常有前途的领域，其中有各种好处，如增加提供舒适性，更高安全性，更合理地使用能源和其他资源。这项研究的应用领域非常重要，未来它为帮助和支持有特殊需求老的人和残疾人士提供了强有力的手段。设计一个智能家居系统时需要考虑许多因素，该系统应该是经济实惠的，是可伸缩的，使得新的设备可以容易地集成到系统中，此外，它应该是用户友好的。 随着智能手机用户的急剧增加，智能手机已经逐渐变成了具备所有功能的便携式设备，为人们提供了日常使用。本文介绍了一种低成本的控制和监视家居环境控制的无线智能家居系统。利用Android设备，可以通过一个嵌入式微Web服务器与实际的IP连接，访问和控制电器和远程的其它设备，这可以利用任何支持Android的设备。Arduino Ethernet 用于微Web服务器从

(精品文献)Android外文翻译

本科毕业设计（论文）外文参考文献译文及原文 学院信息工程学院 专业测控技术与仪器 （光机电一体化方向) 年级班别 2011级（1）班 学号 学生姓名 指导教师

目录 1应用程序基础 (1) 1.1应用程序组件 (1) 1.2激活组件：intent (3) 1.3 关闭组件 (4) 1.4manifest文件 (5) 1.5Intent过滤器 (6) 1.6基于XML的布局 (7) 1Application Fundamentals (8) 1.1 Application Components (8) 1.2Activating components:intent (11) 1.3 Shutting down components (12) 1.4 The manifest file (13) 1.5Intent filters (14) 1.6XML-Based Layout (15)

1 应用程序基础 Android应用程序使用Java编程语言开发。aapt工具把编译后的Java代码连同应用程序所需的其他数据和资源文件一起打包到一个Android包文件中，这个文件使用.apk作为扩展名。此文件是分发并安装应用程序到移动设备的载体；是用户下载到他们的设备的文件。单一.apk文件中的所有代码被认为是一个应用程序。 从多个角度来看，每个Android应用程序都存在于它自己的世界之中： 1 默认情况下，每个应用程序均运行于它自己的Linux进程中。当应用程序中的任何代码需要被执行时，Android启动此进程，而当不再需要此进程并且其它应用程序又请求系统资源时，则就关闭了这个进程。 2 每个进程都有其独有的虚拟机（VM），所以应用程序代码与所有其它应用程序代码是隔离运行的。 3 默认情况下，每个应用程序均被赋予一个唯一的Linux用户ID，并加以权限设置，使得应用程序的文件仅对此用户及此应用程序可见——尽管也有其它的方法使得这些文件同样能为其他应用程序所访问。 1.1 应用程序组件 Android的一个核心的特性就是一个应用程序可以使用其它应用程序的元素（如果那个应用程序允许的话）。例如，如果你的应用程序需要显示一个图片卷动列表，而另一个应用程序已经开发了一个合用的而又允许别的应用程序使用的话，你可以直接调用那个卷动列表来完成工作，而不用自己再开发一个。你的应用程序并没有吸纳或链接其它应用程序的代码。它只是在有需求的时候启动了其它应用程序的那个功能部分。 为达到这个目的，系统必须能够在一个应用程序的任何一部分被需要时启动一个此应用程序的进程，并将那个部分的Java对象实例化。因此，不像其它大多数系统上的应用程序，Android应用程序并没有为应用程序提供一个单独的入口点（比如说，没有main()函数），而是为系统提供了可以实例化和运行所需的必备组件。一共有四种组件类型： (1)Activity

Android手机外文翻译---应用程序基础Android Developers

英文原文及译文 Application Fundamentals Android applications are written in the Java programming language. The compiled Java code —along with any data and resource files required by the application —is bundled by the aapt tool into an Android package, an archive file marked by an .apk suffix. This file is the vehicle for distributing the application and installing it on mobile devices; it's the file users download to their devices. All the code in a single .apk file is considered to be one application. In many ways, each Android application lives in its own world: 1. By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications. 2. Each process has its own virtual machine (VM), so application code runs in isolation from the code of all other applications. 3. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only to that user and only to the application itself — although there are ways to export them to other applications as well. It's possible to arrange for two applications to share the same user ID, in which case they will be able to see each other's files. To conserve system resources, applications with the same ID can also arrange to run in the same Linux process, sharing the same VM. Application Components A central feature of Android is that one application can make use of elements of other applications (provided those applications permit it). For example, if your application needs to display a scrolling list of images and another application has developed a suitable scroller and made it available to others, you can call upon that scroller to do the work, rather than develop your own. Your application doesn't incorporate the code of the other application or link to it. Rather, it simply starts up that piece of the other application when the need arises. For this to work, the system must be able to start an application process when any part of it is needed, and instantiate the Java objects for that part. Therefore, unlike applications on most other systems, Android applications don't have a single entry point for everything in the application (no main() function, for example). Rather, they have essential components that the system can instantiate and run as needed. There are four types of components: Activities

基于安卓的大学生记账管理系统的设计与实现-外文翻译译文和原文

基于安卓的大学生记账管理系统的设计与实现-外文翻译译 文和原文 毕业设计外文文献翻译 院系: 计算机与信息工程学院年级专业: 12软件工程(金融服务)2 姓名: 学号: An Analysis of Personal Financial Lit Among 附件: College Students Among College Students 指导老师评语: 指导教师签名: 年月日 大学生个人理财知识分析 大学生个人理财知识分析 这项研究调查了924名大学生审视自己的个人财务知识;调查了学生的财务知识与学生的特性之间的关系，和理财知识对学生的意见和决定的影响。结果表明，参与者回答问题的正确性为53,。所调查的人包括非经营性专业、妇女、在下层阶级行列的学生、30岁以下并且很少有工作经验的人、知识水平较低者。懂得较少财务知识的学生往往有错误的观点和作出不正确的决定。结论是:大学生不太了解个人理财。低的财务知识水平会限制他们做出明智决策的能力。 I. 介绍 管理个人财务的能力在当今世界已经变得越来越重要。人们必须计划为他们的退休和子女的教育长期投资。他们还必须决定短期储蓄和借贷一个假期，向下支付

房子，汽车贷款和其他大件物品。此外，他们还必须管理自己的医疗保险和人寿保险的需求。 不幸的是，研究表明，美国人有个人认识不足财政(EBRI，1995年，毕马威会计师事务所，1995年; PSRA，1996年，1997年，奥本海默基金/女孩公司，1997年;先锋集团/货币杂志，1997年)。他们未能作出正确决策因为他们还没有收到良好的个人理财教育(HSR，1993年，希拉，1993;奥尼尔，1993年)。 这项研究有三个目的。首先，它提供大学生个人理财素养的证据。其次，它会检查为什么一些大学生相对比别人有更多的理财知识。该分析可以帮助我们识别出大学生所拥有决定能力水平的因素。第三个目的是检查学生的知识如何影响他/她的意见和个人财务问题上的决定。 本文的结构安排如下。第二部分回顾了以前对金融知识的研究。第三部分是讨论方法。第四部分是提出的结果。第五部分总结全文。 II. 文献回顾 大部分以前的研究都是由在金融服务行业的从业人员进行。他们专注于资金管理和投资有关的问题。这个重点与会计师财务策划师的调查结果一致，说明这些问题是个人理财规划的重要领域(NEFE，1993-1996)。这些研究结果表明，参与的调查者回答调查问题的正确率普遍只有不到60,。 此前高中生的研究均发现，他们在个人财务的基本知识上未受到良好的教育，并且知识贫乏(巴肯，1967; CFAJAMEX，1991; HSR，1993; Langrehr，1979; NAEP，1979)。在对来自63所学校的1509高中学生的调查研究中，曼德尔(1997)报告了一个平均正确的比分，57,在收入、资金管理、储蓄、投资和消费等领域。他的结论是:学生们离开学校时没有做出关键决策影响他们生活的能力。 难道成年人对个人理财和投资有一个很好的控制,几个结果研究表明，他们并 1

Android系统外文翻译

附录1：外文原文 What Is Android? It can be said that, for a while, traditional desktop application developers have beenspoiled. This is not to say that traditional desktop application development is easier thanother forms of development. However, as traditional desktop application developers, wehave had the ability to create almost any kind of application we can imagine. I amincluding myself in this grouping because I got my start in desktop programming. One aspect that has made desktop programming more accessible is that we havehad the ability to interact with the desktop operating system, and thus interact with anyunderlying hardware, pretty freely (or at least with minimal exceptions). This kind offreedom to program independently, however, has never really been available to thesmall group of programmers who dared to venture into the murky waters of cell phonedevelopment. 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 desktop—and later web—development, 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, 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

Android应用架构外文翻译

Android Application Architecture author：Lars V ogel 1、AndroidManifest.xml The components and settings of an Android application are described in the file AndroidManifest.xml. For example all Activities and Services of the application must be declared in this file. It must also contain the required permissions for the application. For example if the application requires network access it must be specified here. The package attribute defines the base package for the Java objects referred to in this file. If a Java object lies within a different package, it must be declared with the

安卓应用开发基础论文中英文对照资料外文翻译文献

安卓应用开发基础论文中英文对照 资料外文翻译文献 中英文对照资料外文翻译文献安卓应用开发基础在Java编程语言编写的Android应用程序的Android的SDK工具编译代码以及与任何数据和到一个Android的包，一个归档文件档案资源的.apk后缀，所有的在一个单一的代码.apk文件被认为是一个应用程序，是Android的文件，供电设备来安装应用程序。一旦安装在设备上，每个Android应用程序的生命在它自己的安全沙箱：而Android操作系统是一个多用户Linux系统中，每个应用程序是一个不同的用户。默认情况下，每个应用程序的系统分配一个唯一的Linux用户ID，系统设置所有的应用程序中的文件权限，以便只有用户ID分配给该应用程序可以访问它们。每个进程都有它自己的虚拟

机，因此应用程序的代码在从其他应用程序隔离运行。默认情况下，每个应用程序运行在它自己的Linux进程。Android的启动过程时，应用程序的任何组件需要被执行，然后关闭该进程时，它不再需要或恢复时，系统必须为其他应用程序的内存。这样一来，Android系统实现了最小特权原则，也就是说，每个应用程序，默认情况下，只能访问的组件，它需要做的工作，没有更多，这将创建一个非常安全的环境，使应用程序无法访问的，这就是它没有给予许可制度的部分。但是，有一个应用程序的方法与其他应用程序和应用程序访问系统服务的数据：这有可能为两个应用程序安排共享相同的Linux用户ID，在这种情况下，它们能够相互访问的文件。为了节约使用相同的用户ID系统资源，应用程序还1 可以安排运行在相同的Linux进程和共享同一个VM。应用程序可以请求访问权限，如用户的联

Android系统外文翻译3

Android起航 译 使用XML进行布局 虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。动态的小部件实例保留更多，情况复杂，小工具在编译时不为人所知（例如，在数据检索了互联网基础上将单选按钮填充柱。 考虑到这一点，现在是时候打破XML来学习如何用此种方式来布置Android activities。 什么是基于XML的布局？ 正如其名称所示，一个基于XML的布局是一个关系到每个规格的小部件，和他们的容器（更多关于此内容的在第7章）编码的XML格式。具体来说，Android 认为基于XML的布局是资源，因此布局文件存储在res /在你的Android项目布局目录中。 每个XML文件包含一个指定的部件和容器布局元素树，一种意见认为构成层次。对XML元素的属性，描述一个部件应如何看或者一个容器应如何运转。例如，如果一个按钮元素。 有一个Android的属性值：文字样式=“bold”，这意味着该文本出现在按钮的表面应该是呈现一个粗体字体样式. Android的SDK中附带一个使用的布局的工具（aapt）。这个工具应自动调用你的Android工具链（例如，Eclipse中，Ant’s build.xml）。作为一个开发人员，尤其重要的是，在您的项目中aapt生成R.java源文件，让您能在那些布局中直接从Java代码中获取布局和部件。 为什么使用基于XML的布局？ 使用XML布局文件做的大部分都可以通过Java代码。例如，你可以使用setTypeface（）命令一个按钮使用粗体文本，而不是在一个XML布局中使用属性。由于XML布局是为你跟踪的另一个文件，所以我们需要好的理由来使用这样的文

Android毕设外文资料和译文

东北大学东软信息学院 外文资料和译文 专业：计算机科学与技术（嵌入式软件开发方向）班级：计嵌入式000000 姓名：XXXX 学号：08111XXXXX 指导教师：XXXX教授 2011 年 12 月 18 日

译文 这篇文档主要讲述Android应用框架的核心原则。站在高层来说，以用户为中心来设计良好的交互程序，对于应用设计者或是开发者来说是非常重要的。 下面用例子来阐述了activities和tasks的一些底层原则和机制，例如导航，多任务，activity重用，意图和activity栈。这篇文档也着重讨论了一些设计决策，针对如何利用好它们去设计你的应用程序UI。 这篇文档中的例子均是Android应用程序，包括默认应用程序（比如拨号器）、Google 应用程序（比如地图）。你可以自己在Android模拟器上或是Android手机上去试验这些例子。如果你使用Android手机试验时，可能未提供本文档中的某些例子。Applications, Activities, Activity Stack and Tasks 理解Android系统中的四个基本概念对你是很有帮助的，它们分别是： Applications（应用） Activities（活动） Activity Stack（活动堆栈） Tasks（任务） Applications 一个Android应用程序其实就是由一个或者多个Activity组成。它们被捆绑在一起并存放进.apk文件中，这就是Android应用程序。Android中有着丰富的应用程序，比如邮件、日历、地图定位、文本消息、联系人、照相机、打电话、音乐播放器，系统设置等应用。 一般情况下，桌面上都会有Android应用程序快捷图标，用户可以选择某一个图标来启动应用程序。 Activities Activity是Android应用程序的主要组成部分，activity可以是你自己创建的，当然，还可以是其它应用程序中的activity。它们都是在运行时绑定上的，以便于应用程序扩展其自身的功能，它们一旦组合在一起，就会如同一个应用程序一样。每个activity都有其独特的UI、明确的功能，诸如打电话、看照片、听音乐等。任何一个应用程序都应至少有一个activity。 当使用Android手机时，用户在屏幕上一个接一个地滑动或是点击图标启动activity，完全不会注意到底层的行为——他们体验是无缝的。activity后面有activity，task后面还会有task。 Activity可以处理特定的数据类型和接受一相关的动作。每个activity都有其各自的生命周期，互不干扰；并且它们都可以被用户或者系统独立启动、运行、暂停、恢复运行、停止、重新开始。正因为这个独立性，activity可以以不同的方式被其它的activity 进行替换。 Activity是Android应用中最为突出的组件，其余组件分别为：service、content provider、broadcast receiver。 Activity Stack 用户之所以能够从一个activity转到下一个activity，是因为Android系统针对

基于Android的智能公交出行系统软件设计外文翻译.doc

The intelligent public transit system based on Android software design Abstract The intelligent public transit system software can solve urban bus operation information and interaction between users, allows users to timely learn the operation of the bus dynamic, improve user brought to hand over the recognition, in order to solve urban traffic congestion. To software development principle, the function of the software at the same time introduces the characteristics and research content. In the high-tech and information technology rapid development era, information technology is gradually applied to urban infrastructure operation and management. Since the 90 s, the international popular intelligent bus system, the use of advanced electronic technology of urban public transportation system for comprehensive management. In the 21st century, especially after, with the intelligent mobile phone and the development of the android system, based on the android intelligent bus travel system software also appeared, this paper is to introduce the android based on intelligent bus travel system software design. Although intelligent public transit system software is very practical, the market is also very need。But The city scale continuous expansion, make the public transportation systems become more numerous and jumbled. The development of the intelligent public transportation system is one of the most efficient approach to resolve the traffic problems in a metropolis, and automatic bus location system is the foundation of the intelligent public transportation system, it can collect the real-time locations of moving bus on the road, so to develop the technology of bus location plays an important role on constructing the intelligent public transportation system.Nowadays, the bus is still the general public travel main transportation, thus bus information service is becoming more and more important. But with the development of city information construction, and information the popularity of intelligent terminal , make full use of modern communication technology and computer network technology make people travel more convenient and fast will become a development trend. In terms of city bus can completely make use of modern means of communication to build a more humane service means, solve the problems faced by bus travel information. By implementing intelligent bus information navigation system can solve urban bus operation information and interaction between users, allows users to timely learn the operation of the bus dynamic, improve user brought to hand over the

安卓应用开发基础论文中英文对照资料外文翻译文献

中英文对照资料外文翻译文献 安卓应用开发基础 在Java编程语言编写的Android应用程序的Android的SDK工具编译代码以及与任何数据和到一个Android的包，一个归档文件档案资源的.apk后缀，所有的在一个单一的代码.apk文件被认为是一个应用程序，是Android的文件，供电设备来安装应用程序。 一旦安装在设备上，每个Android应用程序的生命在它自己的安全沙箱：而Android操作系统是一个多用户Linux系统中，每个应用程序是一个不同的用户。 默认情况下，每个应用程序的系统分配一个唯一的Linux用户ID（该ID仅用于由系统是未知的应用程序），系统设置所有的应用程序中的文件权限，以便只有用户ID分配给该应用程序可以访问它们。 每个进程都有它自己的虚拟机（VM），因此应用程序的代码在从其他应用程序隔离运行。 默认情况下，每个应用程序运行在它自己的Linux进程。Android的启动过程时，应用程序的任何组件需要被执行，然后关闭该进程时，它不再需要或恢复时，系统必须为其他应用程序的内存。 这样一来，Android系统实现了最小特权原则，也就是说，每个应用程序，默认情况下，只能访问的组件，它需要做的工作，没有更多，这将创建一个非常安全的环境，使应用程序无法访问的，这就是它没有给予许可制度的部分。 但是，有一个应用程序的方法与其他应用程序和应用程序访问系统服务的数据： 这有可能为两个应用程序安排共享相同的Linux用户ID，在这种情况下，它们能够相互访问的文件。为了节约使用相同的用户ID系统资源，应用程序还

可以安排运行在相同的Linux进程和共享同一个VM（应用也必须使用相同的证书签名）。 应用程序可以请求访问权限，如用户的联系人，短信，可安装存储（SD卡），摄像头，蓝牙等设备的数据，所有应用程序的权限必须由用户在安装时授予。 这涵盖了基本就如何Android应用程序在系统中存在这个文件的其余部分向您介绍： 1、框架的核心组件定义应用程序。 2、清单文件中声明组件和应用程序所需的设备功能。 3、资源是从应用程序代码分开，并允许您的应用程序正常优化的设备配置各种其行为。 应用程序组件(Application Components) Android的核心功能之一就是一个应用程序可以使用其它应用程序的元素（如果那个应用程序允许的话）。比如说，如果你的应用程序需要一个图片卷动列表，而另一个应用程序已经开发了一个合用的而又允许别人使用的话，你可以直接调用那个卷动列表来完成工作，而不用自己再开发一个。你的应用程序并没有吸纳或链接其它应用程序的代码，它只是在有需求的时候启动了其它应用程序的那个功能部分。 为达到这个目的，系统必须在一个应用程序的一部分被需要时启动这个应用程序，并将那个部分的Java对象实例化。与在其它系统上的应用程序不同，Android应用程序没有为应用准备一个单独的程序入口（比如说，没有main()方法），而是为系统依照需求实例化提供了基本的组件。共有四种组件类型： 活动(Activities) 一个 activity代表用户界面的一个独立屏幕。例如，一个邮件应用程序应该有一个activity 用于显示新邮件列表，另一个activity 用于撰写一封邮件，还有一个activity 用于读取邮件。尽管所有activitie 协同工作以构成邮件应用程序的用户体验，但彼此之间相对独立。应次，不同的应用程序能够从任何一个

基于Android平台的图书管理系统手机客户端开发(含外文翻译)

基于Android平台的图书管理系统手机客户端开发 基于Android平台的图书管理系统手机客户端开发此文档为WORD格式，下载后可随意编辑 2017年9月修订

摘要 传统WEB应用只能在PC机上使用，不能做到随时随地的使用，为了解决这样的不足，基于Android平台的图书馆管理系统客户端就应运而生。本设计阐述了在Android平台下图书馆管理系统的设计与实现过程，其目的是让人们能够在基于Google Android平台的移动设备上享用传统WEB上图书馆管理系统的基本功能。本系统采用C/S结构，MVC软件开发模式，使用android布局技术完成UI的设计，基于Java语言开发完成，在不同型号的设备模拟器上测试通过。系统实现了用户注册、登录、查询图书以及学生用户管理和图书管理等功能。“操作简单，功能实用”这是本软件设计的核心理念，本系统力求创造最好的用户体验。 关键词：图书馆管理系统；ANDROID；客户端；数据库设计；服务器端

Abstract The WEB application can only in traditional PC use, can't do it at any time and place to use, in order to solve the shortage of such, based on the Android platform of library management system client is made. This paper expounds the workbench Android library management system design and implementation process, and its purpose is to let people can be based on the Google Android platform of mobile devices to enjoy the traditional WEB on the basic functions of the library management system. The system USES the C/S structure, MVC software development model, use android UI design layout complete technology, based on the Java language development completed, in different types of equipment simulator test is passed. The system realizes the user register, login, inquires the books and the students' user management and library management etc. Function. "The operation is simple, functional practical" this is the core idea of the software design, this system is the best tries to create user experience. Key words: library management system; ANDROID; client; database design; server