diff options
Diffstat (limited to 'docs/html/guide/topics')
6 files changed, 13 insertions, 15 deletions
diff --git a/docs/html/guide/topics/fundamentals.jd b/docs/html/guide/topics/fundamentals.jd index fffc1cd..1658fa6 100644 --- a/docs/html/guide/topics/fundamentals.jd +++ b/docs/html/guide/topics/fundamentals.jd @@ -52,10 +52,9 @@ page.title=Application Fundamentals <p> Android applications are written in the Java programming language. The compiled Java code — along with any data and resource -files required by the application — 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 — 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"><provider></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 diff --git a/docs/html/guide/topics/graphics/2d-graphics.jd b/docs/html/guide/topics/graphics/2d-graphics.jd index 5759be5..05f4023 100644 --- a/docs/html/guide/topics/graphics/2d-graphics.jd +++ b/docs/html/guide/topics/graphics/2d-graphics.jd @@ -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 diff --git a/docs/html/guide/topics/location/obtaining-user-location.jd b/docs/html/guide/topics/location/obtaining-user-location.jd index bc782d2..3b450f0 100644 --- a/docs/html/guide/topics/location/obtaining-user-location.jd +++ b/docs/html/guide/topics/location/obtaining-user-location.jd @@ -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> diff --git a/docs/html/guide/topics/resources/drawable-resource.jd b/docs/html/guide/topics/resources/drawable-resource.jd index d9f619f..cee8fc3 100644 --- a/docs/html/guide/topics/resources/drawable-resource.jd +++ b/docs/html/guide/topics/resources/drawable-resource.jd @@ -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 diff --git a/docs/html/guide/topics/testing/testing_android.jd b/docs/html/guide/topics/testing/testing_android.jd index d4b0dcc..6f3048c 100755 --- a/docs/html/guide/topics/testing/testing_android.jd +++ b/docs/html/guide/topics/testing/testing_android.jd @@ -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> diff --git a/docs/html/guide/topics/ui/declaring-layout.jd b/docs/html/guide/topics/ui/declaring-layout.jd index 843414a..c348767 100644 --- a/docs/html/guide/topics/ui/declaring-layout.jd +++ b/docs/html/guide/topics/ui/declaring-layout.jd @@ -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 — 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 — 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> |