Lines Matching full:link
3 parent.link=activities.html
27 <li>{@link android.app.LoaderManager}</li>
28 <li>{@link android.content.Loader}</li>
47 <li>They are available to every {@link android.app.Activity} and {@link
68 <td>{@link android.app.LoaderManager}</td>
69 <td>An abstract class associated with an {@link android.app.Activity} or
70 {@link android.app.Fragment} for managing one or more {@link
72 longer-running operations in conjunction with the {@link android.app.Activity}
73 or {@link android.app.Fragment} lifecycle; the most common use of this is with a
74 {@link android.content.CursorLoader}, however applications are free to write
78 There is only one {@link android.app.LoaderManager} per activity or fragment. But a {@link android.app.LoaderManager} can have
82 <td>{@link android.app.LoaderManager.LoaderCallbacks}</td>
83 <td>A callback interface for a client to interact with the {@link
84 android.app.LoaderManager}. For example, you use the {@link
89 <td>{@link android.content.Loader}</td>
91 the base class for a loader. You would typically use {@link
97 <td>{@link android.content.AsyncTaskLoader}</td>
98 <td>Abstract loader that provides an {@link android.os.AsyncTask} to do the work.</td>
101 <td>{@link android.content.CursorLoader}</td>
102 <td>A subclass of {@link android.content.AsyncTaskLoader} that queries the
103 {@link android.content.ContentResolver} and returns a {@link
104 android.database.Cursor}. This class implements the {@link
106 building on {@link android.content.AsyncTaskLoader} to perform the cursor query
108 this loader is the best way to asynchronously load data from a {@link
116 for each loader you create, but you'll always need a reference to the {@link
118 of a {@link android.content.Loader} class such as {@link
126 <li>An {@link android.app.Activity} or {@link android.app.Fragment}.</li>
127 <li>An instance of the {@link android.app.LoaderManager}.</li>
128 <li>A {@link android.content.CursorLoader} to load data backed by a {@link
130 of {@link android.content.Loader} or {@link android.content.AsyncTaskLoader} to
132 <li>An implementation for {@link android.app.LoaderManager.LoaderCallbacks}.
135 <li>A way of displaying the loader's data, such as a {@link
137 <li>A data source, such as a {@link android.content.ContentProvider}, when using a
138 {@link android.content.CursorLoader}.</li>
142 <p>The {@link android.app.LoaderManager} manages one or more {@link
143 android.content.Loader} instances within an {@link android.app.Activity} or
144 {@link android.app.Fragment}. There is only one {@link
148 initialize a {@link android.content.Loader} within the activity's {@link
150 {@link android.app.Fragment#onActivityCreated onActivityCreated()} method. You
157 <p>The {@link android.app.LoaderManager#initLoader initLoader()} method takes
164 <li>A {@link android.app.LoaderManager.LoaderCallbacks} implementation, which
165 the {@link android.app.LoaderManager} calls to report loader events. In this
166 example, the local class implements the {@link
170 <p>The {@link android.app.LoaderManager#initLoader initLoader()} call ensures that a loader
176 {@link android.app.LoaderManager#initLoader initLoader()} triggers the
177 {@link android.app.LoaderManager.LoaderCallbacks} method {@link android.app.LoaderManager.LoaderCallbacks#onCreateLoader onCreateLoader()}.
182 <p>In either case, the given {@link android.app.LoaderManager.LoaderCallbacks}
186 data, then the system calls {@link
188 immediately (during {@link android.app.LoaderManager#initLoader initLoader()}),
192 <p>Note that the {@link android.app.LoaderManager#initLoader initLoader()}
193 method returns the {@link android.content.Loader} that is created, but you don't
194 need to capture a reference to it. The {@link android.app.LoaderManager} manages
195 the life of the loader automatically. The {@link android.app.LoaderManager}
200 You most commonly use the {@link
207 <p>When you use {@link android.app.LoaderManager#initLoader initLoader()}, as
212 <p>To discard your old data, you use {@link
214 implementation of {@link android.widget.SearchView.OnQueryTextListener} restarts
230 <p>{@link android.app.LoaderManager.LoaderCallbacks} is a callback interface
231 that lets a client interact with the {@link android.app.LoaderManager}. </p>
232 <p>Loaders, in particular {@link android.content.CursorLoader}, are expected to
234 data across the activity or fragment's {@link android.app.Activity#onStop
235 onStop()} and {@link android.app.Activity#onStart onStart()} methods, so that
237 reload. You use the {@link android.app.LoaderManager.LoaderCallbacks} methods
241 <p>{@link android.app.LoaderManager.LoaderCallbacks} includes these
244 <li>{@link android.app.LoaderManager.LoaderCallbacks#onCreateLoader onCreateLoader()} —
245 Instantiate and return a new {@link android.content.Loader} for the given ID.
248 <li> {@link android.app.LoaderManager.LoaderCallbacks#onLoadFinished onLoadFinished()}
252 <li>{@link android.app.LoaderManager.LoaderCallbacks#onLoaderReset onLoaderReset()}
261 <p>When you attempt to access a loader (for example, through {@link
263 the loader specified by the ID exists. If it doesn't, it triggers the {@link
264 android.app.LoaderManager.LoaderCallbacks} method {@link
266 is where you create a new loader. Typically this will be a {@link
267 android.content.CursorLoader}, but you can implement your own {@link
270 <p>In this example, the {@link
272 callback method creates a {@link android.content.CursorLoader}. You must build
273 the {@link android.content.CursorLoader} using its constructor method, which
274 requires the complete set of information needed to perform a query to the {@link
327 using it. For example, if the data is a cursor from a {@link
328 android.content.CursorLoader}, you should not call {@link
330 placed in a {@link android.widget.CursorAdapter}, you should use the {@link
332 old {@link android.database.Cursor} is not closed. For example:</p>
351 {@link android.widget.SimpleCursorAdapter#swapCursor swapCursor()}
369 <p>As an example, here is the full implementation of a {@link
370 android.app.Fragment} that displays a {@link android.widget.ListView} containing
371 the results of a query against the contacts content provider. It uses a {@link
376 {@link android.Manifest.permission#READ_CONTACTS READ_CONTACTS}.</p>
