drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am 13033ea5: docs: fix misc broken links

Browse Source 
* commit '13033ea52714d48d754c6bc8fccb18514c645a47':
  docs: fix misc broken links
This commit is contained in:
Scott Main
2011-02-15 20:08:07 -08:00
committed by Android Git Automerger
parent 4053452330 13033ea527
commit 0ab1b326c7
17 changed files with 80 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
core/java/android/app/package.html
View File

@ -32,8 +32,9 @@ backwards through the fragment states, without leaving the activity.</p>
action bar.</p>
<p>For information about using some the classes in this package, see the following
documents: <a href="{@docRoot}guide/topics/fundamentals/index.html">Application
Fundamentals</a> (for activities, services, and fragments), <a
documents: <a href="{@docRoot}guide/topics/fundamentals/activities.html">Activities</a>, <a
href="{@docRoot}guide/topics/fundamentals/services.html">Services</a>, <a
href="{@docRoot}guide/topics/fundamentals/fragments.html">Fragments</a>, <a
href="{@docRoot}guide/topics/ui/actionbar.html">Using the Action Bar</a>, <a
href="{@docRoot}guide/topics/ui/dialogs.html">Creating Dialogs</a>, and <a
href="{@docRoot}guide/topics/ui/notifiers/index.html">Notifying the User</a>.</p>

4
core/java/android/content/pm/package.html
View File

@ -5,7 +5,7 @@ application package, including information about its activities,
permissions, services, signatures, and providers.</p>
<p>Most of the information about an application package is defined by its manifest file. For
more information, see the <a
href="{@docRoot}guide/topics/manifest/guide/topics/manifest/manifest-intro.html">AndroidManifest.xml
File</a> documentation.</p>
href="{@docRoot}guide/topics/manifest/manifest-intro.html">AndroidManifest.xml File</a>
documentation.</p>
</BODY>
</HTML>

4
core/java/android/widget/TimePicker.java
View File

@ -43,8 +43,8 @@ import java.util.Calendar;
* or 'P' to pick. For a dialog using this view, see
* {@link android.app.TimePickerDialog}.
*<p>
* See the <a href="{@docRoot}
* resources/tutorials/views/hello-timepicker.html">Time Picker tutorial</a>.
* See the <a href="{@docRoot}resources/tutorials/views/hello-timepicker.html">Time Picker
* tutorial</a>.
* </p>
*/
@Widget

4
docs/html/guide/developing/testing/testing_eclipse.jd
View File

@ -16,8 +16,8 @@ page.title=Testing from Eclipse with ADT
basic processes for creating and running applications with ADT, as described in
<a href="{@docRoot}guide/developing/projects/projects-eclipse.html">Managing Projects from
Eclipse</a>
and <a href="guide/developing/building/building-eclipse.html">Building and Running from
Eclipse</a>.
and <a href="{@docRoot}guide/developing/building/building-eclipse.html">Building and Running
from Eclipse</a>.
You may also want to read
<a href="{@docRoot}guide/topics/testing/testing_android.html">Testing Fundamentals</a>,
which provides an overview of the Android testing framework.

17
docs/html/guide/publishing/licensing.jd
View File

@ -518,7 +518,7 @@ Android Virtual Devices.</li>
</ol>
<p>If you are not familiar with AVDs or how to use them, see <a
href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>.</p>
href="{@docRoot}guide/developing/devices/index.html">Managing Virtual Devices</a>.</p>
<h4 id="project-update">Updating your project configuration</h4>
@ -629,7 +629,7 @@ share its code and resources across multiple applications. </p>
<p style="margin-top:.5em;">If you aren't familiar with library projects or how
to use them, see <a href="{@docRoot}guide/developing/projects/index.html#LibraryProjects">
Creating and Managing Projects</a>.
Managing Projects</a>.
</p>
</div>
</div>
@ -666,8 +666,9 @@ predefined as a library project in its <code>default.properties</code> file, so
no further configuration is needed. </p>
<p>For more information about how to create an application project or work with
library projects in Eclipse, see <a href="{@docRoot}guide/developing/projects/projects-eclipse.html">
Creating and Managing Projects in Eclipse</a></p>.
library projects in Eclipse, see <a
href="{@docRoot}guide/developing/projects/projects-eclipse.html">Managing Projects from
Eclipse with ADT</a></p>.
<h4>Copying the LVL sources to your application</h4>
@ -698,8 +699,8 @@ haven't done that already, do it now before continuing. </p>
Select the "Android" properties group and click <strong>Add</strong>, then
choose the LVL library project (com_android_vending_licensing) and click
<strong>OK</strong>. For more information, see
<a href="{@docRoot}developing/projects/projects-eclipse.html#SettingUpLibraryProject">
Creating and Managing Projects in Eclipse</a></p>.
<a href="{@docRoot}guide/developing/projects/projects-eclipse.html#SettingUpLibraryProject">
Managing Projects from Eclipse with ADT</a></p>.
<div style="margin-bottom:2em;">
@ -727,8 +728,8 @@ properties, including the reference to the library project:</p>
</pre>
<p>For more information about working with library projects,
see <a href="{@docRoot}developing/projects/projects-cmdline.html#SettingUpLibraryProject">
Creating and Managing Projects on the Command Line</a></p>.
see <a href="{@docRoot}guide/developing/projects/projects-cmdline.html#SettingUpLibraryProject">
Managing Projects from the Command Line</a></p>.
<h2 id="app-integration">Integrating the LVL with Your Application</h2>

6
docs/html/guide/topics/advanced/aidl.jd
View File

@ -14,9 +14,11 @@ do that marshalling is tedious to write, so Android handles it for you with AIDL
<p class="note"><strong>Note:</strong> Using AIDL is necessary only if you allow clients from
different applications to access your service for IPC and want to handle multithreading in your
service. If you do not need to perform IPC across
different applications, you should create your interface <a href="Binder">implementing a
different applications, you should create your interface <a
href="{@docRoot}guide/topics/fundamentals/bound-services.html#Binder">implementing a
Binder</a> or, if you want to perform IPC, but do not need to handle multithreading, then you
should implement your interface <a href="#Messenger">using a Messenger</a>.</p>
should implement your interface <a
href="{@docRoot}guide/topics/fundamentals/bound-services.html#Messenger">using a Messenger</a>.</p>
<p>Before you begin designing your AIDL interface, be aware that calls on to an AIDL interface are
direct function calls. You can not generally make assumptions about the thread in which the call

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

@ -422,7 +422,7 @@ because the Android system makes the appropriate adjustments to your UI layout a
resources. However, you should create specialized layouts for certain screen sizes and provide
specialized images for certain densities, using alternative layout resources, and by declaring in
your manifest exactly which screen sizes your application supports with the <a
href="{@docRoot}guide/topics/manifest/supports-screens.html">{@code
href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
&lt;supports-screens&gt;}</a> element.</p>
<p>For more information, see the <a
href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>
@ -453,7 +453,8 @@ platform version specifies an <a
href="{@docRoot}guide/appendix/api-levels.html">API Level</a> (for example, Android 1.0 is API Level
1 and Android 2.3 is API Level 9). If you use any APIs that were added to the platform after
version 1.0, you should declare the minimum API Level in which those APIs were introduced using the
<a href="{@docRoot}guide/topics/manifest/uses-sdk.html">{@code &lt;uses-sdk&gt;}</a> element.</dd>
<a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code &lt;uses-sdk&gt;}</a>
element.</dd>
</dl>
<p>It's important that you declare all such requirements for your application, because, when you

7
docs/html/guide/topics/fundamentals/activities.jd
View File

@ -40,7 +40,7 @@ page.title=Activities
<h2>See also</h2>
<ol>
<li><a href="{@docRoot}resources/tutorials/hello-world.html">Hello World Tutorial</a></li>
<li><a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack">Tasks and Back
<li><a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back
Stack</a></li>
</ol>
@ -594,13 +594,14 @@ from the time {@link android.app.Activity#onPause onPause()} returns to the time
definition in table 1 might still be killed by the system&mdash;but that would happen only in
extreme circumstances when there is no other recourse. When an activity might be killed is
discussed more in the <a
href="{@docRoot}guide/topics/fundamentals/processes-and-threading.html">Processes and
href="{@docRoot}guide/topics/fundamentals/processes-and-threads.html">Processes and
Threading</a> document.</p>
<h3 id="SavingActivityState">Saving activity state</h3>
<p>The introduction to <a href="Lifecycle">Managing the Activity Lifecycle</a> briefly mentions that
<p>The introduction to <a href="#Lifecycle">Managing the Activity Lifecycle</a> briefly mentions
that
when an activity is paused or stopped, the state of the activity is retained. This is true because
the {@link android.app.Activity} object is still held in memory when it is paused or
stopped&mdash;all information about its members and current state is still alive. Thus, any changes

3
docs/html/guide/topics/fundamentals/fragments.jd
View File

@ -743,7 +743,8 @@ from the list. It also demonstrates how to provide different configurations of t
based on the screen configuration.</p>
<p class="note"><strong>Note:</strong> The complete source code for this activity is available in
<a href="resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentLayout.html">{@code
<a
href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentLayout.html">{@code
FragmentLayout.java}</a>.</p>
<p>The main activity applies a layout in the usual way, during {@link

4
docs/html/guide/topics/fundamentals/services.jd
View File

@ -121,7 +121,7 @@ a thread in {@link android.app.Activity#onCreate onCreate()}, start running it i
android.app.Activity#onStart onStart()}, then stop it in {@link android.app.Activity#onStop
onStop()}. Also consider using {@link android.os.AsyncTask} or {@link android.os.HandlerThread},
instead of the traditional {@link java.lang.Thread} class. See the <a
href="{@docRoot}guide/topics/fundamentals/processes-and-threading.html#Threads">Processes and
href="{@docRoot}guide/topics/fundamentals/processes-and-threads.html#Threads">Processes and
Threading</a> document for more information about threads.</p>
<p>Remember that if you do use a service, it still runs in your application's main thread by
default, so you should still create a new thread within the service if it performs intensive or
@ -183,7 +183,7 @@ by the system. If the system kills your service, it restarts it as soon as resou
available again (though this also depends on the value you return from {@link
android.app.Service#onStartCommand onStartCommand()}, as discussed later). For more information
about when the system might destroy a service, see the <a
href="{@docRoot}guide/topics/fundamentals/processes-and-threading.html">Processes and Threading</a>
href="{@docRoot}guide/topics/fundamentals/processes-and-threads.html">Processes and Threading</a>
document.</p>
<p>In the following sections, you'll see how you can create each type of service and how to use

9
docs/html/guide/topics/providers/loaders.jd
View File

@ -29,8 +29,11 @@ page.title=Using Loaders
<h2>Related samples</h2>
<ol>
<li> <a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentCursorLoader.html"> FragmentCursorLoader</a></li>
<li> <a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html"> LoaderThrottle</a></li>
<li> <a
href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentListCursorLoader.html">FragmentListCursorLoader</a></li>
<li> <a
href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html">
LoaderThrottle</a></li>
</ol>
</div>
</div>
@ -480,7 +483,7 @@ public static class CursorLoaderListFragment extends ListFragment
<p>There are a few different samples in <strong>ApiDemos</strong> that
illustrate how to use loaders:</p>
<ul>
<li><a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentCursorLoader.html"> FragmentCursorLoader</a> &#8212; A complete version of the
<li><a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentListCursorLoader.html">FragmentListCursorLoader</a> &#8212; A complete version of the
snippet shown above.</li>
<li><a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html"> LoaderThrottle</a> &#8212; An example of how to use throttling to
reduce the number of queries a content provider does then its data changes.</li>

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

@ -653,10 +653,12 @@ The <a href="{@docRoot}guide/developing/tools/monkey.html">UI/Application Exerci
It guides you through a more complex testing scenario that you develop against a
more realistic application.
</li>
<!-- sample is not available
<li>
The sample test package <a href="{@docRoot}resources/samples/AlarmServiceTest"}>
The sample test package <a href="{@docRoot}resources/samples/AlarmServiceTest/index.html">
Alarm Service Test</a> is an example of testing a {@link android.app.Service}. It contains
a set of unit tests for the Alarm Service sample application's {@link android.app.Service}.
</li>
-->
</ul>

14
docs/html/guide/topics/ui/actionbar.jd
View File

@ -38,7 +38,15 @@ application</li>
<li>{@link android.app.ActionBar}</li>
<li>{@link android.view.Menu}</li>
</ol>
<h2>Related samples</h2>
<ol>
<li><a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/index.html#ActionBar">API
Demos</a></li>
<li><a
href="{@docRoot}resources/samples/HoneycombGallery/index.html">Honeycomb Gallery</a></li>
</ol>
<h2>See also</h2>
<ol>
<li><a href="{@docRoot}guide/topics/ui/menus.html">Creating Menus</a></li>
@ -363,7 +371,7 @@ the icon and/or title text. However, if there's not enough room in the Action Ba
in the overflow menu as a normal menu item and you must respond to it from the {@link
android.app.Activity#onOptionsItemSelected onOptionsItemSelected()} callback method. (For a
guide to providing search functionality, see the <a
href="{@docRoot}gudie/topics/search/index.html">Search</a> documentation.)</p>
href="{@docRoot}guide/topics/search/index.html">Search</a> documentation.)</p>
<p>When the activity first starts, the system populates the Action Bar and overflow menu by calling
{@link android.app.Activity#onCreateOptionsMenu onCreateOptionsMenu()}.
@ -397,7 +405,7 @@ href="{@docRoot}guide/topics/search/index.html">Search</a> developer guide.</p>
<img src="{@docRoot}images/ui/actionbar-tabs.png" alt="" />
<p class="img-caption"><strong>Figure 6.</strong> Screenshot of tabs in the
Action Bar, from the <a
href="{@docRoot}resources/samples/Honeycomb-Gallery/index.html">Honeycomb Gallery</a> sample
href="{@docRoot}resources/samples/HoneycombGallery/index.html">Honeycomb Gallery</a> sample
application.</p>
</div>

4
docs/html/guide/topics/ui/drag-drop.jd
View File

@ -289,14 +289,14 @@ DraggableDot.java</a> in <a href="{@docRoot}resources/samples/ApiDemos/index.htm
<p>
To get the action type, a listener calls {@link android.view.DragEvent#getAction()}. There
are six possible values, defined by constants in the {@link android.view.DragEvent} class. These
are listed in <a href="table1">table 1</a>.
are listed in <a href="#table1">table 1</a>.
</p>
<p>
The {@link android.view.DragEvent} object also contains the data that your application provided
to the system in the call to
{@link android.view.View#startDrag(ClipData,View.DragShadowBuilder,Object,int) startDrag()}.
Some of the data is valid only for certain action types. The data that is valid for each action
type is summarized in <a href="table2">table 2</a>. It is also described in detail with
type is summarized in <a href="#table2">table 2</a>. It is also described in detail with
the event for which it is valid in the section
<a href="#DesignDragOperation">Designing a Drag and Drop Operation</a>.
</p>

41
docs/html/resources/articles/live-wallpapers.jd
View File

@ -27,35 +27,36 @@ to display the appropriate sky.</p>
<img src="images/live_wallpapers_small.png" style="align:center" />
<p>Creating your own live wallpaper is easy, especially if you have had
previous experience with <a
href="../../../reference/android/view/SurfaceView.html"><code>SurfaceView</code></a> or <a
href="../../../reference/android/graphics/Canvas.html"><code>Canvas</code></a>.
previous experience with {@link android.view.SurfaceView} or {@link
android.graphics.Canvas}.
To learn how to create a live wallpaper, you should check out the <a
href="../samples/CubeLiveWallpaper/index.html">CubeLiveWallpaper sample code</a>.</p>
<p>In terms of implementation, a live wallpaper is very similar to a regular
Android <a href="../../../reference/android/app/Service.html">service</a>. The
only difference is the addition of a new method, <a
href="../../../reference/android/service/wallpaper/WallpaperService.html#onCreateEngine()">{@code
onCreateEngine()}</a>, whose goal is to create a <a
href="../../../reference/android/service/wallpaper/WallpaperService.Engine.html">
<code>WallpaperService.Engine</code></a>. The engine is responsible for
<p>In terms of implementation, a live wallpaper is very similar to a {@link android.app.Service}.
The only difference is the addition of a new method, {@link
android.service.wallpaper.WallpaperService#onCreateEngine()}, whose goal is to create a {@link
android.service.wallpaper.WallpaperService.Engine}. The engine is responsible for
handling the lifecycle and drawing of a wallpaper. The system provides a surface
on which you can draw, just like you would with a <code>SurfaceView</code></a>.
on which you can draw, just like you would with a {@link android.view.SurfaceView}.
Drawing a wallpaper can be very expensive so you should optimize your code
as much as possible to avoid using too much CPU, not only for battery life
but also to avoid slowing down the rest of the system. That is also why the
most important part of the lifecycle of a wallpaper is <a href="../../../reference/android/service/wallpaper/WallpaperService.Engine.html#onVisibilityChanged%28boolean%29">when it becomes invisible</a>.
most important part of the lifecycle of a wallpaper is when it becomes visible, as indicated
by a call to {@link android.service.wallpaper.WallpaperService.Engine#onVisibilityChanged
onVisibilityChanged()}.
When invisible, such as when the user launches an application that covers
the home screen, a wallpaper must stop all activity.</p>
<p>The engine can also implement several methods to interact with the user
or the home application. For instance, if you want your wallpaper to scroll
along when the user swipes from one home screen to another, you can use <a href="../../../reference/android/service/wallpaper/WallpaperService.Engine.html#onOffsetsChanged%28float,%20float,%20float,%20float,%20int,%20int%29"><code>onOffsetsChanged()</code></a>.
To react to touch events, simply implement <a href="../../../reference/android/service/wallpaper/WallpaperService.Engine.html#onTouchEvent%28android.view.MotionEvent%29"><code>onTouchEvent(MotionEvent)</code></a>.
along when the user swipes from one home screen to another, you can use
{@link android.service.wallpaper.WallpaperService.Engine#onOffsetsChanged
onOffsetsChanged()}.
To react to touch events, simply implement {@link
android.service.wallpaper.WallpaperService.Engine#onTouchEvent onTouchEvent()}.
Finally, applications can send arbitrary commands to the live wallpaper.
Currently, only the standard home application sends commands to the <a
href="../../../reference/android/service/wallpaper/WallpaperService.Engine.html#onCommand%28java.lang.String,%20int,%20int,%20int,%20android.os.Bundle,%20boolean%29"><code>onCommand()</code></a>
Currently, only the standard home application sends commands to the
{@link android.service.wallpaper.WallpaperService.Engine#onCommand onCommand()}
method of the live wallpaper:</p>
<ul>
@ -78,9 +79,9 @@ before publishing to Android Market:</p>
<ul>
<li><code>&lt;uses-sdk android:minSdkVersion="7" /&gt;</code>, which indicates
to Android Market and the platform that your application requires Android 2.1 or
higher. For more information, see the <a href="../../../guide/appendix/api-levels.html">API
higher. For more information, see the <a href="{@docRoot}guide/appendix/api-levels.html">API
Levels</a> and the documentation for the
<a href="../../../guide/topics/manifest/uses-sdk-element.html"><code>&lt;uses-sdk&gt;</code></a>
<a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code>&lt;uses-sdk&gt;</code></a>
element.</li>
<li><code>&lt;uses-feature android:name="android.software.live_wallpaper" /&gt;</code>,
which tells Android Market that your application includes a live wallpaper
@ -89,7 +90,9 @@ available applications. When you declaring this feature, Android Market
displays your application only to users whose devices support live wallpapers,
while hiding it from other devices on which it would not be able to run. For
more information, see the documentation for the
<a href="../../../guide/topics/manifest/uses-feature-element.html"><code>&lt;uses-feature&gt;</code></a>
<a
href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code
&lt;uses-feature&gt;</a>
element.</li>
</ul>

4
docs/html/sdk/android-3.0.jd
View File

@ -353,8 +353,8 @@ loader for your activity or fragment.</p>
<p>For more information, read the <a
href="{@docRoot}guide/topics/providers/loaders.html">Loaders</a> documentation. You can also see
example code using loaders in the <a
href="{@docRoot}samples/ApiDemos/src/com/example/android/apis/app/FragmentListCursorLoader.html">
FragmentListCursorLoader</a> and <a
href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentListCursorLoader.html">FragmentListCursorLoader</a>
and <a
href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html">
LoaderThrottle</a> samples.</p>

2
docs/html/sdk/preview/start.jd
View File

@ -46,7 +46,7 @@ To get the samples, download them from the SDK repository using the Android SDK
the samples are located in <code>&lt;sdk_root&gt;/samples/android-Honeycomb</code>. The list of links
below helps you find samples for the features you are interested in:</p>
<ul>
<li><a href="{@docRoot}resources/samples/Honeycomb-Gallery/index.html">Honeycomb Gallery</a> -
<li><a href="{@docRoot}resources/samples/HoneycombGallery/index.html">Honeycomb Gallery</a> -
A demo application highlighting how to use some of the new APIs in Honeycomb, including fragments, the action bar,
drag and drop, transition animations, and a stack widget.</li>
<li><a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/index.html#Fragment">Fragments</a>