Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am d36bc32e: Merge "SDK doc updates" into honeycomb

Browse Source 
* commit 'd36bc32ea9a109596308a0516b3e0898c82cebc5':
  SDK doc updates
This commit is contained in:
Bill Gruber
2011-04-04 17:21:25 -07:00
committed by Android Git Automerger
parent 5a41a8a0fd d36bc32ea9
commit 63ac03794d
4 changed files with 151 additions and 194 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/html/guide/developing/index.jd
View File

@@ -9,19 +9,15 @@ page.title=Introduction
<p>However, you may choose to develop with another IDE or a simple text editor and invoke the <p>However, you may choose to develop with another IDE or a simple text editor and invoke the
tools on the command line or with scripts. This is a less streamlined way to develop because you tools on the command line or with scripts. This is a less streamlined way to develop because you
will sometimes have to call command line tools manually, but you will have access to the same will sometimes have to call command line tools manually, but you will have access to the same
amount of features that you would have in Eclipse.</p> number of features that you would have in Eclipse.</p>
<p class="note"><strong>Note:</strong> Before you begin developing Android applications, make
sure you have gone through all of the steps outlined in <a
href="{@docRoot}sdk/installing.html">Installing the SDK</a>.</p>
<p>The basic steps for developing applications with or without Eclipse are the same:</p> <p>The basic steps for developing applications with or without Eclipse are the same:</p>
<ol> <ol>
<li>Install Eclipse or your own IDE.
<p>Install Eclipse along with <a href="{@docRoot}sdk/eclipse-adt.html#installing">the ADT
Plugin</a>, or install an editor of your choice if you want to use the command line SDK tools.
If you are already developing applications, be sure to <a href=
"{@docRoot}sdk/eclipse-adt.html#updating">update Your ADT Plugin</a> to the latest version
before continuing.</p>
</li>
<li>Set up Android Virtual Devices or hardware devices. <li>Set up Android Virtual Devices or hardware devices.

136
docs/html/guide/developing/tools/index.jd
View File

@@ -3,83 +3,83 @@ page.title=Tools
<img src="{@docRoot}assets/images/android_wrench.png" alt="" align="right"> <img src="{@docRoot}assets/images/android_wrench.png" alt="" align="right">
<p>The Android SDK includes a variety of custom tools that help you develop mobile <p>The Android SDK includes a variety of tools that help you develop mobile
applications on the Android platform. The most important of these are the Android applications for the Android platform. The tools are classified into two groups: SDK tools
Emulator and the Android Development Tools plugin for Eclipse, but the SDK also and platform tools. SDK tools are platform independent and are required no matter which
includes a variety of other tools for debugging, packaging, and installing your Android platform you are developing on. Platform tools are customized to support the features of the
applications on the emulator. </p> latest Android platform.</p>
<dl> <h2 id="tools-sdk">SDK Tools</h2>
<dt><a href="adb.html">Android Debug Bridge</a></dt> <p>The SDK tools are installed with the SDK starter package and are periodically updated.
<dd>A versatile tool lets you manage the state of an emulator instance The SDK tools are required if you are developing Android applications. The most important SDK tools
or Android-powered device.</dd> include the Android SDK and AVD Manager (<code>android</code>), the emulator
(<code>emulator</code>), and the Dalvik Debug Monitor Server
<dt><a href="android.html">android</a></dt> (<code>ddms</code>). A short summary of some frequently-used SDK tools is provided below.</p>
<dd>Lets you manage AVDs, projects, and the installed components of the SDK.
</dd>
<dt><a href="bmgr.html">bmgr</a></dt>
<dd>Lets you interact with the Backup Manager on Android devices
supporting API Level 8 or greater. It provides commands to invoke backup and restore operations
so that you don't need to repeatedly wipe data or take similar intrusive steps in order to test
your application's backup agent. These commands are accessed via the adb shell.
</dd>
<dl>
<dt><a href="android.html">android</a></dt>
<dd>Lets you manage AVDs, projects, and the installed components of the SDK.</dd>
<dt><a href="{@docRoot}guide/developing/debugging/ddms.html">Dalvik Debug Monitor
Server (ddms)</a></dt>
<dd>Lets you debug Android applications.</dd>
<dt><a href="dmtracedump.html">dmtracedump</a></dt> <dt><a href="dmtracedump.html">dmtracedump</a></dt>
<dd>Generates graphical call-stack diagrams from trace log files. The tool uses the
<dd>Generates graphical call-stack diagrams from trace log files. Graphviz Dot utility to create the graphical output, so you need to install Graphviz before
The tool uses the Graphviz Dot utility to create the graphical output, so you need to install running <code>dmtracedump</code>. For more information on using <code>dmtracedump</code>, see <a
Graphviz before running <code>dmtracedump</code>. For more information on using <code>dmtracedump</code>, see href="{@docRoot}guide/developing/debugging/debugging-tracing.html#dmtracedump">Profiling
<a href="{@docRoot}guide/developing/debugging/debugging-tracing.html#dmtracedump">Profiling with with Traceview and dmtracedump</a></dd>
Traceview and dmtracedump</a> <dt><a href="draw9patch.html">Draw 9-patch</a></dt>
</dd> <dd>Allows you to easily create a {@link android.graphics.NinePatch} graphic using a
WYSIWYG editor. It also previews stretched versions of the image, and highlights the area in which
<dt><a href="draw9patch.html">Draw 9-patch</a></dt> content is allowed.</dd>
<dd>Allows you to easily create a {@link android.graphics.NinePatch} graphic using a WYSIWYG editor. <dt><a href="emulator.html">Android Emulator (emulator)</a></dt>
It also previews stretched versions of the image, and highlights the area in which content is allowed. <dd>A QEMU-based device-emulation tool that you can use to design, debug, and test
</dd> your applications in an actual Android run-time environment.</dd>
<dt><a href="hierarchy-viewer.html">Hierarchy Viewer (hierarchyviewer)</a></dt>
<dt><a href="emulator.html">Android Emulator</a></dt> <dd>Lets you debug and optimize an Android application's user interface.</dd>
<dd>A QEMU-based device-emulation tool that you can use to design,
debug, and test your applications in an actual Android run-time environment. </dd>
<dt><a href="hprof-conv.html">hprof-conv</a></dt> <dt><a href="hprof-conv.html">hprof-conv</a></dt>
<dd>Converts the HPROF file that is generated by the Android SDK tools to a standard format so
<dd>Converts the HPROF file that is generated by the Android SDK tools to a you can view the file in a profiling tool of your choice.</dd>
standard format so you can view the file in a profiling tool of your choice.</dd>
<dt><a href="layoutopt.html">layoutopt</a></dt> <dt><a href="layoutopt.html">layoutopt</a></dt>
<dd>Lets you quickly analyze your application's layouts in order to <dd>Lets you quickly analyze your application's layouts in order to optimize them for
optimize them for efficiency. efficiency.</dd>
</dd>
<dt><a href="mksdcard.html">logcat</a></dt>
<dd>Lets you read system log messages that are output on an Android device or emulator.</dd>
<dt><a href="mksdcard.html">mksdcard</a></dt> <dt><a href="mksdcard.html">mksdcard</a></dt>
<dd>Helps you create a disk image that you can use with the emulator, <dd>Helps you create a disk image that you can use with the emulator, to simulate the presence
to simulate the presence of an external storage card (such as an SD card).</dd> of an external storage card (such as an SD card).</dd>
<dt><a href="monkey.html">Monkey</a></dt> <dt><a href="monkey.html">Monkey</a></dt>
<dd>Runs on your emulator or device and generates pseudo-random <dd>Runs on your emulator or device and generates pseudo-random streams of user events such
streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey
You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.</dd> to stress-test applications that you are developing, in a random yet repeatable manner.</dd>
<dt><a href="monkeyrunner_concepts.html">monkeyrunner</a></dt> <dt><a href="monkeyrunner_concepts.html">monkeyrunner</a></dt>
<dd>Provides an API for writing programs that control an Android device <dd>Provides an API for writing programs that control an Android device or emulator from
or emulator from outside of Android code.</dd> outside of Android code.</dd>
<dt><a href="proguard.html">ProGuard</a></dt> <dt><a href="proguard.html">ProGuard</a></dt>
<dd>Shrinks, optimizes, and obfuscates your code by removing unused code and renaming classes, <dd>Shrinks, optimizes, and obfuscates your code by removing unused code and renaming
fields, and methods with semantically obscure names.</dd> classes, fields, and methods with semantically obscure names.</dd>
<dt><a href="sqlite3.html">sqlite3</a></dt> <dt><a href="sqlite3.html">sqlite3</a></dt>
<dd>Lets you access the SQLite data files created and used by Android applications.</dd> <dd>Lets you access the SQLite data files created and used by Android applications.</dd>
<dt><a href="traceview.html">traceview</a></dt>
<dd>Provides a graphical viewer for execution logs saved by your application.</dd>
<dt><a href="zipalign.html">zipalign</a></dt> <dt><a href="zipalign.html">zipalign</a></dt>
<dd>Optimizes <code>.apk</code> files by ensuring that all uncompressed data starts <dd>Optimizes <code>.apk</code> files by ensuring that all uncompressed data starts with a
with a particular alignment relative to the start of the file. This should always be used particular alignment relative to the start of the file. This should always be used to align .apk
to align .apk files after they have been signed.</dd> files after they have been signed.</dd>
</dl> </dl>
<h2 id="tools-platform">Platform Tools</h2>
<p>The platform tools are typically updated every time you install a new SDK platform. Each update
of the platform tools is backward compatible with older platforms. Usually, you directly use only
one of the platform tools&mdash;the <a href="adb.html">Android Debug Bridge (<code>adb</code>)</a>.
Android Debug Bridge is a versatile tool that lets you manage the state of an emulator instance or
Android-powered device. You can also use it to install an Android application (.apk) file on a
device.</p>
<p>The other platform tools, such as <a href="{@docRoot}guide/developing/tools/aidl.html">aidl</a>,
<code>aapt</code>, <code>dexdump</code>, and <code>dx</code>, are typically called by the Android
build tools or Android Development Tools (ADT), so you rarely need to invoke these tools directly.
As a general rule, you should rely on the build tools or the ADT plugin to call them as needed.</p>
<p class="note"><strong>Note:</strong> The Android SDK provides additional shell tools that can
be accessed through <code>adb</code>, such as <a href="bmgr.html">bmgr</a> and
<a href="logcat.html">logcat</a>.</p>

24
docs/html/sdk/eclipse-adt.jd
View File

@@ -656,7 +656,7 @@ ADT installation as described in the steps below. </p>
<h3 id="downloading">Downloading the ADT Plugin</h3> <h3 id="downloading">Downloading the ADT Plugin</h3>
<p>Use the Update Manager feature of your Eclipse installation to install the latest <p>Use the Update Manager feature of your Eclipse installation to install the latest
revision of ADT on your development computer.<p> revision of ADT on your development computer.<>
<p>Assuming that you have a compatible version of the Eclipse IDE installed, as <p>Assuming that you have a compatible version of the Eclipse IDE installed, as
described in <a href="#preparing">Preparing for Installation</a>, above, follow described in <a href="#preparing">Preparing for Installation</a>, above, follow
@@ -671,26 +671,32 @@ Software...</strong>.</li>
<li>In the Add Repository dialog that appears, enter "ADT Plugin" for the <em>Name</em> and the <li>In the Add Repository dialog that appears, enter "ADT Plugin" for the <em>Name</em> and the
following URL for the <em>Location</em>: following URL for the <em>Location</em>:
<pre>https://dl-ssl.google.com/android/eclipse/</pre> <pre>https://dl-ssl.google.com/android/eclipse/</pre>
<p>Note: If you have trouble acquiring the plugin, try using "http" in the Location URL, </li>
instead of "https" (https is preferred for security reasons).</p> <li>Click <strong>OK</strong>
<p>Click <strong>OK</strong>.</p></li> <p>Note: If you have trouble acquiring the plugin, try using "http" in the Location URL,
<li>In the Available Software dialog, select instead of "https" (https is preferred for security reasons).</p></li>
the checkbox next to Developer Tools and click <strong>Next</strong>.</li> <li>In the Available Software dialog, select the checkbox next to Developer Tools and click
<strong>Next</strong>.</li>
<li>In the next window, you'll see a list of the tools to be downloaded. Click <li>In the next window, you'll see a list of the tools to be downloaded. Click
<strong>Next</strong>. </li> <strong>Next</strong>. </li>
<li>Read and accept the license agreements, then click <strong>Finish</strong>.</li> <li>Read and accept the license agreements, then click <strong>Finish</strong>.
<p>Note: If you get a security warning saying that the authenticity or validity of
the software can't be established, click <strong>OK</strong>.</p></li>
<li>When the installation completes, restart Eclipse. </li> <li>When the installation completes, restart Eclipse. </li>
</ol> </ol>
<h3 id="configuring">Configuring the ADT Plugin</h3> <h3 id="configuring">Configuring the ADT Plugin</h3>
<p>Once you've successfully downloaded ADT as described above, the next step <p>After you've successfully downloaded the ADT as described above, the next step
is to modify your ADT preferences in Eclipse to point to the Android SDK directory:</p> is to modify your ADT preferences in Eclipse to point to the Android SDK directory:</p>
<ol> <ol>
<li>Select <strong>Window</strong> &gt; <strong>Preferences...</strong> to open the Preferences <li>Select <strong>Window</strong> &gt; <strong>Preferences...</strong> to open the Preferences
panel (Mac OS X: <strong>Eclipse</strong> &gt; <strong>Preferences</strong>).</li> panel (Mac OS X: <strong>Eclipse</strong> &gt; <strong>Preferences</strong>).</li>
<li>Select <strong>Android</strong> from the left panel. </li> <li>Select <strong>Android</strong> from the left panel.</li>
<p>You may see a dialog asking whether you want to send usage statistics to Google. If so,
make your choice and click <strong>Proceed</strong>. You cannot continue with this procedure until
you click <strong>Proceed</strong>.</p>
<li>For the <em>SDK Location</em> in the main panel, click <strong>Browse...</strong> and <li>For the <em>SDK Location</em> in the main panel, click <strong>Browse...</strong> and
locate your downloaded SDK directory. </li> locate your downloaded SDK directory. </li>
<li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li> <li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li>

169
docs/html/sdk/installing.jd
View File

@@ -81,9 +81,9 @@ this page.</p>
<h4>Updating?</h4> <h4>Updating?</h4>
<p>If you already have an Android SDK, use the <em>Android SDK and AVD Manager</em> tool to install <p>If you already have an Android SDK, use the Android SDK and AVD Manager tool to install
updated tools and new Android platforms into your existing environment. For information about how to updated tools and new Android platforms into your existing environment. For information about how to
do that, see <a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a></p> do that, see <a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a>.</p>
<h2 id="Preparing">Step 1. Preparing Your Development Computer</h2> <h2 id="Preparing">Step 1. Preparing Your Development Computer</h2>
@@ -126,7 +126,7 @@ install the SDK Tools into a default location (which you can modify).</p>
<p>Make a note of the name and location of the SDK directory on your system&mdash;you will need to <p>Make a note of the name and location of the SDK directory on your system&mdash;you will need to
refer to the SDK directory later, when setting up the ADT plugin and when using refer to the SDK directory later, when setting up the ADT plugin and when using
the SDK tools from command line.</p> the SDK tools from the command line.</p>
<h2 id="InstallingADT">Step 3. Installing the ADT Plugin for Eclipse</h2> <h2 id="InstallingADT">Step 3. Installing the ADT Plugin for Eclipse</h2>
@@ -147,26 +147,25 @@ step-by-step installation instructions, then return here to continue the
last step in setting up your Android SDK.</p> last step in setting up your Android SDK.</p>
<p>If you prefer to work in a different IDE, you do not need to <p>If you prefer to work in a different IDE, you do not need to
install Eclipse or ADT, instead, you can directly use the SDK tools to build and install Eclipse or ADT. Instead, you can directly use the SDK tools to build and
debug your application. The <a href="{@docRoot}guide/developing/index.html">Overview</a> debug your application. The <a href="{@docRoot}guide/developing/index.html">Introduction</a>
section of the developer guide outlines the major steps that you need to complete to Android application development outlines the major steps that you need to complete when
when developing in Eclipse or other IDEs.</p> developing in Eclipse or other IDEs.</p>
<h2 id="AddingComponents">Step 4. Adding Platforms and Other Components</h2> <h2 id="AddingComponents">Step 4. Adding Platforms and Other Components</h2>
<p>The last step in setting up your SDK is using the <em>Android SDK and AVD Manager</em> (a <p>The last step in setting up your SDK is using the Android SDK and AVD Manager (a
tool included in the SDK starter package) to download tool included in the SDK starter package) to download essential SDK components into your development
essential SDK components into your development environment.</p> environment.</p>
<p>The SDK uses a modular structure that separates the major parts of the SDK&mdash;Android platform <p>The SDK uses a modular structure that separates the major parts of the SDK&mdash;Android platform
versions, add-ons, tools, samples, and documentation&mdash;into a set of separately installable versions, add-ons, tools, samples, and documentation&mdash;into a set of separately installable
components. The SDK starter package, which you've already downloaded, includes only a single components. The SDK starter package, which you've already downloaded, includes only a single
component: the latest version of the SDK Tools. To develop an Android component: the latest version of the SDK Tools. To develop an Android application, you also need to
application, you also need to download at least one Android platform and the SDK Platform-tools download at least one Android platform and the associated platform tools. You can add other
(tools that the latest platform depend upon). However, downloading components and platforms as well, which is highly recommended.</p>
additional components is highly recommended.</p>
<p>If you used the Windows installer, when you complete the installation wizard, it will launch the <p>If you used the Windows installer, when you complete the installation wizard, it will launch the
Android SDK and AVD Manager with a default set of platforms and other components selected Android SDK and AVD Manager with a default set of platforms and other components selected
@@ -185,10 +184,10 @@ Android SDK, then execute: <pre>android</pre> </li>
</ul> </ul>
<p>To download components, use the graphical UI of the Android SDK and AVD <p>To download components, use the graphical UI of the Android SDK and AVD
Manager, shown in Figure 1, to browse the SDK repository and select new or updated Manager to browse the SDK repository and select new or updated
components. The Android SDK and AVD Manager will install the selected components in components (see figure 1). The Android SDK and AVD Manager installs the selected components in
your SDK environment. For information about which components you should download, see the following your SDK environment. For information about which components you should download, see <a
section about <a href="#which">Recommended Components</a>.</p> href="#which">Recommended Components</a>.</p>
<img src="/images/sdk_manager_packages.png" /> <img src="/images/sdk_manager_packages.png" />
<p class="img-caption"><strong>Figure 1.</strong> The Android SDK and AVD Manager's <p class="img-caption"><strong>Figure 1.</strong> The Android SDK and AVD Manager's
@@ -204,35 +203,34 @@ Repository</em> and <em>Third party Add-ons</em>.</p>
<p>The <em>Android Repository</em> offers these types of components:</p> <p>The <em>Android Repository</em> offers these types of components:</p>
<ul> <ul>
<li><strong>SDK Tools</strong> (pre-installed in the Android SDK starter <li><strong>SDK Tools</strong> &mdash; Contains tools for debugging and testing your application
package) &mdash; Contains tools for debugging and other utility tools. These tools are installed with the Android SDK starter package and receive
and testing your application and other utility tools. You can access these periodic updates. You can access these tools in the <code>&lt;sdk&gt;/tools/</code> directory of
in the <code>&lt;sdk&gt;/tools/</code> directory of your SDK and read more about them in the <a your SDK. To learn more about
href="{@docRoot}guide/developing/tools/index.html">Tools</a> section of the developer guide. </li> them, see <a href="{@docRoot}guide/developing/tools/index.html#tools-sdk">SDK Tools</a> in the
developer guide.</li>
<li><strong>SDK Platform-tools</strong> &mdash; Contains tools that are required to develop and <li><strong>SDK Platform-tools</strong> &mdash; Contains platform-dependent tools for developing
debug your application, but which are developed alongside the Android platform in order to support and debugging your application. These tools support the latest features of the Android platform and
the latest features. These tools are typically updated only when a new platform becomes are typically updated only when a new platform becomes available. You can access these tools in the
available. You can access these <code>&lt;sdk&gt;/platform-tools/</code> directory. To learn more about them, see <a
in the <code>&lt;sdk&gt;/platform-tools/</code> directory. Read more about them in href="{@docRoot}guide/developing/tools/index.html#tools-platform">Platform Tools</a> in the
the <a href="{@docRoot}guide/developing/tools/index.html">Tools</a> section of the developer guide. developer guide.</li>
</li>
<li><strong>Android platforms</strong> &mdash; An SDK platform is <li><strong>Android platforms</strong> &mdash; An SDK platform is
available for every production Android platform deployable to Android-powered available for every production Android platform deployable to Android-powered devices. Each
devices. Each platform component includes a fully compliant Android library and SDK platform component includes a fully compliant Android library, system image, sample code,
system image, sample code, emulator skins, and any version specific tools. For and emulator skins. To learn more about a specific platform, see the list of platforms that appears
detailed information about each platform, see the overview documents available under the section "Downloadable SDK Components" on the left part of this page.</li>
under the section "Downloadable SDK Components," at left. </li>
<li><strong>USB Driver for Windows</strong> (Windows only) &mdash; Contains driver files <li><strong>USB Driver for Windows</strong> (Windows only) &mdash; Contains driver files
that you can install on your Windows computer, so that you can run and debug that you can install on your Windows computer, so that you can run and debug
your applications on an actual device. You <em>do not</em> need the USB driver unless your applications on an actual device. You <em>do not</em> need the USB driver unless
you plan to debug your application on an actual Android-powered device. If you you plan to debug your application on an actual Android-powered device. If you
develop on Mac OS X or Linux, you do not need a special driver to debug develop on Mac OS X or Linux, you do not need a special driver to debug
your application on an Android-powered device. (See <a your application on an Android-powered device. See <a
href="{@docRoot}guide/developing/device.html">Developing on a Device</a> for more information href="{@docRoot}guide/developing/device.html">Using Hardware Devices</a> for more information
about developing on a real device.)</li> about developing on a real device.</li>
<li><strong>Samples</strong> &mdash; Contains the sample code and apps available <li><strong>Samples</strong> &mdash; Contains the sample code and apps available
for each Android development platform. If you are just getting started with for each Android development platform. If you are just getting started with
@@ -247,8 +245,8 @@ multiversion documentation for the Android framework API. </li>
<p>The <em>Third party Add-ons</em> provide components that allow you to create a development <p>The <em>Third party Add-ons</em> provide components that allow you to create a development
environment using a specific Android external library (such as the Google Maps library) or a environment using a specific Android external library (such as the Google Maps library) or a
customized (but fully compliant) Android system image. You can add additional Add-on repositories, customized (but fully compliant) Android system image. You can add additional Add-on repositories by
by clicking <strong>Add Add-on Site</strong>.</p> clicking <strong>Add Add-on Site</strong>.</p>
<h3 id="which">Recommended Components</h3> <h3 id="which">Recommended Components</h3>
@@ -381,12 +379,11 @@ file <code>offline.html</code> in a web browser.</td>
</tr> </tr>
<tr> <tr>
<td colspan="3"><code>platform-tools/</code></td> <td colspan="3"><code>platform-tools/</code></td>
<td>Contains development tools that may be updated with each platform release (from the <em>Android <td>Contains platform-dependent development tools that may be updated with each platform release.
SDK Platform-tools</em> component). Tools in here include {@code adb}, {@code dexdump}, and others The platform tools include the Android Debug Bridge ({@code adb}) as well as other tools that you
others that you don't typically use directly. These tools are separate from the generic development don't typically use directly. These tools are separate from the development tools in the {@code
tools in the {@code tools/} directory, because these tools may be updated in order to support new tools/} directory because these tools may be updated in order to support new
features in the latest Android platform, whereas the other tools have no dependencies on the features in the latest Android platform.</td>
platform version.</td>
</tr> </tr>
<tr> <tr>
<td colspan="3"><code>platforms/</code></td> <td colspan="3"><code>platforms/</code></td>
@@ -394,52 +391,12 @@ platform version.</td>
applications against, each in a separate directory. </td> applications against, each in a separate directory. </td>
</tr> </tr>
<tr> <tr>
<td style="width:2em;border-bottom-color:white;"></td> <td style="width:2em;"></td>
<td colspan="2"><code><em>&lt;platform&gt;</em>/</code></td> <td colspan="2"><code><em>&lt;platform&gt;</em>/</code></td>
<td>Platform version directory, for example "android-1.6". All platform version <td>Platform version directory, for example "android-11". All platform version directories contain
directories contain a similar set of files and subdirectory structure.</td> a similar set of files and subdirectory structure. Each platform directory also includes the
</tr> Android library (<code>android.jar</code>) that is used to compile applications against the
platform version.</td>
<tr>
<td style="width:2em;border-bottom-color:white;">&nbsp;</td>
<td style="width:2em;border-bottom-color:white;"></td>
<td><code>data/</code></td>
<td>Storage area for default fonts and resource definitions.</td>
</tr>
<tr>
<td style="width:2em;border-bottom-color:white;"></td>
<td style="width:2em;border-bottom-color:white;"></td>
<td><code>images/</code></td>
<td>Storage area for default disk images, including the Android system image,
the default userdata image, the default ramdisk image, and more. The images
are used in emulator sessions.</td>
</tr>
<tr>
<td style="width:2em;border-bottom-color:white;"></td>
<td style="width:2em;border-bottom-color:white;"></td>
<td><code>skins/</code></td>
<td>A set of emulator skins available for the platform version. Each skin is
designed for a specific screen resolution.</td>
</tr>
<tr>
<td style="width:2em;border-bottom-color:white;"></td>
<td style="width:2em;border-bottom-color:white;"></td>
<td><code>templates/</code></td>
<td>Storage area for file templates used by the SDK development tools.</td>
</tr>
<tr>
<td style="width:2em;border-bottom-color:white;"></td>
<td style="width:2em;border-bottom-color:white;"></td>
<td><code>tools/</code></td>
<td>This directory is used only by SDK Tools r7 and below for development tools that are specific to
this platform version&mdash;it's not used by SDK Tools r8 and above.</td>
</tr>
<tr>
<td style="width:2em;"></td>
<td style="width:2em;"></td>
<td><code>android.jar</code></td>
<td>The Android library used when compiling applications against this platform
version.</td>
</tr> </tr>
<tr> <tr>
<td colspan="3"><code>samples/</code></td> <td colspan="3"><code>samples/</code></td>
@@ -448,21 +405,20 @@ version.</td>
<tr> <tr>
<td colspan="3"><code>tools/</code></td> <td colspan="3"><code>tools/</code></td>
<td>Contains the set of development and profiling tools that are platform-independent, such <td>Contains the set of development and profiling tools that are platform-independent, such
as the emulator, the AVD and SDK Manager, ddms, hierarchyviewer and more. The tools in as the emulator, the Android SDK and AVD Manager, <code>ddms</code>, <code>hierarchyviewer</code>
this directory may be updated at any time (from the <em>Android SDK Tools</em> component), and more. The tools in this directory may be updated at any time using the Android SDK and AVD
independent of platform releases, whereas the tools in {@code platform-tools/} may be updated based Manager and are independent of platform releases.</td>
on the latest platform release.</td>
</tr> </tr>
<tr> <tr>
<td colspan="3"><code>SDK Readme.txt</code></td> <td colspan="3"><code>SDK Readme.txt</code></td>
<td>A file that explains how to perform the initial setup of your SDK, <td>A file that explains how to perform the initial setup of your SDK,
including how to launch the Android SDK and AVD Manager tool on all including how to launch the Android SDK and AVD Manager tool on all
platforms</td> platforms.</td>
</tr> </tr>
<tr> <tr>
<td colspan="3"><code>SDK Manager.exe</code></td> <td colspan="3"><code>SDK Manager.exe</code></td>
<td>Windows SDK only. A shortcut that launches the Android SDK and AVD <td>Windows SDK only. A shortcut that launches the Android SDK and AVD
Manager tool, which you use to add components to your SDK. </td> Manager tool, which you use to add components to your SDK.</td>
</tr> </tr>
<!--<tr> <!--<tr>
<td colspan="3"><code>documentation.html</code></td> <td colspan="3"><code>documentation.html</code></td>
@@ -499,7 +455,7 @@ include these directories in your PATH in the following way:</p>
<li>On Linux, edit your <code>~/.bash_profile</code> or <code>~/.bashrc</code> file. Look <li>On Linux, edit your <code>~/.bash_profile</code> or <code>~/.bashrc</code> file. Look
for a line that sets the PATH environment variable and add the for a line that sets the PATH environment variable and add the
full path to the <code>tools/</code> and <code>platform-tools</code> directories to it. If you full path to the <code>tools/</code> and <code>platform-tools/</code> directories to it. If you
don't see a line setting the path, you can add one: don't see a line setting the path, you can add one:
<pre>export PATH=${PATH}:&lt;sdk&gt;/tools:&lt;sdk&gt;/platform-tools</pre> <pre>export PATH=${PATH}:&lt;sdk&gt;/tools:&lt;sdk&gt;/platform-tools</pre>
</li> </li>
@@ -533,28 +489,27 @@ first step in getting started with Android development. </p>
<p><strong>Learn about Android</strong></p> <p><strong>Learn about Android</strong></p>
<ul> <ul>
<li>Take a look at the <a href="{@docRoot}guide/index.html">Dev <li>Take a look at the <a href="{@docRoot}guide/index.html">Dev
Guide</a> and the types of information it provides</li> Guide</a> and the types of information it provides.</li>
<li>Read an introduction to Android as a platform in <a <li>Read an introduction to Android as a platform in <a
href="{@docRoot}guide/basics/what-is-android.html">What is href="{@docRoot}guide/basics/what-is-android.html">What is
Android?</a></li> Android?</a></li>
<li>Learn about the Android framework and how applications run on it in <li>Learn about the Android framework and how applications run on it in
<a href="{@docRoot}guide/topics/fundamentals.html">Application <a href="{@docRoot}guide/topics/fundamentals.html">Application
Fundamentals</a></li> Fundamentals</a>.</li>
<li>Take a look at the Android framework API specification in the <a <li>Take a look at the Android framework API specification in the <a
href="{@docRoot}reference/packages.html">Reference</a> tab</li> href="{@docRoot}reference/packages.html">Reference</a> tab.</li>
</ul> </ul>
<p><strong>Explore the development tools</strong></p> <p><strong>Explore the development tools</strong></p>
<ul> <ul>
<li>Get an overview of the <a <li>Get an overview of the <a
href="{@docRoot}guide/developing/tools/index.html">development href="{@docRoot}guide/developing/tools/index.html">development
tools</a> that are available to you</li> tools</a> that are available to you.</li>
<li>Read the <a <li>Read the <a href="{@docRoot}guide/developing/index.html">Introduction</a> to Android
href="{@docRoot}guide/developing/index.html">Overview</a> application development.
for how to develop an Android application.
</li> </li>
<li>Read <a href="{@docRoot}guide/developing/device.html">Developing on a Device</a> to set up an <li>Read <a href="{@docRoot}guide/developing/device.html">Using Hardware Devices</a> to learn
Android-powered device to run and test your application.</li> how to set up an Android-powered device so you can run and test your application.</li>
</ul> </ul>
<p><strong>Follow the Notepad tutorial</strong></p> <p><strong>Follow the Notepad tutorial</strong></p>