diff --git a/docs/html/guide/developing/building/building-cmdline.jd b/docs/html/guide/developing/building/building-cmdline.jd index f40ad045414e8..a5ab07dbaaed0 100644 --- a/docs/html/guide/developing/building/building-cmdline.jd +++ b/docs/html/guide/developing/building/building-cmdline.jd @@ -1,4 +1,4 @@ -page.title=Building and Running Apps on the Command Line +page.title=Building and Running from the Command Line @jd:body
Note: When installing JDK on Windows, the default is to install
in the "Program Files" directory. This location will cause ant to fail, because of
the space. To fix the problem, you can specify the JAVA_HOME variable like this:
-
set JAVA_HOME=c:\Progra~1\Java\<jdkdir> -+
set JAVA_HOME=c:\Progra~1\Java\<jdkdir>- The easiest solution, however, is to install JDK in a non-space directory, for example: +
The easiest solution, however, is to install JDK in a non-space directory, for example:
c:\java\jdk1.6.0_02diff --git a/docs/html/guide/developing/building/building-eclipse.jd b/docs/html/guide/developing/building/building-eclipse.jd index 2c610c141cbca..11b9fec5dc5ba 100644 --- a/docs/html/guide/developing/building/building-eclipse.jd +++ b/docs/html/guide/developing/building/building-eclipse.jd @@ -1,4 +1,4 @@ -page.title=Building and Running Apps in Eclipse +page.title=Building and Running from Eclipse @jd:body
Read Connecting Hardware Devices +
Read Using Hardware Devices for more information.
Once set up and your device is connected via USB, install your application on the device by diff --git a/docs/html/guide/developing/building/index.jd b/docs/html/guide/developing/building/index.jd index 25a6e2317e178..59c46452a70d0 100644 --- a/docs/html/guide/developing/building/index.jd +++ b/docs/html/guide/developing/building/index.jd @@ -1,4 +1,4 @@ -page.title=Building and Running Apps +page.title=Building and Running @jd:body

The general process for a typical build is outlined below:
diff --git a/docs/html/guide/developing/debugging/debugging-devtools.jd b/docs/html/guide/developing/debugging/debugging-devtools.jd index 88e6005c00c97..67605aee530ea 100644 --- a/docs/html/guide/developing/debugging/debugging-devtools.jd +++ b/docs/html/guide/developing/debugging/debugging-devtools.jd @@ -59,8 +59,9 @@ adb -d install Development.apk android.app.Activity#onSaveInstanceState} / {@link android.app.Activity#onCreate(android.os.Bundle)} code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application - due to not saving state. For more information about saving an application's state, see - Handling Runtime Changes. + due to not saving state. For more information about saving an activity's state, see the + Activities +document.To create and manage AVDs you use the AVD Manager UI or the android tool
that is included in the SDK.
For complete information about how to set up AVDs, see Creating and Managing Virtual Devices.
You can also use the android tool to automatically create an SD Card image for you, when creating an AVD. For more information, see Creating and Managing Virtual Devices with AVD Manager. +href="{@docRoot}guide/developing/devices/managing-avds.html">Managing Virtual Devices with AVD +Manager
.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 -skin to control the skin used by an emulator instance. For more information about AVDs, see Creating and Managing Virtual Devices.
-c option, like this:
You can also use the -c option to specify a path to an SD card
image to use in the new AVD. For more information, see Creating and Managing Virtual Devices on the Command Line.
+href="{@docRoot}guide/developing/devices/managing-avds-cmdline.html">Managing Virtual Devices
+from the Command Line.
You can also create AVDs on the command line by passing the android tool options.
For more information on how to create AVDs in this manner, see Creating and Managing Virtual
- Devices on the Command Line.
An AVD consists of:
@@ -66,10 +66,10 @@ page.title=Creating and Managing Virtual DevicesTo learn how to manage AVDs using a graphical tool, read - Creating and Managing AVDs with AVD Manager. To learn how to manage AVDs on the command line, read - Creating and Managing AVDs - on the Command Line.
+ "{@docRoot}guide/developing/devices/managing-avds.html">Managing AVDs with AVD Manager. To +learn how to manage AVDs on the command line, read + Managing AVDs + from the Command Line. diff --git a/docs/html/guide/developing/devices/managing-avds-cmdline.jd b/docs/html/guide/developing/devices/managing-avds-cmdline.jd index 878ccc9a86c21..02fd7503d08da 100644 --- a/docs/html/guide/developing/devices/managing-avds-cmdline.jd +++ b/docs/html/guide/developing/devices/managing-avds-cmdline.jd @@ -1,4 +1,4 @@ -page.title=Creating and Managing AVDs on the Command Line +page.title=Managing AVDs from the Command Line @jd:bodyDeveloping applications for Android devices is facilitated by a group of tools that are @@ -28,8 +28,9 @@ page.title=Overview
You need to create Android Virtual Devices (AVD) or connect hardware devices on which you will install your applications.
-See Creating and Managing Virtual Devices - and Connecting Hardware Devices for more information. +
See Managing Virtual Devices + and Using Hardware Devices for more +information.
To build an application project that depends on one or more library projects, you can use the standard Ant build commands and compile modes, as described in Building Your Application, earlier in this - document. The tools compile and merge all libraries referenced by the application as part of + "{@docRoot}guide/developing/building/index.html">Building and Running. The tools +compile and merge all libraries referenced by the application as part of compiling the dependent application project. No additional commands or steps are necessary.
diff --git a/docs/html/guide/developing/projects/projects-eclipse.jd b/docs/html/guide/developing/projects/projects-eclipse.jd index 949e6f7accc3e..6070dc06a6496 100644 --- a/docs/html/guide/developing/projects/projects-eclipse.jd +++ b/docs/html/guide/developing/projects/projects-eclipse.jd @@ -1,4 +1,4 @@ -page.title=Creating and Managing Projects in Eclipse +page.title=Managing Projects from Eclipse @jd:bodyIf you are not developing in Eclipse or you want to learn how to create and run tests from the command line, see - Testing in Other IDEs. + Testing from Other IDEs.
diff --git a/docs/html/guide/developing/testing/testing_otheride.jd b/docs/html/guide/developing/testing/testing_otheride.jd index 48fa032c69cef..50cc4fa0fab87 100644 --- a/docs/html/guide/developing/testing/testing_otheride.jd +++ b/docs/html/guide/developing/testing/testing_otheride.jd @@ -1,4 +1,4 @@ -page.title=Testing In Other IDEs +page.title=Testing from Other IDEs @jd:body
@@ -133,7 +133,7 @@ android create test-project -m <main_path> -n <project_name> -p < This creates a new test project with the appropriate directories and build files. The directory structure and build file contents are identical to those in a regular Android application project. They are described in detail in the topic - Creating and Managing Projects. + Managing Projects.
The operation also creates an AndroidManifest.xml file with instrumentation
diff --git a/docs/html/guide/developing/tools/adb.jd b/docs/html/guide/developing/tools/adb.jd
index bcdc2e612758f..26839a180bc79 100644
--- a/docs/html/guide/developing/tools/adb.jd
+++ b/docs/html/guide/developing/tools/adb.jd
@@ -171,7 +171,8 @@ emulator-5558 device
adb install <path_to_apk>-
For more information about how to create an .apk file that you can install on an emulator/device instance, see Building and Running Apps
+For more information about how to create an .apk file that you can install on an emulator/device +instance, see Building and Running
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.
diff --git a/docs/html/guide/developing/tools/android.jd b/docs/html/guide/developing/tools/android.jd index ebf95ce693743..15cf8e0cf472b 100644 --- a/docs/html/guide/developing/tools/android.jd +++ b/docs/html/guide/developing/tools/android.jd @@ -5,11 +5,11 @@ page.title=android-cache <filepath>
This document is a reference to the available command line options. For more information and sample -output of the tool, see -Optimizing layouts with layoutopt.
+output of the tool, see Optimizing layouts with +layoutopt.logcat from an ADB shell to view the log messages.
This document is a reference to the available command line options. For more information on logcat, see
- Reading and Writing Log Messages. For more
+ Reading and Writing Logs.
+For more
information on accessing logcat from DDMS, instead of the command line, see the documentation for the
Dalvik Debug Monitor Server.
mksdcard
+ The following table describes the command-line options of mksdcard
| Option | @@ -50,4 +50,4 @@ mksdcard -l <label> <size> <file>
|---|