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

Merge "Doc change: fixing links set 2"

Browse Source
This commit is contained in:
Robert Ly
2011-01-06 17:23:58 -08:00
committed by Android (Google) Code Review
parent 6a74aaaea3 1bcc56db07
commit fb892bdca4
17 changed files with 60 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/html/guide/appendix/api-levels.jd
View File

@@ -294,12 +294,11 @@ Manager</strong>.</p>
<p>To run your application against different platform versions in the emulator,
create an AVD for each platform version that you want to test. For more
information about AVDs, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>. If
href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>. If
you are using a physical device for testing, ensure that you know the API Level
of the Android platform it runs. See the table at the top of this document for
a list of platform versions and their API Levels. </p>
<h2 id="provisional">Using a Provisional API Level</h2>
<p>In some cases, an "Early Look" Android SDK platform may be available. To let

3
docs/html/guide/appendix/glossary.jd
View File

@@ -91,8 +91,7 @@ page.title=Glossary
with the SDK. It provides screen capture, log dump, and process
examination capabilities. If you are developing in Eclipse using the ADT
Plugin, DDMS is integrated into your development environment. See <a
href="{@docRoot}guide/developing/tools/ddms.html">Dalvik Debug Monitor
Server</a> to learn more about the program.</dd>
href="{@docRoot}guide/developing/debugging/ddms.html">Using DDMS</a> to learn more about the program.</dd>
<dt id="dialog">Dialog</dt> <dd> A floating window that that acts as a lightweight
form. A dialog can have button controls only and is intended to perform a

3
docs/html/guide/developing/building/index.jd
View File

@@ -1,4 +1,4 @@
page.title=Building and Running Applications
page.title=Building and Running Apps
@jd:body
<div id="qv-wrapper">
@@ -54,6 +54,7 @@ page.title=Building and Running Applications
<p>The general process for a typical build is outlined below:</p>
<ul>
<li>The Android Asset Packaging Tool (aapt) takes your application resource files, such as the
<code>AndroidManifest.xml</code> file and the XML files for your Activities, and compiles them. An <code>R.java</code> is
also produced so you can reference your resources from your Java code.</li>

9
docs/html/guide/developing/debugging/debugging-ui.jd
View File

@@ -9,9 +9,10 @@ page.title=Debugging and Profiling User Interfaces
<li>
<a href="#hierarchyViewer">Debugging and Optimizing User Interfaces with Hierarchy
Viewer</a>
<ul>
<ol>
<li><a href="#layoutview">Layout View</a></li>
<li><a href="#pixelperfect">Pixel Perfect View</a></li>
</ol>
</li>
<li><a href="#layoutopt">Optimizing Layouts with <code>layoutopt</code></a></li>
@@ -94,7 +95,7 @@ page.title=Debugging and Profiling User Interfaces
automatically refresh. You must reload the Layout View by clicking <strong>Load View
Hierarchy</strong>.</p>
<h3>Pixel Perfect View</h3>
<h3 id="pixelperfect">Pixel Perfect View</h3>
<p>The Pixel Perfect View provides a magnified look at the current device window. It helps you
design your UI better by giving you a closer look at your UI's image quality, alignment, and other
@@ -190,7 +191,7 @@ samples/useless.xml
<p>
For more information on running the tool, see the
<a href="${@docRoot}guide/developing/tools/layoutopt.html">layoutopt</a> reference.</p>
<a href="${@docRoot}guide/developing/debugging/debugging-ui.html#layoutopt">layoutopt</a> reference.</p>

10
docs/html/guide/developing/debugging/index.jd
View File

@@ -32,19 +32,19 @@ page.title=Debugging
UNIX shell on the device or emulator, and providing a general means to communicate with
connected emulators and devices.</dd>
<dt><a href="{@docRoot}guide/developing/tools/ddms.html"><strong>Dalvik Debug Monitor
<dt><a href="{@docRoot}guide/developing/debugging/ddms.html"><strong>Dalvik Debug Monitor
Server</strong></a></dt>
<dd>DDMS is a graphical program that communicates with your devices through <code>adb</code>. DDMS can
capture screenshots, gather thread and stack information, spoof incoming calls and SMS
messages, and has many other features.</dd>
<dt><a href="{@docRoot}guide/developing/devices/avds-devices.html"><strong>Device or
Emulator</strong></a></dt>
<dt><strong><a href="{@docRoot}guide/developing/device.html">Device</a> or
<a href="{@docRoot}guide/developing/devices/index.html">Android Virtual Device</a></strong></dt>
<dd>Your application must run in a device or emulator so that it can be debugged. An <code>adb</code> device
<dd>Your application must run in a device or in an AVD so that it can be debugged. An <code>adb</code> device
daemon runs on the device or emulator and provides a means for the <code>adb</code> host daemon to
communicate with the device.</dd>
communicate with the device or emulator.</dd>
<dt><strong>JDWP debugger</strong></dt>

38
docs/html/guide/developing/devices/emulator.jd
View File

@@ -33,7 +33,6 @@ page.title=Using the Android Emulator
</div>
</div>
<img src="/images/emulator-wvga800l.png" alt="Image of the Android Emulator"
width="367" height="349" style="margin-left:2em;float:right;"/>
<p>The Android SDK includes a virtual mobile device emulator
@@ -119,9 +118,10 @@ user data, SD card, and so on. When you launch the emulator with an AVD configur
it automatically loads the user data and SD card data from the AVD directory. By default,
the emulator stores the user data, SD card data, and cache in the AVD directory.</p>
<p>To create and manage AVDs you use the android tool, a command-line utility
included in the SDK. For complete information about how to set up AVDs, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>.</p>
<p>To create and manage AVDs you use the AVD Manager UI or the <code>android</code> tool
that is included in the SDK.
For complete information about how to set up AVDs, see <a
href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>.</p>
<a name="starting"></a>
@@ -352,8 +352,8 @@ Here's the command-line usage for launching the emulator with options: </p>
<td><strong>Required</strong>. Specifies the AVD to load for this emulator
instance.</td>
<td>You must create an AVD configuration before launching the emulator. For
information, see <a href="{@docRoot}guide/developing/tools/avd.html">Android
Virtual Devices</a>.</td>
information, see <a href="{@docRoot}guide/developing/devices/managing-avds.html">Creating and Managing
Virtual Devices with AVD Manager</a>.</td>
<tr>
<td rowspan="7">Disk Images</td>
<td><code>-cache&nbsp;&lt;filepath&gt;</code></td>
@@ -708,7 +708,8 @@ option. Using this option may yield unexpected and in some cases misleading
results, since the density with which to render the skin may not be defined.
AVDs let you associate each skin with a default density and override the default
as needed. For more information, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>.
href="{@docRoot}guide/developing/devices/managing-avds.html">Creating and Managing Virtual Devices
with AVD Manager</a>.
</td>
</tr>
<tr>
@@ -718,15 +719,6 @@ href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>.
</table>
<a name="diskimages"></a>
<h2>Working with Emulator Disk Images</h2>
@@ -892,7 +884,7 @@ emulated SD card and load it in the emulator, see <a href="#sdcard">SD Card Emul
<p>You can also use the android tool to automatically create an SD Card image
for you, when creating an AVD. For more information, see <a
href="{@docRoot}guide/developing/tools/avd.html#options">Command-line options for AVDs</a>.
href="{@docRoot}guide/developing/devices/managing-avds.html">Creating and Managing Virtual Devices with AVD Manager</a>.
<a name="temporaryimages"></a>
<h3>Temporary Images</h3>
@@ -1643,7 +1635,7 @@ kilobits/sec):</p>
<h2>Using Emulator Skins</h2>
<p>The Android SDK includes several Emulator skins that you can use to control the resolution and density of the emulated device's screen. To select a specific skin for running the emulator, create an AVD that uses that skin. Please do not use deprecated emulator options such as <code>-skin</code> to control the skin used by an emulator instance. For more information about AVDs, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>. </p>
href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>.</p>
<a name="multipleinstances"></a>
@@ -1662,9 +1654,9 @@ instance-specific storage area. </p>
<p>If you don't have access to Eclipse or the ADT Plugin, you can install
your application on the emulator <a href="{@docRoot}guide/developing/tools/adb.html#move">using
the adb utility</a>. Before installing the application, you need to package it
in a .apk file using the <a href="{@docRoot}guide/developing/tools/aapt.html">Android Asset Packaging Tool</a>.
Once the application is installed, you can start the emulator from the command
the adb utility</a>. Before installing the application, you need to build and package it
into an <code>.apk</code> as described in <a href="{@docRoot}guide/developing/building/index.html">Building and
Running Apps</a>. Once the application is installed, you can start the emulator from the command
line, as described in this document, using any startup options necessary.
When the emulator is running, you can also connect to the emulator instance's
console to issue commands as needed.</p>
@@ -1707,7 +1699,7 @@ creating an AVD, you simply specify the <code>-c</code> option, like this: </p>
<p>You can also use the <code>-c</code> option to specify a path to an SD card
image to use in the new AVD. For more information, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>.
href="{@docRoot}guide/developing/devices/managing-avds-cmdline.html">Creating and Managing Virtual Devices on the Command Line</a>.
</p>
<h3 id="creatingm">Creating an SD card image using mksdcard</h3>
@@ -1722,7 +1714,7 @@ the tools/ directory of the SDK and create a disk image like this: </p>
<pre>mksdcard 1024M sdcard1.iso</pre>
<p>For more information, see <a href="{@docRoot}guide/developing/tools/othertools.html">Other Tools</a>. </p>
<p>For more information, see <a href="{@docRoot}guide/developing/tools/mksdcard.html"><code>mksdcard</code></a>.</p>
<a name="copying"></a>
<h3>Copying Files to a Disk Image</h3>

5
docs/html/guide/developing/tools/adb.jd
View File

@@ -171,7 +171,7 @@ emulator-5558&nbsp;&nbsp;device</pre>
<pre>adb install &lt;path_to_apk&gt;</pre>
<p>For more information about how to create an .apk file that you can install on an emulator/device instance, see <a href="{@docRoot}guide/developing/tools/aapt.html">Android Asset Packaging Tool</a> (aapt). </p>
<p>For more information about how to create an .apk file that you can install on an emulator/device instance, see <a href="{@docRoot}guide/developing/building/index.html">Building and Running Apps</a></p>
<p>Note that, if you are using the Eclipse IDE and have the ADT plugin installed, you do not need to use adb (or aapt) directly to install your application on the emulator/device. Instead, the ADT plugin handles the packaging and installation of the application for you. </p>
@@ -465,7 +465,8 @@ application and send 500 pseudo-random events to it.</p>
<tr>
<td><code>dumpsys</code></td>
<td>Dumps system data to the screen.</td>
<td rowspan=4">The <a href="{@docRoot}guide/developing/tools/ddms.html">Dalvik Debug Monitor Service</a> (DDMS) tool offers integrated debug environment that you may find easier to use.</td>
<td rowspan=4">The <a href="{@docRoot}guide/developing/debugging/ddms.html">Dalvik Debug Monitor Server</a>
(DDMS) tool offers integrated debug environment that you may find easier to use.</td>
</tr>
<tr>

9
docs/html/guide/developing/tools/emulator.jd
View File

@@ -12,7 +12,7 @@ invoke certain keys on the device. </p>
<p>This document is a reference to the available command line options and the keyboard mapping to device keys.
For a complete guide to using the Android Emulator, see
<a href="${@docRoot}guide/developing/devices/emulator.html">Using the Android Emulator</a>.
<a href="{@docRoot}guide/developing/devices/emulator.html">Using the Android Emulator</a>.
<h2 id="startup-options">Emulator Startup Options</h2>
@@ -85,8 +85,8 @@ Here's the command-line usage for launching the emulator with options: </p>
<td><strong>Required</strong>. Specifies the AVD to load for this emulator
instance.</td>
<td>You must create an AVD configuration before launching the emulator. For
information, see <a href="{@docRoot}guide/developing/tools/avd.html">Android
Virtual Devices</a>.</td>
information, see <a href="{@docRoot}guide/developing/devices/managing-avds.html#createavd">
Creating and Managing AVDs with AVD Manager</a>.</td>
<tr>
<td rowspan="7">Disk Images</td>
<td><code>-cache&nbsp;&lt;filepath&gt;</code></td>
@@ -439,7 +439,8 @@ option. Using this option may yield unexpected and in some cases misleading
results, since the density with which to render the skin may not be defined.
AVDs let you associate each skin with a default density and override the default
as needed. For more information, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>.
href="{@docRoot}guide/developing/devices/managing-avds.html#createavd">
Creating and Managing Virtual Devices with AVD Manager</a>.
</td>
</tr>
<tr>

4
docs/html/guide/practices/screens_support.jd
View File

@@ -38,7 +38,7 @@ page.title=Supporting Multiple Screens
<li><a
href="{@docRoot}guide/topics/resources/providing-resources.html#AlternativeResources">
Providing Alternative Resources</a></li>
<li><a href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a></li>
<li><a href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a></li>
</ol>
</div>
@@ -1205,7 +1205,7 @@ includes several emulator skins to get you started. You can use the Android AVD
Manager or the <code>android</code> tool to create AVDs that use the various
emulator skins and you can also set up custom AVDs to test densities other than
the defaults. For general information about working with AVDs, see
<a href="{@docRoot}guide/developing/tools/avd.html">Android Virtual
<a href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual
Devices</a>.</p>
<p>The Android SDK provides a set of default emulator skins that you can use for

9
docs/html/guide/topics/fundamentals.jd
View File

@@ -52,10 +52,9 @@ page.title=Application Fundamentals
<p>
Android applications are written in the Java programming language.
The compiled Java code &mdash; along with any data and resource
files required by the application &mdash; is bundled by the
<a href="{@docRoot}guide/developing/tools/aapt.html"><code>aapt</code>
tool</a> into an <i>Android package</i>, an archive file
marked by an {@code .apk} suffix. This file is the vehicle
files required by the application &mdash; is bundled into an
<i>Android package</i>, an archive file
marked by an {@code .apk} suffix. This file is the vehicle
for distributing the application and installing it on mobile devices;
it's the file users download to their devices. All the code in a
single {@code .apk} file is considered to be one <i>application</i>.
@@ -425,7 +424,7 @@ elements for broadcast receivers, and
<code><a href="{@docRoot}guide/topics/manifest/provider-element.html">&lt;provider&gt;</a></code>
elements for content providers. Activities, services, and content providers
that are not declared in the manifest are not visible to the system and are
consequently never run. However, broadcast receivers can either be
consequently never run. However, broadcast receivers can either be
declared in the manifest, or they can be created dynamically in code
(as {@link android.content.BroadcastReceiver} objects)
and registered with the system by calling

2
docs/html/guide/topics/graphics/2d-graphics.jd
View File

@@ -61,7 +61,7 @@ extension (E.g., <code>my_image.png</code> is referenced as <var>my_image</var>)
<p class="note"><strong>Note:</strong> Image resources placed in <code>res/drawable/</code> may be
automatically optimized with lossless image compression by the
<a href="{@docRoot}guide/developing/tools/aapt.html">aapt</a> tool. For example, a true-color PNG that does
<code>aapt</code> tool during the build process. For example, a true-color PNG that does
not require more than 256 colors may be converted to an 8-bit PNG with a color palette. This
will result in an image of equal quality but which requires less memory. So be aware that the
image binaries placed in this directory can change during the build. If you plan on reading

6
docs/html/guide/topics/location/obtaining-user-location.jd
View File

@@ -421,8 +421,8 @@ lat/long coordinates, with a GPX file for route playback, or a KML file for mult
<li>Use a KML file describing individual place marks for sequenced playback to the device.</li>
</ul>
<p>For more information on using DDMS to spoof location data, see the
<a href="{@docRoot}guide/developing/tools/ddms.html#emulator-control">Using DDMS guide</a>.
<p>For more information on using DDMS to spoof location data, see
<a href="{@docRoot}guide/developing/debugging/ddms.html">Using DDMS</a>.
<h3 id="MockGeo">Using the "geo" command in the emulator console</h3>
@@ -451,4 +451,4 @@ lat/long coordinates, with a GPX file for route playback, or a KML file for mult
</ol>
<p>For information about how to connect to the emulator console, see
<a href="{@docRoot}guide/developing/tools/emulator.html#console">Using the Emulator Console</a>.</p>
<a href="{@docRoot}guide/developing/devices/emulator.html#console">Using the Emulator Console</a>.</p>

2
docs/html/guide/topics/resources/drawable-resource.jd
View File

@@ -74,7 +74,7 @@ android:drawable="@color/green"}).</p>
alias resource ID in XML.</p>
<p class="note"><strong>Note:</strong> Bitmap files may be automatically optimized with lossless
image compression by the <a href="{@docRoot}guide/developing/tools/aapt.html">aapt</a> tool. For
image compression by the <code>aapt</code> tool during the build process. For
example, a true-color PNG that does not require more than 256 colors may be converted to an 8-bit
PNG with a color palette. This will result in an image of equal quality but which requires less
memory. So be aware that the image binaries placed in this directory can change during the build. If

5
docs/html/guide/topics/testing/testing_android.jd
View File

@@ -625,9 +625,8 @@ The <a href="{@docRoot}guide/developing/tools/monkey.html">UI/Application Exerci
</p>
<p>
When possible, you should run these tests on an actual device. If this is not possible, you can
use the <a href="{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a> with
<a href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a> configured for
the hardware, screens, and versions you want to test.
use the <a href="{@docRoot}guide/developing/devices/emulator.html">Android Emulator</a> with
Android Virtual Devices configured for the hardware, screens, and versions you want to test.
</p>
<h2 id="NextSteps">Next Steps</h2>
<p>

4
docs/html/guide/topics/ui/declaring-layout.jd
View File

@@ -47,11 +47,11 @@ application can create View and ViewGroup objects (and manipulate their properti
Plugin for Eclipse</a> offers a layout preview of your XML &mdash;
with the XML file opened, select the <strong>Layout</strong> tab.</li>
<li>You should also try the
<a href="{@docRoot}guide/developing/tools/hierarchy-viewer.html">Hierarchy Viewer</a> tool,
<a href="{@docRoot}guide/developing/debugging/debugging-ui.html#hierarchyViewer">Hierarchy Viewer</a> tool,
for debugging layouts &mdash; it reveals layout property values,
draws wireframes with padding/margin indicators, and full rendered views while
you debug on the emulator or device.</li>
<li>The <a href="{@docRoot}guide/developing/tools/layoutopt.html">layoutopt</a> tool lets
<li>The <a href="{@docRoot}guide/developing/debugging/debugging-ui.html#layoutopt">layoutopt</a> tool lets
you quickly analyze your layouts and hierarchies for inefficiencies or other problems.</li>
</div>
</div>

6
docs/html/guide/webapps/debugging.jd
View File

@@ -18,7 +18,7 @@ messages</li>
<h2>See also</h2>
<ol>
<li><a href="{@docRoot}guide/developing/debug-tasks.html">Debugging Tasks</a></li>
<li><a href="{@docRoot}guide/developing/debugging/index.html">Debugging</a></li>
</ol>
</div>
@@ -46,8 +46,8 @@ those written using JavaScript {@code console} APIs.</p>
<strong>Device > Run logcat</strong>. When using the <a href="{@docRoot}sdk/eclipse-adt.html">ADT
plugin for Eclipse</a>, you can also view logcat messages by opening the Logcat view, available from
<strong>Window > Show View > Other > Android > Logcat</strong>.</p>
<p>See <a href="{@docRoot}guide/developing/debug-tasks.html">Debugging
Tasks</a> for more information about logcat.</p>
<p>See <a href="{@docRoot}guide/developing/debugging/debugging-log.html">Debugging</a>
for more information about <codelogcat</code>.</p>
</div>
</div>

11
docs/html/sdk/RELEASENOTES.jd
View File

@@ -64,7 +64,7 @@ changes include: </p>
skins. </li>
<li>Android SDK and AVD Manager, a graphical UI to let you manage your
SDK and AVD environments more easily. The tool lets you create and manage
your <a href="{@docRoot}guide/developing/tools/avd.html">Android Virtual
your <a href="{@docRoot}guide/developing/devices/managing-avds.html">Android Virtual
Devices</a> and download new SDK packages (such as platform versions and
add-ons) into your environment.</li>
<li>Improved support for test packages in New Project Wizard</li>
@@ -222,7 +222,7 @@ skins, including: </p>
density for each skin, to create any combination of resolution/density (WVGA
with medium density, for instance). To do so, use the <code>android</code> tool
command line to create a new AVD that uses a custom hardware configuration. See
<a href="{@docRoot}guide/developing/tools/avd.html#createavd">Creating an
<a href="{@docRoot}guide/developing/devices/managing-avds.html#createavd">Creating an
AVD</a> for more information.</p>
<h3>Other Notes and Resolved Issues</h3>
@@ -330,7 +330,7 @@ changes include: </p>
Android 1.5). The tools are updated to let you deploy your application
on any platform in the SDK, which helps you ensure forward-compatibility and,
if applicable, backward-compatibility.</li>
<li>Introduces <a href="{@docRoot}guide/developing/tools/avd.html">Android
<li>Introduces <a href="{@docRoot}guide/developing/devices/managing-avds.html">Android
Virtual Devices</a> &mdash; (AVD) configurations of options that you
run in the emulator to better model actual devices. Each AVD gets its
own dedicated storage area, making it much easier to work with multiple emulators
@@ -407,7 +407,7 @@ that can run in the emulator.
available to use.</p>
<p>For more information about AVDs, see <a
href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>
href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>
<h3>Other Notes</h3>
@@ -585,8 +585,7 @@ these USB drivers that you can install, to let you develop on the device:</p>
<p>The USB driver files are located in the
<code>&lt;SDK&gt;/usb_driver</code> directory. For details and
installation instructions, see <a
href="{@docRoot}guide/developing/device.html#setting-up">Setting Up a
Device for Development</a>.</p>
href="{@docRoot}guide/developing/device.html#setting-up">Connecting Hardware Devices</a>.</p>
</p>
<h3>Resolved Issues, Changes</h3>