diff options
Diffstat (limited to 'docs/html/guide/components')
| -rw-r--r-- | docs/html/guide/components/activities.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/components/fragments.jd | 14 | ||||
| -rw-r--r-- | docs/html/guide/components/index.jd | 10 | ||||
| -rw-r--r-- | docs/html/guide/components/loaders.jd | 30 | ||||
| -rw-r--r-- | docs/html/guide/components/processes-and-threads.jd | 2 |
5 files changed, 29 insertions, 29 deletions
diff --git a/docs/html/guide/components/activities.jd b/docs/html/guide/components/activities.jd index 070154d805e7..e757288424d8 100644 --- a/docs/html/guide/components/activities.jd +++ b/docs/html/guide/components/activities.jd @@ -622,7 +622,7 @@ android.app.Activity#onSaveInstanceState onSaveInstanceState()}.</p> <p>The system calls {@link android.app.Activity#onSaveInstanceState onSaveInstanceState()} before making the activity vulnerable to destruction. The system passes this method -a {@link android.os.Bundle} in which you can save +a {@link android.os.Bundle} in which you can save state information about the activity as name-value pairs, using methods such as {@link android.os.Bundle#putString putString()} and {@link android.os.Bundle#putInt putInt()}. Then, if the system kills your application diff --git a/docs/html/guide/components/fragments.jd b/docs/html/guide/components/fragments.jd index f9c2a26d62e9..951d04211bde 100644 --- a/docs/html/guide/components/fragments.jd +++ b/docs/html/guide/components/fragments.jd @@ -36,7 +36,7 @@ parent.link=activities.html <li>{@link android.app.FragmentManager}</li> <li>{@link android.app.FragmentTransaction}</li> </ol> - + <h2>See also</h2> <ol> <li><a href="{@docRoot}training/basics/fragments/index.html">Building a Dynamic UI with Fragments</a></li> @@ -306,7 +306,7 @@ ID for a fragment:</p> <ul> <li>Supply the {@code android:id} attribute with a unique ID.</li> <li>Supply the {@code android:tag} attribute with a unique string.</li> - <li>If you provide neither of the previous two, the system uses the ID of the container + <li>If you provide neither of the previous two, the system uses the ID of the container view.</li> </ul> </div> @@ -365,7 +365,7 @@ findFragmentByTag()}.</p> <p>For an example activity that uses a fragment as a background worker, without a UI, see the {@code FragmentRetainInstance.java} sample, which is included in the SDK samples (available through the -Android SDK Manager) and located on your system as +Android SDK Manager) and located on your system as <code><sdk_root>/APIDemos/app/src/main/java/com/example/android/apis/app/FragmentRetainInstance.java</code>.</p> @@ -381,7 +381,7 @@ get it, call {@link android.app.Activity#getFragmentManager()} from your activit <li>Get fragments that exist in the activity, with {@link android.app.FragmentManager#findFragmentById findFragmentById()} (for fragments that provide a UI in the activity layout) or {@link android.app.FragmentManager#findFragmentByTag -findFragmentByTag()} (for fragments that do or don't provide a UI).</li> +findFragmentByTag()} (for fragments that do or don't provide a UI).</li> <li>Pop fragments off the back stack, with {@link android.app.FragmentManager#popBackStack()} (simulating a <em>Back</em> command by the user).</li> <li>Register a listener for changes to the back stack, with {@link @@ -568,7 +568,7 @@ public static class FragmentA extends ListFragment { <p>If the activity has not implemented the interface, then the fragment throws a {@link java.lang.ClassCastException}. -On success, the {@code mListener} member holds a reference to activity's implementation of +On success, the {@code mListener} member holds a reference to activity's implementation of {@code OnArticleSelectedListener}, so that fragment A can share events with the activity by calling methods defined by the {@code OnArticleSelectedListener} interface. For example, if fragment A is an extension of {@link android.app.ListFragment}, each time @@ -798,7 +798,7 @@ android.widget.FrameLayout}), or start a new activity (where the fragment can be <p>The second fragment, {@code DetailsFragment} shows the play summary for the item selected from the list from {@code TitlesFragment}:</p> - + {@sample development/samples/ApiDemos/src/com/example/android/apis/app/FragmentLayout.java details} <p>Recall from the {@code TitlesFragment} class, that, if the user clicks a list item and the @@ -811,7 +811,7 @@ the selected play summary when the screen is in portrait orientation:</p> {@sample development/samples/ApiDemos/src/com/example/android/apis/app/FragmentLayout.java details_activity} - + <p>Notice that this activity finishes itself if the configuration is landscape, so that the main activity can take over and display the {@code DetailsFragment} alongside the {@code TitlesFragment}. This can happen if the user begins the {@code DetailsActivity} while in portrait orientation, but diff --git a/docs/html/guide/components/index.jd b/docs/html/guide/components/index.jd index 811d015b82bc..d596b3be3462 100644 --- a/docs/html/guide/components/index.jd +++ b/docs/html/guide/components/index.jd @@ -1,7 +1,7 @@ page.title=App Components page.landing=true -page.landing.intro=Android's application framework lets you create rich and innovative apps using a set of reusable components. This section explains how you can build the components that define the building blocks of your app and how to connect them together using intents. -page.metaDescription=Android's application framework lets you create rich and innovative apps using a set of reusable components. This section explains how you can build the components that define the building blocks of your app and how to connect them together using intents. +page.landing.intro=Android's application framework lets you create rich and innovative apps using a set of reusable components. This section explains how you can build the components that define the building blocks of your app and how to connect them together using intents. +page.metaDescription=Android's application framework lets you create rich and innovative apps using a set of reusable components. This section explains how you can build the components that define the building blocks of your app and how to connect them together using intents. page.landing.image=images/develop/app_components.png page.image=images/develop/app_components.png @@ -11,7 +11,7 @@ page.image=images/develop/app_components.png <div class="col-6"> <h3>Blog Articles</h3> - + <a href="http://android-developers.blogspot.com/2012/05/using-dialogfragments.html"> <h4>Using DialogFragments</h4> <p>In this post, I’ll show how to use DialogFragments with the v4 support library (for backward compatibility on pre-Honeycomb devices) to show a simple edit dialog and return a result to the calling Activity using an interface.</p> @@ -21,7 +21,7 @@ page.image=images/develop/app_components.png <h4>Fragments For All</h4> <p>Today we’ve released a static library that exposes the same Fragments API (as well as the new LoaderManager and a few other classes) so that applications compatible with Android 1.6 or later can use fragments to create tablet-compatible user interfaces. </p> </a> - + <a href="http://android-developers.blogspot.com/2010/07/multithreading-for-performance.html"> <h4>Multithreading for Performance</h4> @@ -33,7 +33,7 @@ handled in a different thread.</p> <div class="col-6"> <h3>Training</h3> - + <a href="http://developer.android.com/training/basics/activity-lifecycle/index.html"> <h4>Managing the Activity Lifecycle</h4> <p>This class explains important lifecycle callback methods that each Activity diff --git a/docs/html/guide/components/loaders.jd b/docs/html/guide/components/loaders.jd index ddd513b2a2c5..7c4baa846ae3 100644 --- a/docs/html/guide/components/loaders.jd +++ b/docs/html/guide/components/loaders.jd @@ -21,14 +21,14 @@ parent.link=activities.html </ol> </li> </ol> - + <h2>Key classes</h2> <ol> <li>{@link android.app.LoaderManager}</li> <li>{@link android.content.Loader}</li> - </ol> - + </ol> + <h2>Related samples</h2> <ol> <li> <a @@ -53,7 +53,7 @@ content changes.</li> recreated after a configuration change. Thus, they don't need to re-query their data.</li> </ul> - + <h2 id="summary">Loader API Summary</h2> <p>There are multiple classes and interfaces that may be involved in using @@ -131,10 +131,10 @@ of {@link android.content.Loader} or {@link android.content.AsyncTaskLoader} to load data from some other source.</li> <li>An implementation for {@link android.app.LoaderManager.LoaderCallbacks}. This is where you create new loaders and manage your references to existing -loaders.</li> +loaders.</li> <li>A way of displaying the loader's data, such as a {@link android.widget.SimpleCursorAdapter}.</li> - <li>A data source, such as a {@link android.content.ContentProvider}, when using a + <li>A data source, such as a {@link android.content.ContentProvider}, when using a {@link android.content.CursorLoader}.</li> </ul> <h3 id="starting">Starting a Loader</h3> @@ -142,7 +142,7 @@ android.widget.SimpleCursorAdapter}.</li> <p>The {@link android.app.LoaderManager} manages one or more {@link android.content.Loader} instances within an {@link android.app.Activity} or {@link android.app.Fragment}. There is only one {@link -android.app.LoaderManager} per activity or fragment.</p> +android.app.LoaderManager} per activity or fragment.</p> <p>You typically initialize a {@link android.content.Loader} within the activity's {@link @@ -159,13 +159,13 @@ the following parameters:</p> <ul> <li>A unique ID that identifies the loader. In this example, the ID is 0.</li> <li>Optional arguments to supply to the loader at -construction (<code>null</code> in this example).</li> +construction (<code>null</code> in this example).</li> <li>A {@link android.app.LoaderManager.LoaderCallbacks} implementation, which the {@link android.app.LoaderManager} calls to report loader events. In this example, the local class implements the {@link android.app.LoaderManager.LoaderCallbacks} interface, so it passes a reference -to itself, {@code this}.</li> +to itself, {@code this}.</li> </ul> <p>The {@link android.app.LoaderManager#initLoader initLoader()} call ensures that a loader is initialized and active. It has two possible outcomes:</p> @@ -196,7 +196,7 @@ the life of the loader automatically. The {@link android.app.LoaderManager} starts and stops loading when necessary, and maintains the state of the loader and its associated content. As this implies, you rarely interact with loaders directly (though for an example of using loader methods to fine-tune a loader's -behavior, see the <a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html"> LoaderThrottle</a> sample). +behavior, see the <a href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderThrottle.html"> LoaderThrottle</a> sample). You most commonly use the {@link android.app.LoaderManager.LoaderCallbacks} methods to intervene in the loading process when particular events occur. For more discussion of this topic, see <a @@ -249,7 +249,7 @@ Instantiate and return a new {@link android.content.Loader} for the given ID. — Called when a previously created loader has finished its load. </li></ul> <ul> - <li>{@link android.app.LoaderManager.LoaderCallbacks#onLoaderReset onLoaderReset()} + <li>{@link android.app.LoaderManager.LoaderCallbacks#onLoaderReset onLoaderReset()} — Called when a previously created loader is being reset, thus making its data unavailable. </li> @@ -344,11 +344,11 @@ public void onLoadFinished(Loader<Cursor> loader, Cursor data) { <h4 id="onLoaderReset">onLoaderReset</h4> -<p>This method is called when a previously created loader is being reset, thus +<p>This method is called when a previously created loader is being reset, thus making its data unavailable. This callback lets you find out when the data is about to be released so you can remove your reference to it. </p> -<p>This implementation calls -{@link android.widget.SimpleCursorAdapter#swapCursor swapCursor()} +<p>This implementation calls +{@link android.widget.SimpleCursorAdapter#swapCursor swapCursor()} with a value of <code>null</code>:</p> <pre> @@ -370,7 +370,7 @@ public void onLoaderReset(Loader<Cursor> loader) { android.app.Fragment} that displays a {@link android.widget.ListView} containing the results of a query against the contacts content provider. It uses a {@link android.content.CursorLoader} to manage the query on the provider.</p> - + <p>For an application to access a user's contacts, as shown in this example, its manifest must include the permission {@link android.Manifest.permission#READ_CONTACTS READ_CONTACTS}.</p> diff --git a/docs/html/guide/components/processes-and-threads.jd b/docs/html/guide/components/processes-and-threads.jd index 7bb3c65a373b..250799853c92 100644 --- a/docs/html/guide/components/processes-and-threads.jd +++ b/docs/html/guide/components/processes-and-threads.jd @@ -121,7 +121,7 @@ required to keep the user interface responsive.</p></li> <ul> <li>It hosts an {@link android.app.Activity} that is not in the foreground, but is still -visible to the user (its {@link android.app.Activity#onPause onPause()} method has been called). +visible to the user (its {@link android.app.Activity#onPause onPause()} method has been called). This might occur, for example, if the foreground activity started a dialog, which allows the previous activity to be seen behind it.</li> |