diff options
Diffstat (limited to 'docs/html/guide/developing/tools')
| -rw-r--r-- | docs/html/guide/developing/tools/adb.jd | 49 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adt.jd | 154 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adt_download.jd | 65 | ||||
| -rw-r--r--[-rwxr-xr-x] | docs/html/guide/developing/tools/aidl.jd | 9 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/ddms.jd | 16 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/draw9patch.jd | 11 | ||||
| -rw-r--r--[-rwxr-xr-x] | docs/html/guide/developing/tools/emulator.jd | 148 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/hierarchy-viewer.jd | 5 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/index.jd | 116 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/monkey.jd | 4 | ||||
| -rw-r--r--[-rwxr-xr-x] | docs/html/guide/developing/tools/othertools.jd | 8 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/traceview.jd | 6 |
12 files changed, 414 insertions, 177 deletions
diff --git a/docs/html/guide/developing/tools/adb.jd b/docs/html/guide/developing/tools/adb.jd index 25b5e29..50fb024 100644 --- a/docs/html/guide/developing/tools/adb.jd +++ b/docs/html/guide/developing/tools/adb.jd @@ -1,14 +1,45 @@ page.title=Android Debug Bridge @jd:body -<p>Android Debug Bridge (adb) is a versatile tool that lets you manage the state of a device or <a href="{@docRoot}reference/emulator.html">emulator</a>. </p> +<div id="qv-wrapper"> +<div id="qv"> + <h2>ADB quickview</h2> + <ul> +<li>Manage the state of an emulator or device</li> +<li>Run shell commands on a device</li> +<li>Manage port forwarding on an emulator or device</li> +<li>Copy files to/from an emulator or device</li> + </ul> + + <h2>In this document</h2> + <ol> +<li><a href="#issuingcommands">Issuing ADB Commands</a></li> +<li><a href="#devicestatus">Querying for Emulator/Device Instances</a></li> +<li><a href="#directingcommands">Directing Commands to a Specific Emulator/Device Instance</a></li> +<li><a href="#move">Installing an Application</a></li> +<li><a href="#forwardports">Forwarding Ports</a></li> +<li><a href="#copyfiles">Copying Files to or from an Emulator/Device Instance</a></li> +<li><a href="#commandsummary">Listing of adb Commands </a></li> +<li><a href="#shellcommands">Issuing Shell Commands</a></li> +<li><a href="#logcat">Enabling logcat Logging</a></li> +<li><a href="#stopping">Stopping the adb Server</a></li> + </ol> + + <h2>See also</h2> + <ol> + <li><a href="emulator.html">Emulator</a></li> + </ol> + +</div> +</div> + +<!-- +<p>Android Debug Bridge (adb) is a versatile tool that </a>. </p> <p>Some of ways you can use adb include:</p> <ul> -<li>Run shell commands on a device</li> -<li>Manage port forwarding on an emulator or device</li> -<li>Copy files to/from an emulator or device</li> + </ul> <p>The sections below introduce adb and describe many of its common uses. </p> @@ -39,8 +70,8 @@ page.title=Android Debug Bridge <a name="overview"></a> <h2>Overview</h2> - -<p>The adb tool is a client-server program that includes three components: </p> +--> +<p>Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components: </p> <ul> <li>A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients. </li> @@ -138,7 +169,7 @@ emulator-5558 device</pre> <pre>adb install <path_to_apk></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}reference/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/tools/aapt.html">Android Asset Packaging Tool</a> (aapt). </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> @@ -409,7 +440,7 @@ application and send 500 pseudo-random events to it.</p> <pre>$ adb shell monkey -v -p your.package.name 500</pre> <p>For more information about command options for Monkey, see the complete -<a href="{@docRoot}reference/monkey.html" title="monkey">UI/Application Exerciser Monkey</a> documentation page.</p> +<a href="{@docRoot}guide/developing/tools/monkey.html" title="monkey">UI/Application Exerciser Monkey</a> documentation page.</p> <a name="othershellcommands"></a> @@ -432,7 +463,7 @@ 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}reference/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/tools/ddms.html">Dalvik Debug Monitor Service</a> (DDMS) tool offers integrated debug environment that you may find easier to use.</td> </tr> <tr> diff --git a/docs/html/guide/developing/tools/adt.jd b/docs/html/guide/developing/tools/adt.jd new file mode 100644 index 0000000..c3bd255 --- /dev/null +++ b/docs/html/guide/developing/tools/adt.jd @@ -0,0 +1,154 @@ +page.title=ADT Plugin +@jd:body + +<p>The Android Development Tools (ADT) plugin adds powerful extensions to the Eclipse integrated development environment. It allows you to create and debug your Android applications easier and faster. If you use Eclipse, the ADT plugin gives you an incredible boost in developing Android applications:</p> + +<ul> + <li>It gives you access to other Android development tools from inside the Eclipse IDE. For example, ADT lets you access the many capabilities of the DDMS tool: take screenshots, manage port-forwarding, set breakpoints, and view thread and process informationd irectly from Eclipse.</li> + <li>It provides a New Project Wizard, which helps you quickly create and set up all of the basic files you'll need for a new Android application.</li> + <li>It automates and simplifies the process of building your Android application.</li> + <li>It provides an Android code editor that helps you write valid XML for your Android manifest and resource files.</li> +</ul> + +<h2 id="installingplugin">Installing the Eclipse Plugin (ADT)</h2> + +<p>If you <em>will not</em> be using the Eclipse IDE, you do not need to download or install the ADT plugin.</p> + +<p>To download and install the ADT plugin, follow the steps below for your respective Eclipse version. </p> + +<table style="font-size:100%"> +<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr> +<tr> +<td width="50%"> +<ol> + <li>Start Eclipse, then select <strong>Help</strong> > <strong>Software Updates</strong> > <strong>Find + and Install...</strong>. </li> + + <li>In the dialog that appears, select <strong>Search for new features to install</strong> and click <strong>Next</strong>. </li> + <li>Click <strong>New Remote Site</strong>. </li> + <li>In the resulting dialog box, enter a name for the remote site (e.g. Android Plugin) and enter this as its URL: + <pre>https://dl-ssl.google.com/android/eclipse/</pre> + <p>Click <strong>OK</strong>.</p> </li> + <li>You should now see the new site added to the search list (and checked). + Click <strong>Finish</strong>. </li> + <li>In the subsequent Search Results dialog box, select the checkbox for + <strong>Android Plugin</strong> > <strong>Developer Tools</strong>. + This will check both features: "Android Developer Tools", and "Android + Editors". The Android Editors feature is optional, but recommended. If + you choose to install it, you need the WST plugin mentioned earlier in this + page. Click <strong>Next</strong>. </li> + <li>Read the license agreement and then select <strong>Accept terms of the license agreement</strong>. + Click <strong>Next</strong>. </li> + <li>Click <strong>Finish</strong>. </li> + + <li>The ADT plugin is not signed; you can accept the installation anyway + by clicking <strong>Install All</strong>. </li> + <li>Restart Eclipse. </li> +</ol> + +</td> +<td> + +<ol> + <li>Start Eclipse, then select <strong>Help</strong> > <strong>Software Updates...</strong>. + </li> + <li>In the dialog that appears, click the <strong>Available Software</strong> tab. + </li> + <li>Click <strong>Add Site...</strong> + </li> + <li>Enter this as the Location: + <pre>https://dl-ssl.google.com/android/eclipse/</pre> + <p>Click <strong>OK</strong>.</p></li> + <li>Back in the Available Software view, you should see the plugin. Select the checkbox next to + <em>Developer Tools</em> and click <strong>Install...</strong> + </li> + <li>On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked. + The Android Editors feature is optional, but recommended. If + you choose to install it, you need the WST plugin mentioned earlier in this + page. Click <strong>Next</strong>. + </li> + <li>Accept the license agreement and click <strong>Finish</strong>.</li> + <li>Restart Eclipse. </li> +</ol> + +</td> +</tr> +</table> + +<h3 id="troubleshooting">Troubleshooting ADT Installation</h3> +<p> +If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions: </p> + +<ul> + <li>In Step 4, try changing the remote update site URL to use <code>http</code>, rather than <code>https</code>. </li> + <li>If you are behind a firewall (such as a corporate firewall), make + sure that you have properly configured your proxy settings in Eclipse. + In Eclipse 3.3/3.4, you can configure proxy information from the main + Eclipse menu in <strong>Window</strong> (on Mac, <strong>Eclipse</strong>) > <strong>Preferences</strong> > <strong>General</strong> > <strong>Network Connections</strong>.</li> +</ul> +<p> +If you are still unable to use Eclipse to download the ADT plugin, follow these steps to download and install the plugin from your computer: +</p> +<ol> +<li><a href="adt_download.html">Download the ADT zip file</a> (do not unpack it). +<li>Follow steps 1 and 2 in the default install instructions (above). +<li>In Eclipse 3.3, click <strong>New Archive Site...</strong>. <br/> + In Eclipse 3.4, click <strong>Add Site...</strong>, then <strong>Archive...</strong> +<li>Browse and select the downloaded the zip file. +<li>Follow the remaining procedures, above, starting from steps 5. +</ol> +<p> +Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.</p> + +<p>Note that the "Android Editors" feature of ADT requires several optional +Eclipse components (for example, WST). If you encounter an error when +installing ADT, your Eclipse installion might not include those components. +For information about how to quickly add the necessary components to your +Eclipse installation, see the troubleshooting topic +<a href="{@docRoot}guide/appendix/faq/troubleshooting.html#installeclipsecomponents">ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui"</a>.</p> + +<h4>For Linux users</h4> +<p>If you encounter this error when installing the ADT Plugin for Eclipse: +<pre> +An error occurred during provisioning. +Cannot connect to keystore. +JKS</pre> +<p> +...then your development machine lacks a suitable Java VM. Installing Sun +Java 6 will resolve this issue and you can then reinstall the ADT +Plugin.</p> + +<a name="Updating_the_ADT_plugin" id="Updating_the_ADT_plugin"></a> + +<h2>Updating the ADT Plugin </h2> + +<p>In some cases, a new ADT plugin may become available for your existing version of the SDK. You can use the steps below to update +the ADT plugin from inside Eclipse. </p> + +<table style="font-size:100%"> +<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr> +<tr> +<td width="50%"> +<ol> + <li> Select <strong>Help</strong> > <strong>Software Updates</strong> > <strong>Find and Install...</strong>. </li> + <li> Select <strong>Search for updates of the currently installed features</strong> and click <strong>Finish</strong>. </li> + <li> If an update for ADT is available, select and install. </li> +</ol> + +<p> Alternatively, </p> +<ol> + <li> Select <strong>Help</strong> > <strong>Software Updates</strong> > <strong>Manage Configuration</strong>. </li> + <li> Navigate down the tree and select <strong>Android Development Tools <version></strong> </li> + <li> Select <strong>Scan for Updates</strong> under <strong>Available Tasks</strong>.</li> +</ol> +</td> +<td> +<ol> + <li>Select <strong>Help</strong> > <strong>Software Updates...</strong></li> + <li>Select the <strong>Installed Software</strong> tab.</li> + <li>Click <strong>Update...</strong></li> + <li>If an update for ADT is available, select it and click <strong>Finish</strong>.</li> +</ol> +</td> +</tr> +</table> diff --git a/docs/html/guide/developing/tools/adt_download.jd b/docs/html/guide/developing/tools/adt_download.jd new file mode 100644 index 0000000..f03cc46 --- /dev/null +++ b/docs/html/guide/developing/tools/adt_download.jd @@ -0,0 +1,65 @@ +page.title=Download the ADT Plugin Zip File +@jd:body + +<p> +If you are unable to download the ADT plugin through <a +href="{@docRoot}guide/developing/tools/adt.html#installingplugin">setting up a remote +update site</a> in Eclipse, you can download the ADT zip file and install it +from your computer (archived site) instead. +</p> +<p> +If you go with this method, in order to update the plugin, you will need to +download the latest version from this page, uninstall the old version from +Eclipse, then install the new version. For more details on the procedure, +see Troubleshooting ADT Installation in the +<a href="{@docRoot}guide/developing/tools/adt.html#troubleshooting"> installation +page</a>. +</p> +<p> +<table> + <tr> + <th>Version</th> + <th>File</th> + <th>Date</th> + <th>Compatible SDK Versions</th> + <th>Notes</th> + </tr> + + <tr> + <td style="background-color:#ffcccc;">0.8.0</td> + <td style="background-color:#ffcccc;"><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">ADT-0.8.0.zip</a></td> + <td style="background-color:#ffcccc;">23 September 2008</td> + <td style="background-color:#ffcccc;">Android 1.0 SDK, Release 1</td> + <td style="background-color:#ffcccc;">Required for users of Android 1.0 SDK, Release 1. </td> + </tr> + <tr> + <td>0.7.1</td> + <td><a href="http://dl-ssl.google.com/android/ADT-0.7.1.zip">ADT-0.7.1.zip</a></td> + <td>18 Aug 2008</td> + <td>Android 0.9 SDK beta</td> + <td>Required for users of Android 0.9 SDK beta. As of this version, <b>Eclipse 3.2 is no longer supported.</b> + Please upgrade to Eclipse Ganymede (3.4) or Europa (3.3) if you are still using 3.2. </td> + </tr> + <tr> + <td>0.4.0</td> + <td><a href="http://dl-ssl.google.com/android/ADT-0.4.0.zip">ADT-0.4.0.zip</a></td> + <td>12 Feb 2008</td> + <td>m5-rc14</td> + <td>Required if you are using the M5 SDK. See the SDK Release Notes for details on changes and enhancements in this version.</td> + </tr> + <tr> + <td>0.3.3</td> + <td><a href="http://dl-ssl.google.com/android/ADT-0.3.3.zip">ADT-0.3.3.zip</a></td> + <td>14 Dec 2007</td> + <td>m3-rc37</td> + <td>Some significant enhancements (see SDK Release Notes).</td> + </tr> + <tr> + <td>0.3.1</td> + <td><a href="http://dl-ssl.google.com/android/ADT-0.3.1.zip">ADT-0.3.1.zip</a></td> + <td>21 Nov 2007</td> + <td>m3-rc20, m3-rc22</td> + <td>Initial Release.</td> + </tr> +</table> +</p> diff --git a/docs/html/guide/developing/tools/aidl.jd b/docs/html/guide/developing/tools/aidl.jd index 145fd93..96e4fec 100755..100644 --- a/docs/html/guide/developing/tools/aidl.jd +++ b/docs/html/guide/developing/tools/aidl.jd @@ -31,8 +31,8 @@ generate code to marshall the parameters.</p> <li><strong><a href="#aidlsyntax">Create your .aidl file</a> </strong>- This file defines an interface (<em>YourInterface</em>.aidl) that defines the methods and fields available to a client. </li> - <li><strong>Add the .aidl file to your makefile</strong> - (the <a href="{@docRoot}intro/installing.html#developingwitheclipse">Eclipse - plugin</a> manages this for you). Android includes the compiler, called + <li><strong>Add the .aidl file to your makefile</strong> - (the ADT Plugin for Eclipse + manages this for you). Android includes the compiler, called AIDL, in the <code>tools/</code> directory. </li> <li><strong><a href="#implementtheinterface">Implement your interface methods</a></strong> - The AIDL compiler creates an interface in the Java programming language from your AIDL interface. @@ -161,7 +161,8 @@ private final IRemoteService.Stub mBinder = new IRemoteService.Stub(){ interface to clients. </p> <pre>public class RemoteService extends Service { ... -{@include development/samples/ApiDemos/src/com/example/android/apis/app/RemoteService.java exposing_a_service} +{@include development/samples/ApiDemos/src/com/example/android/apis/app/RemoteService.java + exposing_a_service} }</pre> <a name="parcelable"></a> @@ -265,7 +266,7 @@ to a Parcel.</p> other processes. In this case, the rect will read four numbers from the parcel, but it is up to you to ensure that these are within the acceptable range of values for whatever the caller is trying to do. See -<a href="{@docRoot}devel/security.html">Security and Permissions in Android</a> for more +<a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> for more on how to keep your application secure from malware.</p> <h2>Calling an IPC Method <a name="calling"></a></h2> diff --git a/docs/html/guide/developing/tools/ddms.jd b/docs/html/guide/developing/tools/ddms.jd index 79ae66a..fa04216 100644 --- a/docs/html/guide/developing/tools/ddms.jd +++ b/docs/html/guide/developing/tools/ddms.jd @@ -19,7 +19,7 @@ the device. On Android, every application runs in its own process, each of which hosts its own virtual machine (VM). And each process listens for a debugger on a different port.</p> -<p>When it starts, DDMS connects to <a href="{@docRoot}reference/adb.html">adb</a> and +<p>When it starts, DDMS connects to <a href="{@docRoot}guide/developing/tools/adb.html">adb</a> and starts a device monitoring service between the two, which will notify DDMS when a device is connected or disconnected. When a device is connected, a VM monitoring service is created between adb and DDMS, which will notify DDMS when a VM on the device is started @@ -32,7 +32,7 @@ DDMS can now talk to the VM using a custom wire protocol.</p> <p>DDMS also opens another local port, the DDMS "base port" (8700, by default), upon which it also listens for a debugger. When a debugger connects to this base port, all traffic is forwarded to the VM currently selected in DDMS, so this is typically where you debugger should connect.</p> <p>For more information on port-forwarding with DDMS, -read <a href="{@docRoot}intro/installing.html#eclipse">Configuring your IDE to attach +read <a href="{@docRoot}guide/developing/debug-tasks.html#ide-debug-port">Configuring your IDE to attach to port 8700 for debugging</a>.</p> <p class="note"><strong>Tip:</strong> @@ -58,7 +58,7 @@ cursor may jump to the last line in the method for one step.</p> currently selected VM. (Notice, as you select a VM in the list, the listed port includes 8700.) This way, there's no need to reconfigure the debugger's port each time you switch between VMs.</p> <p>When an application running on the device calls {@link android.os.Debug#waitForDebugger()} - (or you select this option in the <a href="{@docRoot}intro/installing.html#additionaldebugging">developer + (or you select this option in the <a href="{@docRoot}guide/developing/debug-tasks.html#additionaldebugging">developer options</a>), a red icon will be shown next to the client name, while it waits for the debugger to attach to the VM. When a debugger is connected, the icon will turn green. </p> <p>If you see a crossed-out bug icon, this means that the DDMS was unable to complete a @@ -181,8 +181,8 @@ From here, you can:</p> Future releases may support timed placement and routes within a single coordinate element.</p> </li> </ul> - <p>For <em>additional</em> methods of spoofing location-based data, see the - <a href="{@docRoot}toolbox/apis/lbs.html">Location-based Service APIs</a> document.</p> + <p>For <em>additional</em> methods of setting up mocks of location-based data, see the + <a href="{@docRoot}guide/topics/location/index.html">Location</a> topic.</p> </li> </ul> @@ -192,7 +192,7 @@ From here, you can:</p> <h2 id="file-explorer">File Explorer</h2> <p>With the File Explorer, you can view the device file system and perform basic management, -like pushing and pulling files. This circumvents using the <a href="{@docRoot}reference/adb.html">adb</a> +like pushing and pulling files. This circumvents using the <a href="{@docRoot}guide/developing/tools/adb.html">adb</a> <code>push</code> and <code>pull</code> commands, with a GUI experience.</p> <p>With DDMS open, select <strong>Device</strong> > <strong>File Explorer...</strong> to open the File Explorer window. You can drag-and-drop into the device directories, but cannot drag <em>out</em> of them. @@ -210,7 +210,7 @@ sdcard directory. However, your files may not appear automatically. For example, MP3 file to the sdcard, the media player won't see them until you restart the emulator. (When restarting the emulator from command line, be sure to mount the sdcard again.)</p> <p>For more information on creating an SD card image, see the -<a href="{@docRoot}/reference/othertools.html#mksdcard">Other Tools</a> document.</p> +<a href="{@docRoot}guide/developing/tools/othertools.html#mksdcard">Other Tools</a> document.</p> <h2 id="screen-capture">Screen Capture</h2> <p>You can capture screen images on the device or emulator by selecting <strong>Device</strong> @@ -234,7 +234,7 @@ the emulator from command line, be sure to mount the sdcard again.)</p> <h2 id="examine-radio-state">Examine Radio State</h2> <p>By default, radio state is not output during a standard logcat (it is a lot of information). To see radio information, either click <strong>Device</strong> > <strong>Dump radio - state...</strong> or run logcat as described in <a href="{@docRoot}intro/installing.html#logradio">Logging + state...</strong> or run logcat as described in <a href="{@docRoot}guide/developing/debug-tasks.html#logradio">Logging Radio Information</a>. </p> <h2 id="stop-a-vitrual-machine">Stop a Virtual Machine </h2> diff --git a/docs/html/guide/developing/tools/draw9patch.jd b/docs/html/guide/developing/tools/draw9patch.jd index 25604f8..f25fabb 100644 --- a/docs/html/guide/developing/tools/draw9patch.jd +++ b/docs/html/guide/developing/tools/draw9patch.jd @@ -3,13 +3,12 @@ page.title=Draw 9-patch <p>The Draw 9-patch tool allows you to easily create a {@link android.graphics.NinePatch} graphic using a WYSIWYG editor.</p> -<p>To learn more about what a Nine-patch graphic is, and how they work, please read +<p>For an introduction to Nine-patch graphics and how they work, please read the section on Nine-patch in the -<a href="{@docRoot}reference/available-resources.html#ninepatch">Available Resource -Types</a> document.</p> +<a href="{@docRoot}guide/topics/resources/available-resources.html#ninepatch">Ninepatch Images</a> topic.</p> <div class="sidebox" style="width:auto"><br/> -<img src="/android/images/draw9patch-norm.png" alt="" height="300" width="341" /> +<img src="{@docRoot}images/draw9patch-norm.png" alt="" height="300" width="341" /> </div> <p>Here's a quick guide to create a Nine-patch graphic using the Draw 9-patch tool. @@ -41,7 +40,7 @@ You'll need the PNG image with which you'd like to create a NinePatch.</p> with no drawing area added, because it already exists.</p> <div class="sidebox" style="width:auto"><br/> -<img src="/android/images/draw9patch-bad.png" alt="" height="300" width="341" /> +<img src="{@docRoot}images/draw9patch-bad.png" alt="" height="300" width="341" /> </div> <p>Optional controls include:</p> @@ -57,5 +56,3 @@ You'll need the PNG image with which you'd like to create a NinePatch.</p> produce artifacts in the graphic when stretched. Visual coherence of your stretched image will be maintained if you eliminate all bad patches.</li> <ul> - -<p><strong><a href="/android/intro/tools.html">Back to Development Tools</a></strong></p>
\ No newline at end of file diff --git a/docs/html/guide/developing/tools/emulator.jd b/docs/html/guide/developing/tools/emulator.jd index 0516fdd..dd367b7 100755..100644 --- a/docs/html/guide/developing/tools/emulator.jd +++ b/docs/html/guide/developing/tools/emulator.jd @@ -1,7 +1,7 @@ page.title=Android Emulator @jd:body -<img src="{@docRoot}images/emulator-hvga-p.png" alt="Image of the Android Emulator" width="271" height="524" style="margin-left:0em;float:right;"/> +<img src="{@docRoot}images/emulator-hvga-p.png" alt="Image of the Android Emulator" width="271" height="524" style="margin-left:0em;margin-top:-4em;float:right;"/> <p>The Android SDK includes a mobile device emulator -- a virtual mobile device that runs on your computer. The emulator lets you prototype, develop, and test @@ -25,56 +25,64 @@ arriving SMS messages or phone calls), and simulate latency effects and dropouts on the data channel.</p> -<h2 style="clear:right;">Contents</h2> - -<div class="g-section g-tpl-50-50"> -<div class="g-unit g-first"> - -<dl> -<dt><a href="#overview">Overview</a></dt> -<dt><a href="#starting">Starting and Stopping the Emulator</a></dt> -<dt><a href="#controlling">Controlling the Emulator</a></dt> -<dt><a href="#startup-options">Emulator Startup Options</a></dt> -<dt><a href="#diskimages">Working with Emulator Disk Images</a></dt> - <dd><a href="#systemimages">System Images</a></dd> - <dd><a href="#runtimeimages">Runtime Images: User Data and SD Card</a></dd> - <dd><a href="#temporaryimages">Temporary Images</a></dd> -<dt><a href="#emulatornetworking">Emulator Networking</a></dt> - <dd><a href="#networkaddresses">Network Address Space</a></dd> - <dd><a href="#networkinglimitations">Local Networking Limitations</a></dd> - <dd><a href="#redirections">Using Network Redirections</a></dd> - <dd><a href="#dns">Configuring the Emulator's DNS Settings</a></dd> - <dd><a href="#proxy">Using the Emulator with a Proxy</a></dd> - <dd><a href="#connecting">Interconnecting Emulator Instances</a></dd> - <dd><a href="#calling">Sending a Voice Call or SMS to Another Emulator Instance</a></dd> -</dl> + + +<div class="inline-toc" style="whitespace:nowrap;"> +<h4>In this document:</h4> +<div class="g-unit g-first" style="whitespace:nowrap;width:35%;"> +<ol class="toc"> +<li><a href="#overview">Overview</a></li> +<li><a href="#starting">Starting and Stopping the Emulator</a></li> +<li><a href="#controlling">Controlling the Emulator</a></li> +<li><a href="#startup-options">Emulator Startup Options</a></li> +<li><a href="#diskimages">Working with Emulator Disk Images</a> + <ol class="toc"> + <li><a href="#systemimages">System Images</a></li> + <li><a href="#runtimeimages">Runtime Images: User Data and SD Card</a></li> + <li><a href="#temporaryimages">Temporary Images</a></li> + </ol></li> +<li><a href="#emulatornetworking">Emulator Networking</a> + <ol class="toc"> + <li><a href="#networkaddresses">Network Address Space</a></li> + <li><a href="#networkinglimitations">Local Networking Limitations</a></li> + <li><a href="#redirections">Using Network Redirections</a></li> + <li><a href="#dns">Configuring the Emulator's DNS Settings</a></li> + <li><a href="#proxy">Using the Emulator with a Proxy</a></li> + <li><a href="#connecting">Interconnecting Emulator Instances</a></li> + <li><a href="#calling">Sending a Voice Call or SMS to Another Emulator Instance</a></li> + </ol></li> +</ol> </div> -<div class="g-unit"> -<dl> -<dt><a href="#console">Using the Emulator Console</a></dt> - <dd><a href="#portredirection">Port Redirections</a></dd> - <dd><a href="#geo">Geo Location Provider Emulation</a></dd> - <dd><a href="#events">Sending Events</a></dd> - <dd><a href="#power">Emulating Device Power Characteristics</a></dd> - <dd><a href="#netstatus">Network Status</a></dd> - <dd><a href="#netdelay">Network Delay Emulation</a></dd> - <dd><a href="#netspeed">Network Speed Emulation</a></dd> - <dd><a href="#telephony">Telephony Emulation</a></dd> - <dd><a href="#sms">SMS Emulation</a></dd> - <dd><a href="#vm">VM State</a></dd> - <dd><a href="#window">Emulator Window</a></dd> - <dd><a href="#terminating">Terminating an Emulator Instance</a></dd> -<dt><a href="#skins">Using Emulator Skins</a></dt> -<dt><a href="#multipleinstances">Running Multiple Instances of the Emulator</a></dt> -<dt><a href="#apps">Installing Applications on the Emulator</a></dt> -<dt><a href="#sdcard">SD Card Emulation</a></dt> - <dd><a href="#creating">Creating a Disk Image</a></dd> - <dd><a href="#copying">Copying Files to a Disk Image</a></dd> - <dd><a href="#loading">Loading the Disk Image at Emulator Startup</a></dd> -<dt><a href="#troubleshooting">Troubleshooting Emulator Problems</a></dt> -<dt><a href="#limitations">Emulator Limitations</a></dt> -</dl> +<div class="g-unit" style="whitespace:nowrap;"> +<ol class="toc"> +<li><a href="#console">Using the Emulator Console</a> + <ol class="toc"> + <li><a href="#portredirection">Port Redirections</a></li> + <li><a href="#geo">Geo Location Provider Emulation</a></li> + <li><a href="#events">Sending Events</a></li> + <li><a href="#power">Emulating Device Power Characteristics</a></li> + <li><a href="#netstatus">Network Status</a></li> + <li><a href="#netdelay">Network Delay Emulation</a></li> + <li><a href="#netspeed">Network Speed Emulation</a></li> + <li><a href="#telephony">Telephony Emulation</a></li> + <li><a href="#sms">SMS Emulation</a></li> + <li><a href="#vm">VM State</a></li> + <li><a href="#window">Emulator Window</a></li> + <li><a href="#terminating">Terminating an Emulator Instance</a></li> + </ol></li> +<li><a href="#skins">Using Emulator Skins</a></li> +<li><a href="#multipleinstances">Running Multiple Instances of the Emulator</a></li> +<li><a href="#apps">Installing Applications on the Emulator</a></li> +<li><a href="#sdcard">SD Card Emulation</a> + <ol class="toc"> + <li><a href="#creating">Creating a Disk Image</a></li> + <li><a href="#copying">Copying Files to a Disk Image</a></li> + <li><a href="#loading">Loading the Disk Image at Emulator Startup</a></li> + </ol></li> +<li><a href="#troubleshooting">Troubleshooting Emulator Problems</a></li> +<li><a href="#limitations">Emulator Limitations</a></li> +</ol> </div> </div> @@ -209,7 +217,7 @@ the keys of your keyboard. </p> </tr> <tr> <td>Audio volume up button</td> - <td>KEYPAD_PLUS, Ctrl-F5</td> + <td>KEYPAD_PLUS, Ctrl-5</td> </tr> <tr> @@ -242,7 +250,11 @@ the keys of your keyboard. </p> </tr> <tr> <td>Toggle trackball mode</td> - <td>Ctrl-T</td> + <td>F6</td> + </tr> + <tr> + <td>Enter trackball mode temporarily (while key is pressed)</td> + <td>Delete</td> </tr> <tr> <td>DPad left/up/right/down</td> @@ -333,8 +345,8 @@ Here's the command-line usage for launching the emulator with options: </p> <td>Use <filepath> as the working user-data disk image. </td> <td>Optionally, you can specify a path relative to the current working directory. If <code>-data</code> is not used, the emulator looks for a file named "userdata-qemu.img" - in the directory specified in <datadir>. ~/.android (on Linux/Mac) or - C:\Documents and Settings\<user>\Local Settings\Application Data\Android (on Windows). + in the directory specified in <datadir>. ~/.android/SDK-1.0 (on Linux/Mac) or + C:\Documents and Settings\<user>\Local Settings\Application Data\Android\SDK-1.0 (on Windows). <p> If you use <code>-data <filepath></code> but the file does not exist, the emulator creates a file at that location using the specified name. </p> <p>See <a href="#multipleinstances">Running Multiple Emulator Instances</a> for information about how @@ -348,8 +360,8 @@ Here's the command-line usage for launching the emulator with options: </p> <td><code><dir></code> is a path relative to the current working directory. <p>If you do not specify <code>-datadir</code>, the emulator looks for the user-data image in the - directory ~/.android (on Linux/Mac) or C:\Documents and Settings\<user>\Local Settings\Application - Data\Android (on Windows). </p><p>For more information on disk images, use <code>-help-disk-images</code>.</p> + directory ~/.android/SDK-1.0 (on Linux/Mac) or C:\Documents and Settings\<user>\Local Settings\Application + Data\Android\SDK-1.0 (on Windows). </p><p>For more information on disk images, use <code>-help-disk-images</code>.</p> </td></tr> --> <tr> @@ -776,8 +788,8 @@ described above. The emulator stores the default image in this location on on your development machine: </p> <ul> - <li>Linux and OS X: <code>~/.android</code></li> - <li>Windows: <code>C:\Documents and Settings\<user>\Local Settings\Application Data\Android</code></li> + <li>Linux and OS X: <code>~/.android/SDK-1.0</code></li> + <li>Windows: <code>C:\Documents and Settings\<user>\Local Settings\Application Data\Android\SDK-1.0</code></li> </ul> <!-- @@ -1034,7 +1046,7 @@ case, <code>redir</code> generates an error message to that effect. </p> <p>The Android Debug Bridge (ADB) tool provides port forwarding, an alternate way for you to set up network redirections. For more information, see <a -href="{@docRoot}reference/adb.html#forwardports">Forwarding Ports</a> in the ADB +href="{@docRoot}guide/developing/tools/adb.html#forwardports">Forwarding Ports</a> in the ADB documentation.</p> <p>Note that ADB does not currently offer any way to remove a redirection, @@ -1159,7 +1171,7 @@ B:10.0.2.15:<serverPort></code></li> <p><code>Android Emulator (5554)</code></p> -<p>Alternatively, you can use the <code>adb devices</code> command, which prints a list of running emulator instances and their console port numbers. For more information, see <a href="{@docRoot}reference/adb.html#devicestatus">Querying for Emulator/Device Instances</a> in the adb documentation.</p> +<p>Alternatively, you can use the <code>adb devices</code> command, which prints a list of running emulator instances and their console port numbers. For more information, see <a href="{@docRoot}guide/developing/tools/adb.html#devicestatus">Querying for Emulator/Device Instances</a> in the adb documentation.</p> <p class="note">Note: The emulator listens for connections on ports 5554-5587 and accepts connections only from localhost.</p> @@ -1233,7 +1245,7 @@ B:10.0.2.15:<serverPort></code></li> </tr> </table> -<p>You can issue the <code>geo</code> command to fix the GPS location as soon as an emulator instance is running. The emulator creates a mock location provider that sends the location to GPS-aware applications as soon as they start and register location listeners. Any application can query the location manager to obtain the current GPS fix for the emulated device by calling: +<p>You can issue the <code>geo</code> command to fix the GPS location as soon as an emulator instance is running. The emulator creates a mock location provider that sends it to GPS-aware applications as soon as they start and register location listeners. Any application can query the location manager to obtain the current GPS fix for the emulated device by calling: <pre>LocationManager.getLastKnownLocation("gps")</pre> @@ -1443,7 +1455,7 @@ kilobits/sec):</p> <tr> <td><code>call <phonenumber></code></td> <td>Simulate an inbound phone call from <phonenumber>.</td> - <td>See also <a href="#calling">Sending a Voice Call or SMS to another Emulator Instance</a>.</td> + <td> </td> </tr> <tr> <td><code>accept <phonenumber></code></td> @@ -1632,8 +1644,8 @@ kilobits/sec):</p> <ul> <li>By default, only the first-launched emulator instance can preserve user data across sessions. When a session closes, the emulator stores the user data to a user-data image file — by default, it stores the data in the file - <code>~/.android/userdata-qemu.img </code>(on Linux and Mac) or <code>C:\Documents and Settings\<user>\Local - Settings\Application Data\Android\userdata-qemu.img</code> (on Windows) in your development computer.</li> + <code>~/.android/SDK-1.0/userdata-qemu.img </code>(on Linux and Mac) or <code>C:\Documents and Settings\<user>\Local + Settings\Application Data\Android\SDK-1.0\userdata-qemu.img</code> (on Windows) in your development computer.</li> <li>Emulator instances that you start after the first instance (that are running concurrently) can also store user data during a session, but they <em>do not</em> preserve it for the next session, unless you have specified a unique user-data image file in which the data should be stored. </li> @@ -1646,9 +1658,9 @@ kilobits/sec):</p> <h2>Installing Applications on the Emulator</h2> <p>If you don't have access to Eclipse or the ADT Plugin, you can install -your application on the emulator <a href="{@docRoot}reference/adb.html#move">using +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="aapt.html">Android Asset Packaging Tool</a>. +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 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 @@ -1683,7 +1695,7 @@ see <a href="#diskimages">Working with Emulator Disk Images</a>.</p> <pre>mksdcard 1024M sdcard1.iso</pre> -<p>For more information, see <a href="{@docRoot}reference/othertools.html">Other Tools</a>. </p> +<p>For more information, see <a href="{@docRoot}guide/developing/tools/othertools.html">Other Tools</a>. </p> <a name="copying"></a> <h3>Copying Files to a Disk Image</h3> @@ -1702,12 +1714,12 @@ see <a href="#diskimages">Working with Emulator Disk Images</a>.</p> <h2>Troubleshooting Emulator Problems</h2> -<p>The adb utility sees the emulator as an actual physical device. For this reason, you might have to use the -d flag with some common adb commands, such as <code>install</code>. The -d flag lets you specify which of several connected devices to use as the target of a command. If you don't specify -d, the emulator will target the first device in its list. For more information about adb, see <a href="{@docRoot}reference/adb.html">Android Debug Bridge</a>.</p> +<p>The adb utility sees the emulator as an actual physical device. For this reason, you might have to use the -d flag with some common adb commands, such as <code>install</code>. The -d flag lets you specify which of several connected devices to use as the target of a command. If you don't specify -d, the emulator will target the first device in its list. For more information about adb, see <a href="{@docRoot}guide/developing/tools/adb.html">Android Debug Bridge</a>.</p> <p>For emulators running on Mac OS X, if you see an error "Warning: No DNS servers found" when starting the emulator, check to see whether you have an <code>/etc/resolv.conf</code> file. If not, please run the following line in a command window:</p> <pre>ln -s /private/var/run/resolv.conf /etc/resolv.conf</pre> -<p>See <a href="{@docRoot}kb/index.html">Frequently Asked Questions</a> for more troubleshooting information. </p> +<p>See <a href="{@docRoot}guide/appendix/faq/index.html">Frequently Asked Questions</a> for more troubleshooting information. </p> <a name="limitations"></a> <h2>Emulator Limitations</h2> diff --git a/docs/html/guide/developing/tools/hierarchy-viewer.jd b/docs/html/guide/developing/tools/hierarchy-viewer.jd index 065211c..431008c 100644 --- a/docs/html/guide/developing/tools/hierarchy-viewer.jd +++ b/docs/html/guide/developing/tools/hierarchy-viewer.jd @@ -35,7 +35,7 @@ to refresh the list of available windows on the right.</p> <li>Wire-frame View: a wire-frame drawing of the layout, on the bottom-right.</li> </ul> <br/> -<img src="/android/images/hierarchyviewer-layout.png" alt="" height="509" width="700" /> +<img src="{@docRoot}images/hierarchyviewer-layout.png" alt="" height="509" width="700" /> <p>Select a node in the Tree View to display the properties of that element in the Properties View. When a node is selected, the Wire-frame View @@ -66,7 +66,7 @@ You must reload the Layout View by clicking <strong>Load View Hierarchy</strong> <li>Loupe View: a magnified, pixel-grid view of the device window, on the right.</li> </ul> <br/> -<img src="/android/images/hierarchyviewer-pixelperfect.png" alt="" height="509" width="700" /> +<img src="{@docRoot}images/hierarchyviewer-pixelperfect.png" alt="" height="509" width="700" /> <p>Click on an element in the Explorer View and a "layout box" will be drawn in the Normal View to indicate the layout position of that element. The layout box uses multiple rectangles, to indicate the normal bounds, the padding and the margin (as needed). The purple or green rectangle indicates @@ -95,5 +95,4 @@ in the Normal View, because the hierarchy believes you are still focused on the <li><strong>Zoom</strong>: Adjust the zoom level of the Loupe View.</li> </ul> -<p><strong><a href="/android/intro/tools.html">Back to Development Tools</a></strong></p> diff --git a/docs/html/guide/developing/tools/index.jd b/docs/html/guide/developing/tools/index.jd index c38f6c5..b491a4f 100644 --- a/docs/html/guide/developing/tools/index.jd +++ b/docs/html/guide/developing/tools/index.jd @@ -1,7 +1,7 @@ page.title=Tools Overview @jd:body -<img src="{@docRoot}images/android_icon_125.png" alt="android_robot" align="right" width="125" height="137""> +<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 applications on the Android platform. The most important of these are the Android @@ -10,51 +10,29 @@ includes a variety of other tools for debugging, packaging, and installing your applications on the emulator. </p> <dl> - <dt><a href="{@docRoot}emulator.html">Android Emulator</a></dt> + <dt><a href="emulator.html">Android Emulator</a></dt> <dd>A virtual mobile device that runs on your computer. You use the emulator to design, debug, and test your applications in an actual Android run-time environment. </dd> - <dt><a href="{@docRoot}hierarchy-viewer.html">Hierarchy Viewer</a> - <sup class="new">New!</sup></dt></dt> - <dd>The Hierarchy Viewer tool allows you to debug and optimize your user interface. - It provides a visual representation of your layout's hierarchy of Views and a magnified inspector - of the current display with a pixel grid, so you can get your layout just right. - </dd> - - <dt><a href="{@docRoot}draw9patch.html">Draw 9-patch</a> - <sup class="new">New!</sup></dt> - <dd>The Draw 9-patch tool 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 content is allowed. - </dd> + <dt><a href="adt.html">Android Development Tools Plugin</a> (for the Eclipse IDE)</dt> + <dd>The ADT plugin adds powerful extensions to the Eclipse integrated environment, + making creating and debugging your Android applications easier and faster. If you + use Eclipse, the ADT plugin gives you an incredible boost in developing Android + applications.</dd> - <dt>Android - Development Tools Plugin</a> for the Eclipse IDE</dt> - <dd>The ADT plugin adds powerful extensions to the Eclipse integrated environment, - making creating and debugging your Android applications easier and faster. If you - use Eclipse, the ADT plugin gives you an incredible boost in developing Android - applications: - </dd> - - <ul> - <li>It gives you access to other Android development tools from inside - the Eclipse IDE. For example, ADT lets you access the many capabilities of the - DDMS tool — taking screenshots, managing port-forwarding, setting breakpoints, - and viewing thread and process information — directly from Eclipse. - <li>It provides a New Project Wizard, which helps you quickly create and set up - all of the basic files you'll need for a new Android application.</li> - <li>It automates and simplifies the process of building your Android application.</li> - <li>It provides an Android code editor that helps you write valid XML for your - Android manifest and resource files.</li> - </ul> + <dt><a href="hierarchy-viewer.html">Hierarchy Viewer</a></dt> + <dd>The Hierarchy Viewer tool allows you to debug and optimize your user interface. + It provides a visual representation of your layout's hierarchy of Views and a magnified inspector + of the current display with a pixel grid, so you can get your layout just right. + </dd> - <p>For more information about the ADT plugin, including - installation instructions, see <em>Installing the ADT Plugin for - Eclipse</em> in your SDK package. For a usage example with screenshots, see the <a - href="{@docRoot}tutorials/hello-android.html" title="Hello - Android">Hello Android</a> tutorial.</p> + <dt><a href="draw9patch.html">Draw 9-patch</a></dt> + <dd>The Draw 9-patch tool 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 content is allowed. + </dd> - <dt><a href="{@docRoot}ddms.html" >Dalvik Debug Monitor + <dt><a href="ddms.html" >Dalvik Debug Monitor Service</a> (ddms)</dt> <dd>Integrated with Dalvik, the Android platform's custom VM, this tool lets you manage processes on an emulator or device and assists in debugging. @@ -62,49 +40,49 @@ applications on the emulator. </p> generate trace data, view heap and thread information, take screenshots of the emulator or device, and more. </dd> - <dt><a href="{@docRoot}adb.html" >Android Debug Bridge</a> (adb)</dt> - <dd>The adb tool lets you install your application's .apk files on an - emulator or device and access the emulator or device from a command line. - You can also use it to link a standard debugger to application code running - on an Android emulator or device.</dd> + <dt><a href="adb.html" >Android Debug Bridge</a> (adb)</dt> + <dd>The adb tool lets you install your application's .apk files on an + emulator or device and access the emulator or device from a command line. + You can also use it to link a standard debugger to application code running + on an Android emulator or device.</dd> - <dt><a href="{@docRoot}aapt.html" >Android Asset - Packaging Tool</a> (aapt)</dt> - <dd>The aapt tool lets you create .apk files containing the binaries and - resources of Android applications.</dd> + <dt><a href="aapt.html">Android Asset + Packaging Tool</a> (aapt)</dt> + <dd>The aapt tool lets you create .apk files containing the binaries and + resources of Android applications.</dd> - <dt><a href="{@docRoot}aidl.html" >Android Interface - Description Language</a> (aidl)</dt> - <dd>Lets you generate code for an interprocess interface, such as what - a service might use.</dd> + <dt><a href="aidl.html" >Android Interface + Description Language</a> (aidl)</dt> + <dd>Lets you generate code for an interprocess interface, such as what + a service might use.</dd> - <dt><a href="{@docRoot}adb.html#sqlite">sqlite3</a></dt> + <dt><a href="adb.html#sqlite">sqlite3</a></dt> <dd>Included as a convenience, this tool lets you access the SQLite data files created and used by Android applications.</dd> - <dt><a href="{@docRoot}traceview.html" >Traceview</a></dt> - <dd> This tool produces graphical analysis views of trace log data that you - can generate from your Android application. </dd> + <dt><a href="traceview.html" >Traceview</a></dt> + <dd> This tool produces graphical analysis views of trace log data that you + can generate from your Android application. </dd> - <dt><a href="{@docRoot}othertools.html#mksdcard">mksdcard</a></dt> - <dd>Helps you create a disk image that you can use with the emulator, - to simulate the presence of an external storage card (such as an SD card).</dd> + <dt><a href="othertools.html#mksdcard">mksdcard</a></dt> + <dd>Helps you create a disk image that you can use with the emulator, + to simulate the presence of an external storage card (such as an SD card).</dd> - <dt><a href="{@docRoot}othertools.html#dx">dx</a></dt> - <dd>The dx tool rewrites .class bytecode into Android bytecode - (stored in .dex files.)</dd> + <dt><a href="othertools.html#dx">dx</a></dt> + <dd>The dx tool rewrites .class bytecode into Android bytecode + (stored in .dex files.)</dd> - <dt><a href="{@docRoot}monkey.html" >UI/Application + <dt><a href="monkey.html">UI/Application Exerciser Monkey</a></dt> <dd>The Monkey is a program that runs on your emulator or device and generates pseudo-random streams of user events such as clicks, touches, or gestures, as well as a number of system- level events. You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.</dd> - <dt><a href="{@docRoot}othertools.html#activitycreator">activitycreator</a></dt> - <dd>A script that generates <a - href="http://ant.apache.org/" title="Ant">Ant</a> build files that - you can use to compile your Android applications. If you are developing - on Eclipse with the ADT plugin, you won't need to use this script. </dd> + <dt><a href="othertools.html#activitycreator">activitycreator</a></dt> + <dd>A script that generates <a + href="http://ant.apache.org/" title="Ant">Ant</a> build files that + you can use to compile your Android applications. If you are developing + on Eclipse with the ADT plugin, you won't need to use this script. </dd> </dl> diff --git a/docs/html/guide/developing/tools/monkey.jd b/docs/html/guide/developing/tools/monkey.jd index d829f5b..9a2ab6f 100644 --- a/docs/html/guide/developing/tools/monkey.jd +++ b/docs/html/guide/developing/tools/monkey.jd @@ -2,7 +2,7 @@ page.title=UI/Application Exerciser Monkey @jd:body <p>The Monkey is a program that runs on your -<a href="{@docRoot}reference/emulator.html">emulator</a> or device and generates pseudo-random +<a href="{@docRoot}guide/developing/tools/emulator.html">emulator</a> or device and generates pseudo-random streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.</p> @@ -185,7 +185,7 @@ transitions invoked by your application.</td> <td>If set, this option will generate profiling reports immediately before and after the Monkey event sequence. This will generate large (~5Mb) files in data/misc, so use with care. See -<a href="{@docRoot}reference/traceview.html" title="traceview">Traceview</a> for more information +<a href="{@docRoot}guide/developing/tools/traceview.html" title="traceview">Traceview</a> for more information on trace files.</td> </tr> diff --git a/docs/html/guide/developing/tools/othertools.jd b/docs/html/guide/developing/tools/othertools.jd index 4ebcf4a..eaa0b76 100755..100644 --- a/docs/html/guide/developing/tools/othertools.jd +++ b/docs/html/guide/developing/tools/othertools.jd @@ -47,7 +47,7 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t </table> -<p>Once you have created the disk image file, you can load it in the emulator at startup using the emulator's -sdcard option. For more information, see <a href="{@docRoot}reference/emulator.html">Android Emulator</a>.</p> +<p>Once you have created the disk image file, you can load it in the emulator at startup using the emulator's -sdcard option. For more information, see <a href="{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a>.</p> <pre>emulator -sdcard <file></pre> @@ -55,7 +55,7 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t <h2>dx</h2> -<p>The dx tool lets you generate Android bytecode from .class files. The tool converts target files and/or directories to Dalvik executable format (.dex) files, so that they can run in the Android environment. It can also dump the class files in a human-readable format and run a target unit test. You can get the usage and options for this tool by using <code>dx -help</code>.</p> +<p>The dx tool lets you generate Android bytecode from .class files. The tool converts target files and/or directories to Dalvik executable format (.dex) files, so that they can run in the Android environment. It can also dump the class files in a human-readable format and run a target unit test. You can get the usage and options for this tool by using <code>dx --help</code>.</p> <a name="activitycreator"></a> @@ -63,7 +63,7 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t <p>If you aren't using the Eclipse IDE and ADT plugin, you can use the the activitycreator script to get started with a new application. When you run the script, it creates the structure of a minimal Android application that you can build on and extend to meet your needs. </p> -<p>For Linux and Mac, the SDK provides <code>activitycreator.py</code>, a Python script, and for Windows <code>activitycreator.bat</code>, a batch script that runs an executable. Regardless of platform, the usage for the script is the same:</p> +<p>For Linux and Mac, the SDK provides <code>activitycreator</code>, a shell script, and for Windows <code>activitycreator.bat</code>, a batch script that runs an executable. Regardless of platform, the usage for the script is the same:</p> <pre>activitycreator [--out <folder>] [--ide intellij] your.package.name.ActivityName</pre> @@ -97,7 +97,7 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t <li>bin -- The output folder for the compiled .apk (when built by Ant).</li> </ul> -<p>When you are ready, you can use Ant to <a href="{@docRoot}intro/installing.html#buildingwithant">build the project</a> so that you can run it on the emulator.</p> +<p>When you are ready, you can use Ant to <a href="{@docRoot}guide/developing/other-ide.html#antbuild">build the project</a> so that you can run it on the emulator.</p> <p>If you are using Eclipse with the ADT plugin, you do not need to use activitycreator. You can use the New Project Wizard, provided by the ADT plugin, instead. </p> diff --git a/docs/html/guide/developing/tools/traceview.jd b/docs/html/guide/developing/tools/traceview.jd index 8c87eed..dd3f4bb 100644 --- a/docs/html/guide/developing/tools/traceview.jd +++ b/docs/html/guide/developing/tools/traceview.jd @@ -69,7 +69,7 @@ can create an SD card image and mount it when launching the emulator like so:</p <b>$</b> emulator -sdcard ./img </pre> <p>For more information, read about the -<a href="{@docRoot}reference/othertools.html#mksdcard">mksdcard tool</a>.</p> +<a href="{@docRoot}guide/developing/tools/othertools.html#mksdcard">mksdcard tool</a>.</p> <p>The format of the trace files is described <a href="#format">later in this document</a>. </p> @@ -111,7 +111,7 @@ the emulator host machine:</p> the first row show the extent (entry to exit) of all the calls to the selected method. The method in this case is LoadListener.nativeFinished() and it was selected in the profile view. </p> -<p><img src="../images/traceview_timeline.png" alt="Traceview timeline panel" width="893" height="284"></p> +<p><img src="/images/traceview_timeline.png" alt="Traceview timeline panel" width="893" height="284"></p> <a name="profilepanel"></a> <h3>Profile Panel</h3> <p>The image below shows the profile pane. The profile pane shows a @@ -128,7 +128,7 @@ the emulator host machine:</p> view, we can see that there were 14 calls to LoadListener.nativeFinished(); looking at the timeline panel shows that one of those calls took an unusually long time.</p> -<p><img src="../images/traceview_profile.png" alt="Traceview profile panel." width="892" height="630"></p> +<p><img src="/images/traceview_profile.png" alt="Traceview profile panel." width="892" height="630"></p> <a name="format"></a> <h2>Traceview File Format</h2> |