![Framework Overview ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Android For Java Developers
Similar a Android For Java Developers (20)
Más de Mike Wolfson
Más de Mike Wolfson (20)
Último
Último (20)
Android For Java Developers
- 1. Android for Java Developers
Notas del editor
- http://developer.android.com/guide/basics/what-is-android.html Linux Kernel Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack. Runtime + Dalvik virtual machine VM optimized for mobile devices; Every Android application runs in its own process, with its own instance of the Dalvik virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal memory footprint. The VM is register-based, and runs classes compiled by a Java language compiler that have been transformed into the .dex format by the included "dx" tool. The Dalvik VM relies on the Linux kernel for underlying functionality such as threading and low-level memory management. 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. Each process has its own Java virtual machine (VM), so application code runs in isolation from the code of all other applications. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only that user, only to the application itself — although there are ways to export them to other applications as well. Native Libraries Open GL – custom 2D lib; 3D graphics are based on OpenGL ES 1.0 specification SQLite for structured data storage Integrated browser based on the open source WebKit engine Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) Camera, GPS, compass, and accelerometer (hardware dependent) Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE Application Framework: Activity Manager – Resource Manager – Location Manager – Notification Manager – Content Provider - Applications
- http://developer.android.com/guide/basics/what-is-android.html Linux Kernel Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack.
- http://developer.android.com/guide/basics/what-is-android.html Runtime + Dalvik virtual machine VM optimized for mobile devices; Every Android application runs in its own process, with its own instance of the Dalvik virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik Executable (.dex) - generated by included “dx tool”. .dex format which is optimized for minimal memory footprint. The Dalvik VM relies on the Linux kernel for underlying functionality such as threading and low-level memory management. 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. Each process has its own Java virtual machine (VM), so application code runs in isolation from the code of all other applications. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only that user, only to the application itself — although there are ways to export them to other applications as well.
- Native Libraries Open GL – custom 2D lib; 3D graphics are based on OpenGL ES 1.0 specification SQLite for structured data storage Integrated browser based on the open source WebKit engine Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) Camera, GPS, compass, and accelerometer (hardware dependent) Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE
- Application Framework: A rich and extensible set of Views that can be used to build an application, including lists, grids, text boxes, buttons, and even an embeddable web browser Content Providers that enable applications to access data from other applications (such as Contacts), or to share their own data A Resource Manager , providing access to non-code resources such as localized strings, graphics, and layout files A Notification Manager that enables all applications to display custom alerts in the status bar An Activity Manager that manages the lifecycle of applications and provides a common navigation backstack
- Applications
- http://developer.android.com/guide/basics/what-is-android.html Linux Kernel Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack. Runtime + Dalvik virtual machine VM optimized for mobile devices; Every Android application runs in its own process, with its own instance of the Dalvik virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal memory footprint. The VM is register-based, and runs classes compiled by a Java language compiler that have been transformed into the .dex format by the included "dx" tool. The Dalvik VM relies on the Linux kernel for underlying functionality such as threading and low-level memory management. 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. Each process has its own Java virtual machine (VM), so application code runs in isolation from the code of all other applications. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only that user, only to the application itself — although there are ways to export them to other applications as well. Native Libraries Open GL – custom 2D lib; 3D graphics are based on OpenGL ES 1.0 specification SQLite for structured data storage Integrated browser based on the open source WebKit engine Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) Camera, GPS, compass, and accelerometer (hardware dependent) Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE Application Framework: Activity Manager – Resource Manager – Location Manager – Notification Manager – Content Provider - Applications
- Other Tools: android To create/update Android projects and to create/move/delete AVDs. Android Emulator To run your Android applications on an emulated Android platform. Android Debug Bridge To interface with your emulator or connected device (install apps, shell the device, issue commands, etc.).
- Android (android.bat) – command line tool to allow developer to manage SDK and AVDs Emulator (Mobile device emulator) -- a virtual mobile device that runs on your computer. The emulator lets you prototype, develop, and test Android applications without using a physical device. Each AVD is made up of: A hardware profile. You can set options to define the hardware features of the virtual device. For example, you can define whether the device has a camera, whether it uses a physical QWERTY keyboard or a dialing pad, how much memory it has, and so on. A mapping to a system image. You can define what version of the Android platform will run on the virtual device. You can choose a version of the standard Android platform or the system image packaged with an SDK add-on. Other options. You can specify the emulator skin you want to use with the AVD, which lets you control the screen dimensions, appearance , and so on. You can also specify the emulated SD card to use with the AVD. A dedicated storage area on your development machine, in which is stored the device's user data (installed applications, settings, and so on) and emulated SD card. ADB: Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components: A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients. A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device. A daemon, which runs as a background process on each emulator or device instance. DDMS: Includes: file explorer; Memory/Thread inspector (dumpsys, dumpstate); tools to execute Garbage Collection; Screen capture;
- http://developer.android.com/resources/tutorials/hello-world.html Steps to create a new project. Once you complete the New Project Wizard, ADT creates the following folders and files in your new project: src/ Includes your stub Activity Java file. All other Java files for your application go here. <Android Version> / (e.g., Android 1.1/) Includes the android.jar file that your application will build against. This is determined by the build target that you have chosen in the New Project Wizard . gen/ This contains the Java files generated by ADT, such as your R.java file and interfaces created from AIDL files. assets/ This is empty. You can use it to store raw asset files. See Resources and Assets . res/ A folder for your application resources, such as drawable files, layout files, string values, etc. See Resources and Assets . AndroidManifest.xml The Android Manifest for your project. See The AndroidManifest.xml File . default.properties This file contains project settings, such as the build target. This files is integral to the project, as such, it should be maintained in a Source Revision Control system. It should never be edited manually — to edit project properties, right-click the project folder and select &quot;Properties&quot;.
- Activity – (Noun) A single screen, your application is made up of one or more of these Intent – (Verb) code to perform an action – used to call an activity, service or broadcast receiver; this is the wiring between activities; Intent messaging is a facility for late run-time binding between components in the same or different applications Resource – text, pictures, sound, etc; These things are all abstracted from the code, and compiled into a class called R.class Manifest File – always named AndroidManifest.xml – bundled into .apk file (that contains the applications code, files, and resources), declares the components of an application, describes security permissions required by the app, and lists required library dependancies. Widget – miniature application views that can be embedded in other applications (such as the home screen), and receive periodic updates Service – a task that can be running, but is not visible (background apps FTW!) Broadcast Receiver – a component that does nothing but receive and react to broadcast announcements. These don’t contain a UI, but could be used to start an activity when an event triggers it. Ex. Listed for timezone, or low battery warnings. Security and Permissions - A central design point of the Android security architecture is that no application, by default, has permission to perform any operations that would adversely impact other applications, the operating system, or the user. Android is a multi-process system, in which each application (and parts of the system) runs in its own process. Most security between applications and the system is enforced at the process level through standard Linux facilities, such as user and group IDs that are assigned to applications. Additional finer-grained security features are provided through a &quot;permission&quot; mechanism that enforces restrictions on the specific operations that a particular process can perform, and per-URI permissions for granting ad-hoc access to specific pieces of data. A basic Android application has no permissions associated with it, meaning it can not do anything that would adversely impact the user experience or any data on the device. To make use of protected features of the device, you must include in your AndroidManifest.xml one or more <uses-permission> tags declaring the permissions that your application needs. Content Provider – Functionality designed to allow data to be shared across applications. It is data and an API that any app can access; Android uses this feature to provide contact info; they can be accessed through the android.provider package (some require permissions to access)
- Activity – (Noun) A single screen, your application is made up of one or more of these
- LinearLayout – arranges children in a single row/column. FrameLayout – arranges children so they show up at the top left. Commonly used for Activities with a single element, or tabbed views RelativeLayout – elements are arranges in relation to each other. (Element X is above Y). TableLayout – elements arranged in cells (like HTML tables)
- Intent – (Verb) code to perform an action – used to call an activity, service or broadcast receiver; this is the wiring between activities; Intent messaging is a facility for late run-time binding between components in the same or different applications
- Resource – text, pictures, sound, etc; These things are all abstracted from the code, and compiled into a class called R.class
- Manifest File – always named AndroidManifest.xml – bundled into .apk file (that contains the applications code, files, and resources), declares the components of an application, describes security permissions required by the app, and lists required library dependancies.
- Widget – miniature application views that can be embedded in other applications (such as the home screen), and receive periodic updates Service – a task that can be running, but is not visible (background apps FTW!) Broadcast Receiver – a component that does nothing but receive and react to broadcast announcements. These don’t contain a UI, but could be used to start an activity when an event triggers it. Ex. Listed for timezone, or low battery warnings. Security and Permissions - A central design point of the Android security architecture is that no application, by default, has permission to perform any operations that would adversely impact other applications, the operating system, or the user. Android is a multi-process system, in which each application (and parts of the system) runs in its own process. Most security between applications and the system is enforced at the process level through standard Linux facilities, such as user and group IDs that are assigned to applications. Additional finer-grained security features are provided through a &quot;permission&quot; mechanism that enforces restrictions on the specific operations that a particular process can perform, and per-URI permissions for granting ad-hoc access to specific pieces of data. A basic Android application has no permissions associated with it, meaning it can not do anything that would adversely impact the user experience or any data on the device. To make use of protected features of the device, you must include in your AndroidManifest.xml one or more <uses-permission> tags declaring the permissions that your application needs. Content Provider – Functionality designed to allow data to be shared across applications. It is data and an API that any app can access; Android uses this feature to provide contact info; they can be accessed through the android.provider package (some require permissions to access)