Android Development Tutorial PDF

10/03/12 Andoid Deelopmen Toial
1/53 .ogella.de/aicle/Andoid/aicle.hml
T
2.7k
www.smartsheet.com
Ads b Google
A D T
Baed on Andoid 4.0
L V
Version 10.0
Copyright 2009, 2010, 2011, 2012 Lars Vogel
06.03.2012
Revision Histor
Revision 0.1 04.07.2009
Created
Revision 0.2 - 10.0 07.07.2009 - 06.03.2012
bug fixing and enhancements
D A G E
This tutorial describes how to create Android applications with Eclipse. It is based on Eclipse 3.7 (Indigo), Java 1.6
and Android 4.0 (Ice Cream Sandwich).
T C
1. What is Android?
1.1. Android Operation System
1.2. Google Play
1.3. Security and permissions
2. Android components
2.1. Activity
2.2. Views and ViewGroups
2.3. Intents
2.4. Services
2.5. ContentProvider
2.6. BroadcastReceiver
2.7. (HomeScreen) Widgets
2.8. Other
3. Android Development Tools
3.1. What are the Android Development Tools?
3.2. Dalvik Virtual Machine
3.3. How to develop Android Applications
4. Android Application Architecture
4.1. AndroidManifest.xml
4.2. R.java and Resources
4.3. Assets
4.4. Activities and Layouts
4.5. Reference to resources in XML files
4.6. Activities and Lifecycle
4.7. Configuration Change
4.8. Context
5. Installation
5.1. Eclipse
5.2. Pre-requisites for using a 64bit Linux
5.3. Install ADT Plug-ins and Android SDK
5.4. Manually install Android SDK
5.5. Install a specific Android version
5.6. Android Source Code
6. Android virtual device - Emulator
6.1. What is the Android Emulator?
6.2. Google vrs. Android AVD
6.3. Emulator Shortcuts
6.4. Performance
6.5. Hardware button
7. Tutorial: Create and run Android Virtual Device
8. Error handling and typical problems
8.1. Clean Project
8.2. Problems with Android Debug Bridge (adb)
8.3. LogCat
8.4. Emulator does not start
8.5. Timeout during deployment
8.6. Install failed due to insufficient storage
8.7. Debug Certificate expired
8.8. Error message for @override
8.9. Missing Imports
8.10. Eclipse Tips
9. Conventions for the tutorials
9.1. API version, package and application name
9.2. Warnings Messages for Strings
9.3. Android Exercises and Tutorials
10. Your first Android project
10.1. Create Project
10.2. Two faces of things
10.3. Create attributes
10.4. Add UI Elements
10.5. Edit UI properties
10.6. Code your application
10.7. Start Project
11. Starting an deployed application
12. Menus and Action Bar
12.1. Definition of menu entries
12.2. Action bar tabs
12.3. Context menus
13. Tutorial: Menus and Action Bar
13.1. Project
13.2. Add a menu XML resource
14. Preferences
15. Tutorial: Preferences
15.1. Using preferences
15.2. Run
16. Layout Manager and ViewGroups
16.1. Available Layout Manager
16.2. LinearLayout
16.3. RelativeLayout
16.4. Gridlayout
16.5. ScrollView
17. Tutorial: ScrollView
18. Styling
18.1. Overview
18.2. Example
19. Supporting different screen sizes
19.1. Using device independent pixel
19.2. Using resource qualifiers
20. Fragments
20.1. Overview
20.2. When to use Fragments
21. Fragments Tutorial
21.1. Overview
21.2. Create project
21.3. Create layouts for portrait mode
21.4. Create Fragment classes
21.5. Create layouts for landscape mode
21.6. Activities
21.7. Run
22. DDMS perspective and important views
22.1. DDMS - Dalvik Debug Monitor Server
22.2. LogCat View
22.3. File explorer
23. Shell
23.1. Android Debugging Bridge - Shell
23.2. Uninstall an application via adb
23.3. Emulator Console via telnet
24. Deploy your application on a real device
25. Thank you
26. Questions and Discussion
27. Links and Literature
27.1. Source Code
27.2. Android Resources
27.3. vogella Resources
1. W A?
1.1. A O S
Android is an operating system based on Linux with a Java programming interface.
The Android Software Development Kit (Android SDK) provides all necessary tools to develop Android applications.
This includes a compiler, debugger and a device emulator, as well as its own virtual machine to run Android
programs.
Android is currently primarily developed by Google.
Android allows background processing, provides a rich user interface library, supports 2-D and 3-D graphics using
the OpenGL libraries, access to the file system and provides an embedded SQLite database.
Android applications consist of different components and can re-use components of other applications, if these
applications declare their components as available. This leads to the concept of a task in Android; an application
can re-use other Android components to archive a task.
For example you can write an application which integrates a map component and a camera component to archive a
certain task.
1.2. G P
Google offers the "Google Play" service. Google hosts Android applications and the Google Play application allows
to install new Android application on an Android device. Google Play used to be called "Android Market".
1.3. S
During deployment on an Android device, the Android system will create a unique user and group ID for every
Android application. Each application file is private to this generated user, e.g. other applications cannot access
these files.
In addition each Android application will be started in its own process.
Therefore by means of the underlying Linux operating system, every Android application is isolated from other
running applications. A misbehaving application cannot easily harm other Android applications.
If data should be shared, the application must do this explicitly, e.g. via a Seice or a ConenPoide
Android also contains a permission system. Android predefines permissions for certain tasks but every application
can also define its own permissions.
An application must declare in its configuration file (AndroidManifest.xml) that it requires certain permissions.
Depending on the details of the required permission, the Android system will either automatically grant the
permission, reject it or ask the user if he grants this permission to the application during installation.
If for example the application declares that it requires Internet access, the user needs to confirm the usage of this
permission during installation.
This is called "user driven security". The user decides to grant a permission or to deny it. If the user denies a
permission required by the application, this application cannot be installed. The check of the permission is only
performed during installation, permissions cannot be denied or granted after the installation.
Typically not all users check the permissions in detail but some users do. If there is seems to be something
in connection with them, they will write bad reviews on Google Play.
2. A
The following gives a short overview of the most important Android components.
2.1. A
Acii represents the presentation layer of an Android application. A simplified (and slightly incorrect)
description is that an Acii is a screen. This is slightly incorrect as Aciiie can be displayed as Dialogs
or can be transparent. An Android application can have several Aciiie.
2.2. V VG
Vie are user interface widgets, e.g. buttons or text fields. The base class for all Vie is
andoid.ie.Vie. Vie often have attributes which can be used to change their appearance and
A VieGop is responsible for arranging other Vie e.g. a VieGop is a layout manager. The base class
for a layout manager is andoid.ie.VieGop. VieGop also extends Vie. VieGop
nestled to create complex layouts. You should not nestle VieGop too deeply as this has a negative
the performance.
2.3. I
Inen are asynchronous messages which allow the application to request functionality from other components of
the Android system, e.g. from Seice or Aciiie. An application can call a component directly (explicit
Inen ) or ask the Android system to evaluate registered components for a certain Inen (implicit
For example the application could implement sharing of data via an Inen and all components which allow sharing
of data would be available for the user to select. Applications register themselves to an Inen via an
InenFile.
Inen allow to combine loosely coupled components to perform certain tasks.
2.4. S
Seice perform background tasks without providing a user interface. They can notify the user via the notification
framework in Android.
2.5. CP
ConenPoide provides a structured interface to application data. Via a ConenPoide your
application can share data with other applications. Android contains an SQLite database which is frequently used in
conjunction with a ConenPoide to persist the data of the ConenPoide.
2.6. BR
BoadcaReceie can be registered to receive system messages and Inen. A BoadcaReceie
will get notified by the Android system, if the specified situation happens. For example a BoadcaReceie
could get called once the Android system completed the boot process or if a phone call is received.
2.7. (HS) W
Widge are interactive components which are primarily used on the Android homescreen. They typically display
some kind of data and allow the user to perform actions via them. For example a Widge could display
summary of new emails and if the user selects an email, it could start the email application with the selected email.
2.8. O
Android provide many more components but the list above describes the most important ones. Other Android
components are "Live Folders" and "Live Wallpapers". Live Folders display data on the homescreen without
launching the corresponding application.
3. A D T
3.1. W A D T?
Google provides the Android Development Tools (ADT) to develop Android applications with Eclipse. ADT is a set
of components (plug-ins) which extend the Eclipse IDE with Android development capabilities.
ADT contains all required functionalities to create, compile, debug and deploy Android applications from the Eclipse
IDE and from the command line. Other IDE's, e.g. IntellJ, are also reusing components of ADT.
ADT also provides an Android device emulator, so that Android applications can be tested without a real Android
phone.
3.2. D V M
The Android system uses a special virtual machine, i.e. the Dalvik Virtual Machine to run Java based applications.
Dalvik uses an own bytecode format which is different from Java bytecode.
Therefore you cannot directly run Java class files on Android, they need to get converted in the Dalvik bytecode
format.
3.3. H A A
Android applications are primarily written in the Java programming language. The Java source files are converted to
Java class files by the Java compiler.
Android provides a tool called "dx"" which converts Java class files into a de (Dalvik Executable) file. All class files
of one application are placed in one compressed .dex file. During this conversion process redundant information in
the class files are optimized in the .dex file. For example if the same String is found in different class files,
file contains only once reference of this String.
These dex files are therefore much smaller in size than the corresponding class files.
The .dex file and the resources of an Android project, e.g. the images and XML files, are packed into an
(Android Package) file. The program aap (Android Asset Packaging Tool) performs this packaging.
The resulting .apk file contains all necessary data to run the Android application and can be deployed to an Android
device via the "adb" tool.
The Android Development Tools (ADT) allows that all these steps are performed transparently to the user; either
within Eclipse or via the command line.
If you use the ADT tooling you press a button or run a script and the whole Android application (.apk file) will be
created and deployed.
4. A A A
4.1. AM.
The components and settings of an Android application are described in the file AndoidManife.ml
example all Aciiie and Seice 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.

<?xm1 ves1on="1.0" encod1ng="uff-"?>
<man1fesf xm1ns:ando1d="hffp://schemas.ando1d.com/apk/es/ando1d"
package="de.voge11a.ando1d.fempeafue"
ando1d:ves1onCode="1"
ando1d:ves1onName="1.0">
<app11caf1on ando1d:1con="0daWab1e/1con" ando1d:1abe1="0sf1ng/appname">
<acf1v1fy ando1d:name=".Convef"
ando1d:1abe1="0sf1ng/appname">
<1nfenf-f11fe>
<acf1on ando1d:name="ando1d.1nfenf.acf1on.MAlN" />
<cafegoy ando1d:name="ando1d.1nfenf.cafegoy.LAuNChLk" />
</1nfenf-f11fe>
</acf1v1fy>
</app11caf1on>
<uses-sdk ando1d:m1n5dkves1on="9" />
</man1fesf>

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 full qualified package name.
Google Play requires that every Android application uses its own unique package. Therefore it is a good habit to
your reverse domain name as package name. This will avoid collisions with other Android applications.
andoid:eionName and andoid:eionCode specify the version of your application. eionName
is what the user sees and can be any String.
eionCode must be an integer. The Android Market determine based on the eionCode, if it should
perform an update of the applications for the existing installations. You typically start with "1" and increase this value
by one, if you roll-out a new version of your application.
The tag <acii> defines an Acii, in this example pointing to the Cone class in the
de.ogella.andoid.empeae package. An intent filter is registered for this class which defines
this Acii is started once the application starts (action
andoid:name="andoid.inen.acion.MAIN" ). The category definition caego
andoid:name="andoid.inen.caego.LAUNCHER" defines that this application is added to the
application directory on the Android device.
The @ing/app_name value refers to resource files which contain the actual value of the application name. The
usage of resource file makes it easy to provide different resources, e.g. strings, colors, icons, for different devices
and makes it easy to translate applications.
The "uses-sdk" part of the "AndroidManifest.xml" file defines the minimal SDK version for which your application is
valid. This will prevent your application being installed on devices with older SDK versions.
4.2. R. R
The " gen " directory in an Android project contains generated values. R.jaa is a generated class which contains
references to certain resources of the project.
These resources must be defined in the "res" directory and can be XML files, icons or pictures. You can for example
define values, menus, layouts or animations via XML files.
If you create a new resource, the corresponding reference is automatically created in R.jaa via the Eclipse ADT
tools. These references are static int values and define ID's for the resources.
The Android system provides methods to access the corresponding resource via these ID's.
For example to access a String with the R.ing.oSing ID, you would use the
geSing(R.ing.oSing)) method.
R.java is automatically created by the Eclipse development environment, manual changes are not necessary and will
be overridden by the tooling.
4.3. A
While the e directory contains structured values which are known to the Android platform, the ae
can be used to store any kind of data. In Java you access this data via the AeManage and the
geAe() method .
4.4. A L
The user interface for Aciiie is defined via layouts. The layout defines the included Vie (widgets) and
their properties.
A layout can be defined via Java code or via XML. In most cases the layout is defined as an XML file.
XML based layouts are defined via a resource file in the /e/lao folder. This file specifies the
VieGop, Vie, their relationship and their attributes for this specific layout.
If a Vie needs to be accessed via Java code, you have to give the Vie a unique ID via the andoid:id
attribute. To assign a new ID to a Vie use @+id/oale. The following shows an example in which a
Bon gets the "button1" ID assigned.

<8uffon
ando1d:1d="0+1d/buffon1"
ando1d:1ayoufW1dfh="Wapconfenf"
ando1d:1ayoufhe1ghf="Wapconfenf"
ando1d:fexf="5hoW Pefeences" >
</8uffon>

By conversion this will create and assign a new oale ID to the corresponding Vie. In your Java code you
can later access a Vie via the method findVieBId(R.id.oale).
Defining layouts via XML is usually the preferred way as this separates the programming logic from the layout
definition. It also allows the definition of different layouts for different devices. You can also mix both approaches.
4.5. R XML
In your XML files, for example your layout files, you can refer to other resources via the @ sign.
For example, if you want to refer to a color which is defined in a XML resource, you can refer to it via
@colo/o_id. Or if you defined a "hello" string in an XML resource, you could access it via
@ing/hello.
4.6. A L
The Android system controls the lifecycle of your application. At any time the Android system may stop or destroy
your application, e.g. because of an incoming call. The Android system defines a lifecycle for Aciiie
predefined methods. The most important methods are:
onSaeInanceSae() - called if the Acii is stopped. Used to save data so that the
can restore its states if re-started
onPae() - always called if the Acii ends, can be used to release resource or save data
onReme() - called if the Acii is re-started, can be used to initialize fields
4.7. C C
An Acii will also be restarted, if a so called "configuration change" happens. A configuration change happens
if an event is triggered which may be relevant for the application. For example if the user changes the orientation of
the device (vertically or horizontally). Android assumes that an Acii might want to use different resources for
these orientations and restarts the Acii.
In the emulator you can simulate the change of the orientation via CNTR+F11.
You can avoid a restart of your application for certain configuration changes via the configChange attribute on
your Acii definition in your AndoidManife.ml. The following Acii will not be restarted in case
of orientation changes or position of the physical keyboard (hidden / visible).

<acf1v1fy ando1d:name=".Pogess1esfAcf1v1fy"
ando1d:1abe1="0sf1ng/appname"
ando1d:conf1gChanges="o1enfaf1on|keyboadh1dden|keyboad">
</acf1v1fy>

4.8. C
The class andoid.conen.Cone provides the connections to the Android system. It is the interface to
global information about the application environment. Cone also provides access to Android Seice
the Location Service. Aciiie and Seice extend the Cone class and can therefore be used
Cone.
5. I
5.1. E
The following assume that you have already Java and Eclipse installed and know how to use Eclipse. For an
introduction into Eclipse please see the following tutorial: Eclipse IDE Tutorial.
The tutorial above also describes how to install new components into Eclipse. This is required to install the Android
Development Tools. You find the necessary steps described in the following section of the tutorial: Eclipse Update
Manager.
The author of this text has also published a Kindle book on the usage of the Eclipse IDE, which can be found here:
Eclipse IDE Book for Kindle.
5.2. P- 64 L
The Android SDK is 32bit, therefore on an 64bit Linux system you need to have the package ia32-lib
For Ubuntu you can do this via the following command.

apf-gef 1nsfa11 1a32-11bs

Please check your distribution documentation, if you are using a different flavor of Linux.
5.3. I ADT P- A SDK
Use the Eclipse update manager to install all available components for the Android Development Tools
the URL https://dl-ssl.google.com/android/eclipse/.
After the new Android development components are installed, you will be prompted to install the Android SDK. You
can use the following wizard or go to the next section to learn how to do it manually.
5.4. M A SDK
After the installation of the ADT the Eclipse tooling allows to download the Android SDK automatically. Alternatively
you can also manually download the Android SDK from the Android SDK download page.
The download contains a zip file, which you can extract to any place in your file system, e.g. on my Linux system I
placed it under "/home/vogella/android-sdks". Avoid using spaces in the path name, otherwise you may experience
problems with the usage of the Android SDK.
You also have to define the location of the Android SDK in the Eclipse Preferences. In Eclipse open the Preferences
dialog via the menu Windows Preferences. Select Android and enter the installation path of the Android SDK.
5.5. I A
The Android SDK Manager allows you to install specific versions of Android. Select Window Android SDK
Manager from the Eclipse menu.
The dialog allows you to install new packages and also allows you to delete them.
Select "Available packages" and open the "Third Party Add-ons". Select the Google API 15 (Android 4.0.3) version
of the SDK and press "Install".
Press the "Install" button and confirm the license for all packages. After the installation completes, restart Eclipse.
5.6. A S C
The following step is optional.
5.6.1. A A 4.0
During Android development it is very useful to have the Android source code available.
As of Android 4.0 the Android development tools provides also the source code. You can download it via the
Android SDK Manager by selecting the "Sources for Android SDK".
The sources are downloaded to the source directory located in "path_to_android_sdk/sources/android-xx". xx is the
API level of Android, e.g. 15 for the Android 4.0.3 version.
To connect the sources with the android.jar file in your Android project, right click on your android.jar in the Eclipse
Package Explorer and select Properties Java Source Attachment. Type in the source directory name and press
OK.
Afterwards you can browse through the source code.
5.6.2. P A 4.0
For earlier versions Haris Peco maintains plugins, which provide the Android Source code code. Use the Eclipse
update manager to install the Android Source plugin from the following update site: "http://adt-
addons.googlecode.com/svn/trunk/source/com.android.ide.eclipse.source.update".
More details can be found on the project website.
6. A - E
6.1. W A E?
The Android Development Tools (ADT) include an emulator to run an Android system. The emulator behaves
real Android device (in most cases) and allows you to test your application without having a real device.
You can configure the version of the Android system you would like to run, the size of the SD card, the screen
resolution and other relevant settings. You can define several devices with different configurations.
These devices are called "Android Virtual Device" (AVD) and you can start several in parallel. Starting a new
emulator is very slow, due to some initial setup.
The ADT allow to deploy and run your Android program on the AVD.
6.2. G . A AVD
During the creation of an AVD you decide if you want an Android device or an Google device.
An AVD created for Android will contain the programs from the Android Open Source Project. An AVD created for
the Google API's will also contain several Google applications, most notable the Google Maps application.
If you want to use functionality which is only provided via the Google API's, e.g. Cloud2DeviceMessaging or Google
Maps you must run this application on an AVD with Google API's.
6.3. E S
The following shortcuts are useful for working with the emulator.
A+E Maximizes the emulator. Nice for demos.
C+F11 changes the orientation of the emulator.
F8 Turns network on / off.
6.4. P
The graphics of the emulator are rendered in software, which is very slow. To have a responsive emulator use a
small resolution for your emulator, as for example HVGA.
Also if you have sufficient memory on your computer, add at least 1 GB of memory to your emulator. This is the value
"Device ram size" during the creation of the AVD.
Also set the flag "Enabled" for Snapshots. This will save the state of the emulator and let it start much faster.
6.5. H
Android 4.0 introduced that devices do not have to have hardware button anymore. If you want to create such an
AVD, add the "Hardware Back/Home keys" property to the device configuration and set it to "false".
7. T: C A V D
To define an Android Virtual Device (ADV) open the "AVD Manager" via Windows AVD Manager and
"New".
Enter the following.
We can also select the box "Enabled" for Snapshots. This will make the second start of the virtual device much
faster.
At the end press the button "Create AVD". This will create the AVD configuration and display it under the "Virtual
devices".
To test if your setup is correct, select your device and press "Start".
After (a long time) your AVD starts. You are able to use it via the mouse and via the virtual keyboard of the emulator.
8. E
Things are not always working as they should. This section gives an overview over typical problems and how to solve
them.
8.1. C P
Several users report that get the following errors:
1. Project ... is missing required source folder: 'gen'
2. The project could not be built until build path errors are resolved.
3. Unable to open class file R.java.
To solve any of these errors, go to the project menu and select Project Clean.
8.2. P A D B ()
The communication with the emulator or your Android device might have problems. This communication is handled
by the Android Debug Bridge (adb).
Eclipse allows to reset the adb in case this causes problems. Select therefore the DDMS perspective via
Open Perspective Other DDMS
To restart the adb, select the "Reset adb" in the Device Vie.
8.3. LC
The "LogCat" Vie shows you the log messages of your Android device and help you analyze problems. For
example Java exceptions in your program would be shown here. To open this view, select Window Show View
Other Android LogCat.
8.4. E
If your emulator does not start, make sure that the android-sdk version is in a path without any spaces in the path
name.
8.5. T
If you face timeout issues during deployment you can increase the default timeout in the Eclipse preferences. Select
Window Preferences Android DDMS and increase the "ADB connection timeout (in ms)" value.
8.6. I
Sometimes the emulator will refuse to install an application with the error message:
INSTALL_FAILED_INSUFFICIENT_STORAGE.
An Android virtual device provides per default only 64M for internal storage of application. You can clean your
installed application by re-starting the emulator and selecting the "Wipe user data" flag.
Alternative you can set the the data partition size, if you press edit on the AVD you can set the "Ideal size of data
partition" property via the "New" button.
8.7. D C
If you get the error message "Debug Certificate expired" switch to the folder which contains the Android AVD, e.g.
".android" under Linux and delete the "debug.keystore" file. This file is only valid for a year and if not present Eclipse
will regenerate the password.
8.8. E @
The @override annotation was introduced in Java 1.6. If you receive an error message for @oeide
Java compiler level to Java 1.6. To do this right-click on the project, select Properties Java Compiler
compliance level and select "1.6" in the drop-down box.
8.9. M I
Java requires that classes which are not part of the standard Java Language be either fully qualified or declared via
imports.
If you see error message with "XX cannot be resolved to a variable", right-click in your Edio and select
Organize Imports to important required packages.
8.10. E T
To work more efficiently with Eclipse, select Window Preferences Java Editor Save Actions
that the source code should be formatted and that the imports should be organized at every save.
9. C
9.1. API ,
The tutorials of this document have been developed and tested with Android 4.0.3, API Level 15. Please use this
version for all tutorials in this book. Higher version usually should also work. Lower version of the Android API might
also work, but if you face issues, try the recommended version.
The base package for the projects is always the same as the project name, e.g. if you are asked to create a project
"de.vogella.android.example.test" then the corresponding package name is "de.vogella.android.example.test".
The Application name, which must be entered on the Android project generation wizard, will not be predefined.
Choose a name you like.
9.2. W M S
The Android development tools are show warnings if you use hard-coded strings, for example in layout files. While
for real application its best practice to use string resource files we use use Strings directly to simplify the creation of
the examples.
9.3. A E T
You find different types of exercises. Some exercises explain every mouse click you have to do, others just give you
the task to do. Most exercises try to give you a base example and ask you to extend this example.
10. Y A
10.1. C P
This app is also available on the Android Marketplace. Search for "vogella" for find this example.
Select File New Other Android Android Project and create the Android project
"de.vogella.android.temperature". Enter the following.
Press "Finish". This should create the following directory structure.
While "res" contains structured values which are known to the Android platform the directory "assets" can be used to
store any kind of data. In Java you can access this data via the AssetsManager and the method getAssets().
10.2. T
The Android SDK allows the developer to define certain artifacts, e.g. strings and UI's, in two ways: via a rich editor,
and directly via XML.
The following description tries to use the rich UI but for validation the resulting XML is also displayed. You can switch
between both things by clicking on the tab on the lower part of the screen. For example in the Package Explorer
select "res/layout/main.xml".
10.3. C
Android allows you to create attributes for resources, e.g. for strings or colors. These attributes can be used in your
UI definition via XML or in your Java source code.
Select the file "res/values/string.xml" and press "Add". Select "Color" and enter "myColor" as the name and
"#3399CC" as the value.
Add also the following "String" attributes. String attributes allow the developer to translate the application at a later
point.
T 1. S A
N V
celsius to Celsius
fahrenheit to Fahrenheit
calc Calculate
Switch to the XML representation and validate the values.

<esouces>
<sf1ng name="he11o">he11o Wo1d, Convef!</sf1ng>
<sf1ng name="appname">1empeafue Convefe</sf1ng>
<co1o name="myCo1o">#3399CC</co1o>
<sf1ng name="myC11ckhand1e">myC11ckhand1e</sf1ng>
<sf1ng name="ce1s1us">fo Ce1s1us</sf1ng>
<sf1ng name="fahenhe1f">fo Iahenhe1f</sf1ng>
<sf1ng name="ca1c">Ca1cu1afe</sf1ng>
</esouces>

10.4. A UI E
Select "res/layout/main.xml" and open the Android editor via a double-click. This editor allows you to create the UI via
drag and drop or via the XML source code. You can switch between both representations via the tabs at the bottom
of the editor. For changing the position and grouping elements you can use the outline view.
The following shows a screenshot of the Palette view from which you can drag and drop new UI elements into your
layout. Please note that the "Palette" view changes frequently so your view might be a bit different.
Right-click on the text object Hello World, Hello! in the layout. Select Delete on the popup menu to remove the text
object. Then, from the Palette view, select Text Fields and locate Plain Text. Drag this onto the layout to create a
text input field. All object types in the section "Text Fields derive from the class "EditText", they just specify via an
additional attribute which text type can be used.
Now select the Palette section Form Widgets and drag a RadioGroup object onto the layout. The number of radio
buttons added to the radio button group depends on your version of Eclipse. Make sure there are two radio buttons
by deleting or adding radio buttons to the group.
From the Palette section Form Widgets, drag a Button object onto the layout.
The result should look like the following.
Switch to "main.xml" and verify that your XML looks like the following.

<L1neaLayouf xm1ns:ando1d="hffp://schemas.ando1d.com/apk/es/ando1d"
ando1d:o1enfaf1on="vef1ca1" ando1d:1ayoufW1dfh="f111paenf"
ando1d:1ayoufhe1ghf="f111paenf">
<Ld1f1exf ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:1d="0+1d/ed1f1exf1"
ando1d:1ayoufW1dfh="mafchpaenf" ando1d:fexf="Ld1f1exf"></Ld1f1exf>
<kad1oGoup ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:1d="0+1d/ad1oGoup1"
ando1d:1ayoufW1dfh="mafchpaenf">
<kad1o8uffon ando1d:fexf="kad1o8uffon"
ando1d:1ayoufW1dfh="Wapconfenf" ando1d:1d="0+1d/ad1o0"
ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:checked="fue"></kad1o8uffon>
<kad1o8uffon ando1d:fexf="kad1o8uffon"
ando1d:1ayoufW1dfh="Wapconfenf" ando1d:1d="0+1d/ad1o1"
ando1d:1ayoufhe1ghf="Wapconfenf"></kad1o8uffon>
</kad1oGoup>
<8uffon ando1d:fexf="8uffon" ando1d:1d="0+1d/buffon1"
ando1d:1ayoufW1dfh="Wapconfenf" ando1d:1ayoufhe1ghf="Wapconfenf"
</L1neaLayouf>

10.5. E UI
If you select a UI element you can change its properties via the properties view. Most of the properties can be
changed via the right mouse menu. You can also edit properties of fields directy in XML. Typically you change
properties directly in the XML file as this is much faster. But the right mouse functionality is nice if you are
for a certain property.
Open your file "main.xml" We will delete the initial text for the EditText field in XML. Switch to the XML tab called
"main.xml" and delete the andoid:e="EdiTe" property from the EditText part. Switch back to the
"Graphical Layout" tab and check that the text is removed.
Use the right mouse click on the first radio button to assign the "celsius" string attribute to its "text" property. Assign
the and "fahrenheit" string attribute to the second radio button.
From now on I assume you are able to use the properties menu on the UI elements. You can either edit the XML file
or modify the properties via right mouse click.
Set the property "Checked" to true for the first RadioButton. Assign "calc" to the text property of your button and
assign "myClickHandler" to the "onClick" property. Set the "Input type" property to "numberSigned" and
"numberDecimal" on your EditText.
All your other UI controls are contained in a LinearLayout. We want to assign a background color to this
LinearLayout. Right-click on an empty space in Graphical Layout mode, then select Other Properties
Background. Select Color and then myColor in the list.
Switch to the "main.xml" tab and verify that the XML is correctly maintained.

ando1d:o1enfaf1on="vef1ca1" ando1d:1ayoufW1dfh="f111paenf"
ando1d:1ayoufhe1ghf="f111paenf" ando1d:backgound="0co1o/myCo1o">
<Ld1f1exf ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:1d="0+1d/ed1f1exf1"
ando1d:1ayoufW1dfh="mafchpaenf" ando1d:1npuf1ype="numbeDec1ma1|numbe51gned"
></Ld1f1exf>
<kad1oGoup ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:1d="0+1d/ad1oGoup1"
ando1d:1ayoufW1dfh="mafchpaenf">
<kad1o8uffon ando1d:1ayoufW1dfh="Wapconfenf"
ando1d:1d="0+1d/ad1o0" ando1d:1ayoufhe1ghf="Wapconfenf"
ando1d:fexf="0sf1ng/ce1s1us" ando1d:checked="fue"></kad1o8uffon>
<kad1o8uffon ando1d:1ayoufW1dfh="Wapconfenf"
ando1d:1d="0+1d/ad1o1" ando1d:1ayoufhe1ghf="Wapconfenf"
ando1d:fexf="0sf1ng/fahenhe1f"></kad1o8uffon>
</kad1oGoup>
<8uffon ando1d:1d="0+1d/buffon1" ando1d:1ayoufW1dfh="Wapconfenf"
ando1d:1ayoufhe1ghf="Wapconfenf" ando1d:fexf="0sf1ng/ca1c"
ando1d:onC11ck="myC11ckhand1e"></8uffon>
</L1neaLayouf>

10.6. C
During the generation of your new Android project you specified that an Acii called ConeAcii
should get created. The project wizard also created the corresponding Java classs.
Change your code in ConeAcii.jaa to the following. Note that the mClickHandle will be called
based on the OnClick property of your button.

package de.voge11a.ando1d.fempeafue
1mpof ando1d.app.Acf1v1fy
1mpof ando1d.os.8und1e
1mpof ando1d.v1eW.v1eW
1mpof ando1d.W1dgef.Ld1f1exf
1mpof ando1d.W1dgef.kad1o8uffon
1mpof ando1d.W1dgef.1oasf
pub11c c1ass ConvefAcf1v1fy exfends Acf1v1fy {
p1vafe Ld1f1exf fexf
0Ove1de
pub11c vo1d onCeafe{8und1e savedlnsfance5fafe} {
supe.onCeafe{savedlnsfance5fafe}
sefConfenfv1eW{k.1ayouf.ma1n}
fexf = {Ld1f1exf} f1ndv1eW8yld{k.1d.ed1f1exf1}
}
// 1h1s mefhod 1s ca11ed af buffon c11ck because We ass1gned fhe name fo fhe
// "On C11ck popefy" of fhe buffon
pub11c vo1d myC11ckhand1e{v1eW v1eW} {
sW1fch {v1eW.gefld{}} {
case k.1d.buffon1:
kad1o8uffon ce1s1us8uffon = {kad1o8uffon} f1ndv1eW8yld{k.1d.ad1o0}
kad1o8uffon fahenhe1f8uffon = {kad1o8uffon} f1ndv1eW8yld{k.1d.ad1o1}
1f {fexf.gef1exf{}.1engfh{} == 0} {
1oasf.make1exf{fh1s, "P1ease enfe a va11d numbe",
1oasf.LLNG1hLONG}.shoW{}
efun
}
f1oaf 1npufva1ue = I1oaf.paseI1oaf{fexf.gef1exf{}.fo5f1ng{}}
1f {ce1s1us8uffon.1sChecked{}} {
fexf.sef1exf{5f1ng
.va1ueOf{convefIahenhe1f1oCe1s1us{1npufva1ue}}}
ce1s1us8uffon.sefChecked{fa1se}
fahenhe1f8uffon.sefChecked{fue}
} e1se {
fexf.sef1exf{5f1ng
.va1ueOf{convefCe1s1us1oIahenhe1f{1npufva1ue}}}
fahenhe1f8uffon.sefChecked{fa1se}
ce1s1us8uffon.sefChecked{fue}
}
beak
}
}
// Convefs fo ce1s1us
p1vafe f1oaf convefIahenhe1f1oCe1s1us{f1oaf fahenhe1f} {
efun {{fahenhe1f - 32} " 5 / 9}
}
// Convefs fo fahenhe1f
p1vafe f1oaf convefCe1s1us1oIahenhe1f{f1oaf ce1s1us} {
efun {{ce1s1us " 9} / 5} + 32
}
}

10.7. S P
To start the Android Application, select your project, right click on it, and select Run-As Android Application
patient, the emulator starts up very slowly.
You should get the following result.
Type in a number, select your conversion and press the button. The result should be displayed and the other option
should get selected.
11. S
After you run your application on the virtual device you can start it again on the device. If you press the Home button
you can also select your application.
12. M A B
12.1. D
Android provides two possible ways to display global actions which the user can select. The first one is the usage of
the Action Bar in the application. The Action Bar is a window feature at the top of the activity that may display the
activity title, navigation modes, and other interactive items.
The second option is that the app can open a menu which shows additional actions via a popup menu. Typically you
define your menu entries in a way that they are added to the action bar if sufficient space is available in the action
bar and if not, remaining menu items are displayed in the popup menu.
The option menu and the action bar of your activity is filled by the method onCreateOptionsMenu() of your
The AcionBa also shows an icon of your application. You can also add an action to this icon. If you select this
icon the onOpionIemSeleced() method will be called with the value andoid.R.id.home. The
recommendation is to return to the main Acii in your program.

// lf home 1con 1s c11cked efun fo ma1n Acf1v1fy
case ando1d.k.1d.home:
lnfenf 1nfenf = neW lnfenf{fh1s, Ovev1eWAcf1v1fy.c1ass}
1nfenf.addI1ags{lnfenf.ILAGAC1lvl1YCLLAk1OP}
sfafAcf1v1fy{1nfenf}
beak

In this method you can create the menu programmatically or you can use a pre-defined XML resources which you
inflate via the MenInflao class. Each Acii has already an instance of the class available and this
instance can get accessed via the geMenInflao() method.
The onCeaeOpionMen() method is only called once. If you want to influence the menu later you have to use
the onPepaeOpionMen() method.
12.2. A
It is also possible to add tabs to an action bar.
12.3. C
You can also assign a context menu to an UI widget (view). A context menu is activated if the user "long
view.
A context menu for a view is registered via the egieFoConeMen(ie) method. The
onCeaeConeMen() method is called every time a context menu is activated as the context menu is
discarded after its usage. The Android platform may also add options to your Vie, e.g. EdiTe provides
context options to select text, etc.
13. T: M A B
13.1. P
This chapter will demonstrate how to create and evaluate a option menu which is displayed in the action bar if
sufficient space is available. This example will be extended in the chapter about preferences.
Create a project called "de.vogella.android.socialapp" with the Acii called "OverviewActivity". Change the
"main.xml" layout file in the diretory "/res/layout/" to the following:

ando1d:1ayoufW1dfh="f111paenf"
ando1d:1ayoufhe1ghf="f111paenf"
ando1d:o1enfaf1on="vef1ca1" >
<8uffon
ando1d:1d="0+1d/8uffon01"
ando1d:fexf="5hoW Pefeences" >
</8uffon>
<8uffon
ando1d:fexf="Change Pefeences" >
</8uffon>
</L1neaLayouf>

13.2. A XML
Select your project, right click on it and select New Other Android Android XML File to create a new XML
resource.
Select the option "Menu", enter as File "mainmenu.xml" and press the button "Finish".
This will create a new file "mainmenu.xml" in the folder "res/menu" of your project. Android provides a nice editor to
edit this file, unfortunately this editor is not always automatically used due to bugs in the ADT. If that happens, you can
open this editor manually. Right-click on your menu file and select Open with Android Menu Editor.
Switch if necessary to the "Layout" tab of the editor. Press Add and select "Item". Maintain the following value. This
defines the entries in your menu. We will also define that the menu entry is displayed in the action bar if there is
sufficient space available.
Change your Activity class "OverviewActivity" to the following. The OnCreateOptionsMenu method is used to create
the menu. The behavior in "onOptionsItemSelected" is currently hard-coded to show a Toast and will soon call the
preference settings. In case you want to disable or hide menu items you can use the method
"onPrepareOptionsMenu" which is called every time the menu is called.

package de.voge11a.ando1d.soc1a1app
1mpof ando1d.v1eW.Menu
1mpof ando1d.v1eW.Menulnf1afe
1mpof ando1d.v1eW.Menulfem
pub11c c1ass Ovev1eWAcf1v1fy exfends Acf1v1fy {
0Ove1de
}
0Ove1de
pub11c boo1ean onCeafeOpf1onsMenu{Menu menu} {
Menulnf1afe 1nf1afe = gefMenulnf1afe{}
1nf1afe.1nf1afe{k.menu.ma1nmenu, menu}
efun fue
}
0Ove1de
pub11c boo1ean onOpf1onslfem5e1ecfed{Menulfem 1fem} {
1oasf.make1exf{fh1s, "Jusf a fesf", 1oasf.LLNG1h5hOk1}.shoW{}
efun fue
}
}

Run your application. As there is enough space in the action bar your item will be displayed there. If there would be
more items you could press "Menu" on the emulator to see them. If you select the menu item you should see
info message.
The two "Preference" buttons are not yet active. We will use them in the next chapter.
14. P
Android supports the usage of Preferences to allow you to save data for your application. Preferences are
key values. The definition of Preferences can also be done via an XML resource.
Android provides the class "PreferenceActivity" which extends the class Activity. PreferenceActivity supports the
simple handling of preferences. This activity can load a preference definition resources via the method
addPreferencesFromResource().
To communicate between different components Android uses Intents. Typically the PreferenceActivity is started from
another activity via an Intent.
In your application you can access the preference manager via the following:

5haedPefeences pefeences = PefeenceManage.gefDefau1f5haedPefeences{fh1s}

Values can get access via the key of the preference setting.

5f1ng usename = pefeences.gef5f1ng{"usename", "n/a"}

To create or change preferences you have to call the edit() methods. Once you have changed the value you have to
call commit() to apply your changes.

Ld1fo ed1f = pefeences.ed1f{}
ed1f.puf5f1ng{"usename", "neWva1uefouse"}
ed1f.comm1f{}

15. T: P
15.1. U
We will continue using the example project "de.vogella.android.social".
Create an Android XML resource "preferences.xml" of type "PreferenceScreen".
Open the file via right-mouse click and Open-with Android XML Resource Editor. Press Add, add a
"PreferenceCategory" and add two preferences "EditTextPreferences" to this category : "User" and "Password".
You can also enter values for other properties of EdiTeField, e.g. the inputMethod.
Add the following attribute to the XML definition of your password field to make the input quoted with *.

ando1d:1npuf1ype="fexfPassWod"

Create the class MPefeenceAcii which extends PefeenceAcii. This Acii
the "preference.xml" file and will allow the user to change the values.

1mpof ando1d.pefeence.PefeenceAcf1v1fy
pub11c c1ass MyPefeencesAcf1v1fy exfends PefeenceAcf1v1fy {
0Ove1de
addPefeencesIomkesouce{k.xm1.pefeences}
}
}

To make this class available as an activity for Android you need to register it in your "AndroidManifest.xml" file.
Select "AndroidManifest.xml" and the tab "Application". Scroll to the botton of the view and add your new
the "Add" button.
To make use of our new preference activity and the preference values we adjust the "OverviewActivity".
button will show the current values of the preferences via a Toast and the second button will revert the maintained
user name to demonstrate how you could change the preferences via code.

1mpof ando1d.confenf.5haedPefeences
1mpof ando1d.confenf.5haedPefeences.Ld1fo
1mpof ando1d.pefeence.PefeenceManage
1mpof ando1d.v1eW.Menu
1mpof ando1d.v1eW.Menulnf1afe
1mpof ando1d.v1eW.Menulfem
1mpof ando1d.v1eW.v1eW.OnC11ckL1sfene
1mpof ando1d.W1dgef.8uffon
pub11c c1ass Ovev1eWAcf1v1fy exfends Acf1v1fy {
5haedPefeences pefeences
0Ove1de
8uffon buffon = {8uffon} f1ndv1eW8yld{k.1d.8uffon01}
// ln1f1a11ze pefeences
pefeences = PefeenceManage.gefDefau1f5haedPefeences{fh1s}
buffon.sefOnC11ckL1sfene{neW OnC11ckL1sfene{} {
pub11c vo1d onC11ck{v1eW v} {
5f1ng usename = pefeences.gef5f1ng{"usename", "n/a"
5f1ng passWod = pefeences.gef5f1ng{"passWod", "n/a"
shoWPefs{usename, passWod}
}
}}
8uffon buffonChangePefeences = {8uffon} f1ndv1eW8yld{k.1d.8uffon02}
buffonChangePefeences.sefOnC11ckL1sfene{neW OnC11ckL1sfene{} {
pub11c vo1d onC11ck{v1eW v} {

updafePefeenceva1ue{}
}
}}
}

p1vafe vo1d shoWPefs{5f1ng usename, 5f1ng passWod}{
1oasf.make1exf{
Ovev1eWAcf1v1fy.fh1s,
"lnpuf: " + usename + " and passWod: "
+ passWod, 1oasf.LLNG1hLONG}.shoW{}
}

p1vafe vo1d updafePefeenceva1ue{}{
Ld1fo ed1f = pefeences.ed1f{}
5f1ng usename = pefeences.gef5f1ng{"usename", "n/a"}
// We W111 usf evef fhe cuenf use name and save aga1n
5f1ng8uffe buffe = neW 5f1ng8uffe{}
fo {1nf 1 = usename.1engfh{} - 1 1 >= 0 1--} {
buffe.append{usename.chaAf{1}}
}
ed1f.puf5f1ng{"usename", buffe.fo5f1ng{}}
ed1f.comm1f{}
// A foasf 1s a v1eW confa1n1ng a qu1ck 11ff1e message fo fhe
// use. We g1ve a 11ff1e feedback
1oasf.make1exf{Ovev1eWAcf1v1fy.fh1s,
"kevefed sf1ng sequence of use name.",
}

To open the new preference Acii we will use the onOpionIemSeleced() method. Even though we
currently have only one option in our menu we use a switch to be ready for several new menu entries. To see the
current values of the preferences we define a button and use the class PefeenceManage to get the
sharedPreferences.

0Ove1de
pub11c boo1ean onCeafeOpf1onsMenu{Menu menu} {
Menulnf1afe 1nf1afe = gefMenulnf1afe{}
1nf1afe.1nf1afe{k.menu.ma1nmenu, menu}
efun fue
}
// 1h1s mefhod 1s ca11ed once fhe menu 1s se1ecfed
0Ove1de
pub11c boo1ean onOpf1onslfem5e1ecfed{Menulfem 1fem} {
sW1fch {1fem.geflfemld{}} {
// We have on1y one menu opf1on
case k.1d.pefeences:
// Launch Pefeence acf1v1fy
lnfenf 1 = neW lnfenf{Ovev1eWAcf1v1fy.fh1s, MyPefeencesAcf1v1fy.c1ass
sfafAcf1v1fy{1}
// 5ome feedback fo fhe use
1oasf.make1exf{Ovev1eWAcf1v1fy.fh1s, "Lnfe you use cedenf1a1s.",
beak
}
efun fue
}

15.2. R
Run your application. Press the "menu" hardware button and then select your menu item "Preferences". You should
be able to enter your user settings then press the back hardware button to return to your main activity. The saved
values should be displayed in a small message windows (Toast) if you press your first button. If you press the
button the username should be reversed.
16. L M VG
16.1. A L M
A layout manager is a subclass of VieGop and is responsible for the layout of itself and its child Vie
Android supports different default layout managers.
As of Android 4.0 the most relevant layout manager are LineaLao, FameLao, RelaieLao
GidLao.
All layouts allow the developer to define attributes. Children can also define attributes which may be evaluated by
their parent layout.
AboleLaoLao is deprecated and TableLao can be implemented more effectively via
GidLao
16.2. LL
LineaLao puts all its child elements into a single column or row depending on the andoid:oienaion
attribute. Possible values for this attribute are hoional and eical, hoional is the default value.
LineaLao can be nested to achieve more complex layouts.
16.3. RL
RelaieLao allow to position the widget relative to each other. This allows for complex layouts.
A simple usage for RelaieLao is if you want to center a single component. Just add one component
RelaieLao and set the andoid:lao_ceneInPaen attribute to true.

<ke1af1veLayouf xm1ns:ando1d="hffp://schemas.ando1d.com/apk/es/ando1d"
ando1d:1ayoufW1dfh="mafchpaenf"
ando1d:1ayoufhe1ghf="mafchpaenf"
<Pogess8a
ando1d:1d="0+1d/pogess8a1"
sfy1e="?ando1d:aff/pogess8a5fy1eLage"
ando1d:1ayoufcenfelnPaenf="fue"
/>
</ke1af1veLayouf>

16.4. G
GidLao was introduced with Android 4.0. This layout allows you to organize a view into a Grid. GridLayout
separates its drawing area into: rows, columns, and cells.
You can specify how many columns you want for define for each Vie in which row and column it should be placed
and how many columns and rows it should use. If not specified GidLao uses defaults, e.g. one column, one
row and the position of a Vie depends on the order of the declaration of the Vie.
16.5. SV
ScrollViews can be used to contain one view that might be to big to fit on one screen. If the view is to big the
ScrollView will display a scroll bar to scroll the context. Of course this view can be a layout which can then contain
other elements.
17. T: SV
Create an android project "de.vogella.android.scrollview" with the activity "ScrollView". Create the following layout
and class.

<5co11v1eW xm1ns:ando1d="hffp://schemas.ando1d.com/apk/es/ando1d"
ando1d:f111v1eWpof="fue"
<L1neaLayouf
ando1d:1d="0+1d/L1neaLayouf01"
<1exfv1eW
ando1d:1d="0+1d/1exfv1eW01"
ando1d:padd1ngLeff="d1p"
ando1d:padd1ngk1ghf="d1p"
ando1d:padd1ng1op="d1p"
ando1d:fexf="1h1s 1s a heade"
ando1d:fexfAppeaance="?ando1d:aff/fexfAppeaanceLage" >
</1exfv1eW>
<1exfv1eW
ando1d:1d="0+1d/1exfv1eW02"
ando1d:1ayoufWe1ghf="1.0"
ando1d:fexf="0+1d/1exfv1eW02" >
</1exfv1eW>
<L1neaLayouf
ando1d:1d="0+1d/L1neaLayouf02"
ando1d:1ayoufhe1ghf="Wapconfenf" >
<8uffon
ando1d:fexf="5ubm1f" >
</8uffon>
<8uffon
ando1d:fexf="Cance1" >
</8uffon>
</L1neaLayouf>
</L1neaLayouf>
</5co11v1eW>

package de.voge11a.ando1d.sco11v1eW
1mpof ando1d.W1dgef.1exfv1eW
pub11c c1ass 5co11v1eW exfends Acf1v1fy {

/"" Ca11ed When fhe acf1v1fy 1s f1sf ceafed. "/
0Ove1de
1exfv1eW v1eW = {1exfv1eW} f1ndv1eW8yld{k.1d.1exfv1eW02}
5f1ng s=""
fo {1nf 1=0 1 < 100 1++} {
s += "voge11a.de "
}
v1eW.sef1exf{s}
}
}

The attribute "android:fillViewport="true"" ensures that the scrollview is set to the full screen even if the elements are
smaller then one screen and the "layout_weight" tell the android system that these elements should be extended.
18. S
18.1. O
Styles in Android allow to define the look and feel of Android application in external files. These styles can get
assigned to the complete Applications, Aciiiie or Vie.
You can define styles in XML and assign them to these elements. This way you only have to set common attributes
once and can later change the look in one central place.
18.2. E
The following "styles.xml" XML file would be created in the "/res/xml" folder.

<esouces>
<sfy1e name="fexf">
<1fem name="ando1d:padd1ng">4d1p</1fem>
<1fem name="ando1d:fexfAppeaance">?ando1d:aff/fexfAppeaanceLage</1fem>
<1fem name="ando1d:fexfCo1o">#000000</1fem>
</sfy1e>
<sfy1e name="1ayouf">
<1fem name="ando1d:backgound">#C0C0C0</1fem>
</sfy1e>
</esouces>

You assign the style attribute to your elements, for example to the text elements via style=@style/text.
19. S
19.1. U
Android devices are different in terms of resolution and in terms of density. Therefore it is recommended never to
use fixed sized dimensions.
The unit of measurement which should be used is "dp" (which is the same as "dip" but shorter). dp refers to the base
line of an Android device, e.g. 320x480 with 160dpi (dots per inch), which was the size of the first Android device
(G1). This size is also known as mdpi (medium dots per inch).
If you specify the size in "dp", Android will automatically scale it, depending on the device. On a mdpi device "dp" will
be equal to pixel but it will be smaller on a ldpi (approx. 120dip) and larger on a hdip(approx. 240dpi) device, so
it always occupies the same physical space.
You can use "dp" in your resources, e.g. layout files. The Android SDK expects that you specify everything in pixels.
You can therefore use the following formulator to calculate the right amount of pixels for a dimension specified in dp.

pub11c 1nf convef1oDp{1nf 1npuf} {
// Gef fhe sceens dens1fy sca1e
f1na1 f1oaf sca1e = gefkesouces{}.gefD1sp1ayMef1cs{}.dens1fy
// Convef fhe dps fo p1xe1s, based on dens1fy sca1e
efun {1nf} {1npuf " sca1e + 0.5f}
}

19.2. U
Android also allows to use resource qualifiers to specify that certain resources should only be used for certain
resolutions.
20. F
20.1. O
Fagmen components allow you to organize your application code so that it is easier to support different sized
devices.
Fagmen are components with their own lifecycle and their own user interface. They can be defined via layout
files or via coding.
Fagmen always run in the context of an Acii. If an Acii is stopped its Fagmen will also be
stopped; if an Acii is destroyed its Fagmen will also get destroyed.
If a Fagmen component is defined in an XML layout file, the andoid:name attribute points to the Fagmen
class.
The base class for Fagmen is andoid.app.Fagmen. For special purposes you can also use more
special classes, like LiFagmen or DialogFagmen.
The onCreateView() method is called by Android once the Fagmen should create its user interface. Here you can
inflate an layout. The onSa() mehod i called once he Fagmen ge iible.
Fagmen can be dynamically added and removed from an Acii via Fagmen transactions. This will add
the action to the history stack of the Acii, i.e. this will allow to revert the Fagmen changes in the
Acii via the back button.
20.2. W F
Fagmen make it easy to re-use components in different layouts, e.g. you can build single-pane layouts for
handsets (phones) and multi-pane layouts for tablets.
This is not limited to tablets; for example you can use Fagmen also to support different layout for landscape and
portrait orientation. But as tablets offer significantly more space you typically include more views into the layout and
Fagmen makes that easier.
The typical example is a list of items in an activity. On a tablet you see the details immediately on the same screen
on the right hand side if you click on item. On a handset you jump to a new detail screen. The following discussion will
assume that you have two Fagmen (main and detail) but you can also have more. We will also have one
activity and one detailed activity. On a tablet the main activity contains both Fagmen in its layout, on a handheld
it only contains the main fragment.
To check for an fragment you can use the FragmentManager.

Defa11Iagmenf fagmenf = {Defa11Iagmenf} gefIagmenfManage{}.
f1ndIagmenf8yld{k.1d.defa11fag}
1f {fagmenf==nu11 || ! fagmenf.1slnLayouf{}} {
// sfaf neW Acf1v1fy
}
e1se {
fagmenf.updafe{...}
}

To create different layouts with Fagmen you can:
Use one activity, which displays two Fagmen for tablets and only one on handsets devices. In this case
you would switch the Fagmen in the activity whenever necessary. This requires that the fragment
declared in the layout file as such Fagmen cannot be removed during runtime. It also requires an update of
the action bar if the action bar status depends on the fragment.
Use separate activities to host each fragment on a handset. For example, when the tablet UI uses two
Fagmen in an activity, use the same activity for handsets, but supply an alternative layout that includes just
one fragment. When you need to switch Fagmen, start another activity that hosts the other fragment.
The second approach is the most flexible and in general preferable way of using Fagmen. In this case the main
activity checks if the detail fragment is available in the layout. If the detailed fragment is there, the main activity tells
the fragment that is should update itself. If the detail fragment is not available the main activity starts the detailed
activity.
It is good practice that Fagmen do not manipulate each other. For this purpose a Fagmen typically
implements an interface to get new data from its host Acii.
21. F T
21.1. O
The following tutorial demonstrates how to use Fagmen. The entry Acii (called MainAcii
application ) will use different layouts for portrait and for landscape mode.
In portrait mode MainAcii will show one Fragment with a list of names. If the user touches an item in the list,
a second Acii called DeailAcii will start and show the selected text.
In landscape mode MainAcii will show two Fagmen. The first is again the Fagmen which shows the
list of names. The second Fagmen shows the text of the current selected item. This is similar to the portrait mode,
but the whole information will be shown on one screen.
21.2. C
Create a new project de.ogella.andoid.fagmen with an Acii called MainAcii
21.3. C
Create or change the following layout files in the "res/layout/" folder.
First create the following file called "details.xml". This layout will be used by the DeailFagmen.

<1exfv1eW
ando1d:1d="0+1d/defa11s1exf"
ando1d:1ayoufgav1fy="cenfeho1zonfa1|cenfevef1ca1"
ando1d:1ayoufmag1n1op="20d1p"
ando1d:fexf="Lage 1exf"
ando1d:fexfAppeaance="?ando1d:aff/fexfAppeaanceLage"
ando1d:fexf51ze="30d1p" />
</L1neaLayouf>

Change the existing "main.xml" file. This layout will be used by MainAcii in landscape mode and shows two
Fagmen.

ando1d:o1enfaf1on="ho1zonfa1" >
<fagmenf
ando1d:1d="0+1d/11sfIagmenf"
ando1d:1ayoufW1dfh="150d1p"
ando1d:1ayoufmag1n1op="?ando1d:aff/acf1on8a51ze"
c1ass="de.voge11a.ando1d.fagmenfs.L1sfIagmenf" ></fagmenf>
<fagmenf
ando1d:1d="0+1d/defa11Iagmenf"
c1ass="de.voge11a.ando1d.fagmenfs.Defa11Iagmenf" >

</fagmenf>
</L1neaLayouf>

21.4. C F
Create now the Fagmen classes. Create the LiFagmen class.

package de.voge11a.ando1d.fagmenfs
1mpof ando1d.confenf.lnfenf
1mpof ando1d.W1dgef.AayAdapfe
1mpof ando1d.W1dgef.L1sfv1eW
pub11c c1ass L1sfIagmenf exfends ando1d.app.L1sfIagmenf {
0Ove1de
}
0Ove1de
pub11c vo1d onAcf1v1fyCeafed{8und1e savedlnsfance5fafe} {
supe.onAcf1v1fyCeafed{savedlnsfance5fafe}
5f1ng|] va1ues = neW 5f1ng|] { "Ando1d", "1Phone", "W1ndoWsMob11e",
"81ackbey", "WebO5", "ubunfu", "W1ndoWs7", "Max O5 X",
"L1nux", "O5/2" }
AayAdapfe<5f1ng> adapfe = neW AayAdapfe<5f1ng>{gefAcf1v1fy{},
ando1d.k.1ayouf.s1mp1e11sf1fem1, va1ues}
sefL1sfAdapfe{adapfe}
}
0Ove1de
pub11c vo1d onL1sflfemC11ck{L1sfv1eW 1, v1eW v, 1nf pos1f1on, 1ong 1d} {
5f1ng 1fem = {5f1ng} gefL1sfAdapfe{}.geflfem{pos1f1on}
Defa11Iagmenf fagmenf = {Defa11Iagmenf} gefIagmenfManage{}
.f1ndIagmenf8yld{k.1d.defa11Iagmenf}
1f {fagmenf != nu11 && fagmenf.1slnLayouf{}} {
fagmenf.sef1exf{1fem}
} e1se {
lnfenf 1nfenf = neW lnfenf{gefAcf1v1fy{}.gefApp11caf1onConfexf{},
Defa11Acf1v1fy.c1ass}
1nfenf.pufLxfa{"va1ue", 1fem}
sfafAcf1v1fy{1nfenf}
}
}
}

Create the DeailFagmen class.

1mpof ando1d.app.Iagmenf
1mpof ando1d.uf11.Log
1mpof ando1d.v1eW.Layouflnf1afe
1mpof ando1d.v1eW.v1eWGoup
pub11c c1ass Defa11Iagmenf exfends Iagmenf {
0Ove1de
Log.e{"1esf", "he11o"}
}
0Ove1de
pub11c vo1d onAcf1v1fyCeafed{8und1e savedlnsfance5fafe} {
supe.onAcf1v1fyCeafed{savedlnsfance5fafe}
}
0Ove1de
pub11c v1eW onCeafev1eW{Layouflnf1afe 1nf1afe, v1eWGoup confa1ne,
8und1e savedlnsfance5fafe} {
v1eW v1eW = 1nf1afe.1nf1afe{k.1ayouf.defa11s, confa1ne, fa1se}
efun v1eW
}
pub11c vo1d sef1exf{5f1ng 1fem} {
1exfv1eW v1eW = {1exfv1eW} gefv1eW{}.f1ndv1eW8yld{k.1d.defa11s1exf}
v1eW.sef1exf{1fem}
}
}

21.5. C
We want that Android uses a different main.xml file in portrait model then in landscape mode.
For this reason create the "res/layout-port" folder.
In portrait mode Android will check the "layout-port" folder for fitting layout files. Only if we would not have a
"main.xml" file in "layout-port", Android would check the "layout" folder.
Therefore create the following "main.xml" layout file in "res/layout-port".

ando1d:o1enfaf1on="ho1zonfa1" >
<fagmenf
ando1d:1d="0+1d/11sfIagmenf"
ando1d:1ayoufmag1n1op="?ando1d:aff/acf1on8a51ze"
c1ass="de.voge11a.ando1d.fagmenfs.L1sfIagmenf" />
</L1neaLayouf>

Also create the "details_activity_layout.xml" layout file. This layout will be used in the DeailAcii
only used in portrait mode. Please note that we could have create this file also in the "layout" folder, but as it is only
used in portrait mode it is best practise to place it into this folder.

<fagmenf
ando1d:1d="0+1d/defa11Iagmenf"
c1ass="de.voge11a.ando1d.fagmenfs.Defa11Iagmenf" />
</L1neaLayouf>
Home
Tutorials Trainings Books Social

21.6. A
Create a new Acii called DeailAcii with the following class.

1mpof ando1d.confenf.es.Conf1guaf1on
pub11c c1ass Defa11Acf1v1fy exfends Acf1v1fy {
0Ove1de
pofecfed vo1d onCeafe{8und1e savedlnsfance5fafe} {
// Need fo check 1f Acf1v1fy has been sW1fched fo 1andscape mode
// lf yes, f1n1shed and go back fo fhe sfaf Acf1v1fy
1f {gefkesouces{}.gefConf1guaf1on{}.o1enfaf1on == Conf1guaf1on.OklLN1A1lONLAN
D5CAPL} {
f1n1sh{}
efun
}
sefConfenfv1eW{k.1ayouf.defa11sacf1v1fy1ayouf}
8und1e exfas = geflnfenf{}.gefLxfas{}
1f {exfas != nu11} {
5f1ng s = exfas.gef5f1ng{"va1ue"}
1exfv1eW v1eW = {1exfv1eW} f1ndv1eW8yld{k.1d.defa11s1exf}
v1eW.sef1exf{s}
}
}
}

MainAcii will remain unmodified.

pub11c c1ass Ma1nAcf1v1fy exfends Acf1v1fy {

/"" Ca11ed When fhe acf1v1fy 1s f1sf ceafed. "/
0Ove1de
}
}

21.7. R
Run your example. If you run the application in portrait mode you should see only one Fagmen. Use Ctrl+F11 to
switch the orientation. In horizontal mode you should see two Fagmen. If you select an item in portrait mode a
new Acii should get started with the selected item. In horizontal mode your second Fagmen should display
the select item.
22. DDMS
22.1. DDMS - D D M S
Eclipse provides a perspective for interacting with your Android (virtual) device and your Android application
program. Select Window Open Perspective Other DDMS to open this perspective. It includes several
Vie which can also be used independently and allows for example the application to place calls and send SMS to
the device. It also allows the application to set the current geo position and allows you to perform a performance
trace of your application.
22.2. LC V
You can see the log (including System.out.print() statements) via the LogCat view.
22.3. F
The file explorer allows to see the files on the Android simulator.
23. S
23.1. A D B - S
You can access your Android emulator also via the console. Open a shell, switch to your "android-sdk" installation
directory into the folder "tools". Start the shell via the following command "adb shell".

adb she11

You can also copy a file from and to your device via the following commands.

// Assume fhe gesfue f11e ex1sfs on you Ando1d dev1ce
adb pu11 /sdcad/gesfues ~/fesf
// NoW copy 1f back
adb push ~/fesf/gesfue /sdcad/gesfues2

This will connect you to your device and give you Linux command line access to the underlying file system, e.g. ls, rm,
mkdir, etc. The application data is stored in the directory "/data/data/package_of_your_app".
If you have several devices running you can issue commands to one individual device.

# L1sfs a11 dev1ces
adb dev1ces
#kesu1f
L1sf of dev1ces affached
emu1afo-5554 affached
emu1afo-5555 affached
# lssue a command fo a spec1f1c dev1ce
adb -s emu1afo-5554 she11

23.2. U
You can uninstall an android application via the shell. Switch the data/app directory (cd /data/app) and simply delete
your android application.
You can also uninstall an app via adb with the package name.

adb un1nsfa11 <packagename>

23.3. E C
Alternatively to adb you can also use telnet to connect to the device. This allows you to simulate certain things, e.g.
incoming call, change the network "stability", set your current geocodes, etc. Use "telnet localhost 5554" to connect
to your simulated device. To exit the console session, use the command "quit" or "exit".
For example to change the power settings of your phone, to receive an sms and to get an incoming call make the
following.

# connecfs fo dev1ce
fe1nef 1oca1hosf 5554
# sef fhe poWe 1eve1
poWe sfafus fu11
poWe sfafus chag1ng
# make a ca11 fo fhe dev1ce
gsm ca11 012041293123
# send a sms fo fhe dev1ce
sms send 12345 W111 be home soon
# sef fhe geo 1ocaf1on
geo f1x 4 51

For more information on the emulator console please see Emulator Console manual
24. D
Turn on "USB Debugging" on your device in the settings. Select in the settings Applications > Development, then
enable USB debugging. You also need to install the driver for your mobile phone. For details please see
on a Device . Please note that the Android version you are developing for must be the installed version on your
phone.
To select your phone, select the "Run Configurations", select "Manual" selection and select your device.
25. T
Please help me to support this article:

26. Q D
Before posting questions, please see the vogella FAQ. If you have questions or find an error in this article please
the www.vogella.de Google Group. I have created a short list how to create good questions which might also help
you.
27. L L
27.1. S C
Source Code of Examples
27.2. A R
Android 2 (German Book)
Android ListView and ListActivity
Android SQlite Database
Android Widgets
Android Live Wallpaper
Android Services
Android Location API and Google Maps
Android Intents
Android and Networking
Android Homepage
Android Developer Homepage
Android Issues / Bugs
Android Google Groups
Android Live Folder
27.3. R
Eclipse RCP Training (German) Eclipse RCP Training with Lars Vogel
Android Tutorial Introduction to Android Programming
GWT Tutorial Program in Java and compile to JavaScript and HTML
Eclipse RCP Tutorial Create native applications in Java
JUnit Tutorial Test your application
Git Tutorial Put everything you have under distributed version control system

Android Development Tutorial PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Android Development Tutorial PDF

Hochgeladen von

Copyright:

Verfügbare Formate

10/03/12 Andoid Deelopmen Toial

Das könnte Ihnen auch gefallen