Lines Matching refs:link
128 fragment, you must extend the {@link android.app.Fragment} class and implement several lifecycle
129 callback methods, similar to an {@link android.app.Activity}. You can then combine multiple
153 <p>To manage the fragments in your activity, you must use the {@link
158 <p>To perform a transaction, such as add or remove a fragment, you must create a {@link
159 android.app.FragmentTransaction}. You can then call methods such as {@link
160 android.app.FragmentTransaction#add add()} {@link android.app.FragmentTransaction#remove
161 remove()}, or {@link android.app.FragmentTransaction#replace replace()}. Once you've applied all
162 the changes you want to perform for the transaction, you must call {@link
199 which the system delivers to your activity's {@link android.app.Activity#onOptionsItemSelected
204 attribute, then call {@link android.app.ActionBar#setDisplayUseLogoEnabled
237 <p>To start using the clipboard, get the global {@link android.content.ClipboardManager} object
238 by calling {@link android.content.Context#getSystemService getSystemService(CLIPBOARD_SERVICE)}.</p>
240 <p>To copy an item to the clipboard, you need to create a new {@link
241 android.content.ClipData} object, which holds one or more {@link android.content.ClipData.Item}
242 objects, each describing a single entity. To create a {@link android.content.ClipData} object
243 containing just one {@link android.content.ClipData.Item}, you can use one of the helper methods,
244 such as {@link android.content.ClipData#newPlainText newPlainText()}, {@link
245 android.content.ClipData#newUri newUri()}, and {@link android.content.ClipData#newIntent
246 newIntent()}, which each return a {@link android.content.ClipData} object pre-loaded with the
247 {@link android.content.ClipData.Item} you provide.</p>
249 <p>To add the {@link android.content.ClipData} to the clipboard, pass it to {@link
250 android.content.ClipboardManager#setPrimaryClip setPrimaryClip()} for your instance of {@link
253 <p>You can then read a file from the clipboard (in order to paste it) by calling {@link
254 android.content.ClipboardManager#getPrimaryClip()} on the {@link
255 android.content.ClipboardManager}. Handling the {@link android.content.ClipData} you receive can
259 <p>The clipboard holds only one piece of clipped data (a {@link android.content.ClipData}
260 object) at a time, but one {@link android.content.ClipData} can contain multiple {@link
275 operation is the transfer of some kind of data—carried in a {@link android.content.ClipData}
276 object—from one place to another. The start and end point for the drag operation is a {@link
278 in the {@link android.view.View} class.</p>
281 defined by a {@link android.view.DragEvent} object—such as {@link
282 android.view.DragEvent#ACTION_DRAG_STARTED}, {@link android.view.DragEvent#ACTION_DRAG_ENTERED}, and
283 {@link android.view.DragEvent#ACTION_DROP}. Each view that wants to participate in a drag
286 <p>To begin dragging content in your activity, call {@link android.view.View#startDrag startDrag()}
287 on a {@link android.view.View}, providing a {@link android.content.ClipData} object that represents
288 the data to drag, a {@link android.view.View.DragShadowBuilder} to facilitate the "shadow"
289 that users see under their fingers while dragging, and an {@link java.lang.Object} that can share
292 <p>To accept a drag object in a {@link android.view.View} (receive the "drop"), register the view
293 with an {@link android.view.View.OnDragListener OnDragListener} by calling {@link
295 system calls {@link android.view.View.OnDragListener#onDrag onDrag()} for the {@link
296 android.view.View.OnDragListener OnDragListener}, which receives a {@link android.view.DragEvent}
297 describing the type of drag action has occurred (such as {@link
298 android.view.DragEvent#ACTION_DRAG_STARTED}, {@link android.view.DragEvent#ACTION_DRAG_ENTERED}, and
299 {@link android.view.DragEvent#ACTION_DROP}). During a drag, the system repeatedly calls {@link
301 stream of drag events. The receiving view can inquire the event type delivered to {@link
302 android.view.View#onDragEvent onDragEvent()} by calling {@link android.view.DragEvent#getAction
303 getAction()} on the {@link android.view.DragEvent}.</p>
305 <p class="note"><strong>Note:</strong> Although a drag event may carry a {@link
321 Home screen, including: {@link android.widget.GridView}, {@link android.widget.ListView}, {@link
322 android.widget.StackView}, {@link android.widget.ViewFlipper}, and {@link
325 <p>More importantly, you can use the new {@link android.widget.RemoteViewsService} to create app
326 widgets with collections, using widgets such as {@link android.widget.GridView}, {@link
327 android.widget.ListView}, and {@link android.widget.StackView} that are backed by remote data,
330 <p>The {@link android.appwidget.AppWidgetProviderInfo} class (defined in XML with an {@code
331 <appwidget-provider>} element) also supports two new fields: {@link
332 android.appwidget.AppWidgetProviderInfo#autoAdvanceViewId} and {@link
333 android.appwidget.AppWidgetProviderInfo#previewImage}. The {@link
336 {@link android.appwidget.AppWidgetProviderInfo#previewImage} field specifies a preview of what the
340 <p>To help create a preview image for your app widget (to specify in the {@link
355 <p>The {@link android.app.Notification} APIs have been extended to support more content-rich status
356 bar notifications, plus a new {@link android.app.Notification.Builder} class allows you to easily
357 create {@link android.app.Notification} objects.</p>
360 <li>Support for a large icon in the notification, using {@link
364 <li>Support for custom layouts in the status bar ticker, using {@link
366 <li>Support for custom notification layouts to include buttons with {@link
375 <p>New framework APIs facilitate asynchronous loading of data using the {@link
377 fragments to dynamically load data from worker threads. The {@link
379 a {@link android.content.ContentProvider}.</p>
381 <p>All you need to do is implement the {@link android.app.LoaderManager.LoaderCallbacks
383 changed, then call {@link android.app.LoaderManager#initLoader initLoader()} to initialize the
404 <p>You can initialize the respective {@link android.bluetooth.BluetoothProfile} by calling {@link
405 android.bluetooth.BluetoothAdapter#getProfileProxy getProfileProxy()} with either the {@link
406 android.bluetooth.BluetoothProfile#A2DP} or {@link android.bluetooth.BluetoothProfile#HEADSET}
407 profile constant and a {@link android.bluetooth.BluetoothProfile.ServiceListener} to receive
429 the system how to calculate the values for that given type, by implementing the {@link
432 <p>There are two animators you can use to animate the values of a property: {@link
433 android.animation.ValueAnimator} and {@link android.animation.ObjectAnimator}. The {@link
436 listen for the updates and process the data with your own logic. The {@link
437 android.animation.ObjectAnimator} is a subclass of {@link android.animation.ValueAnimator} and
439 That is, you give the {@link android.animation.ObjectAnimator} the object to animate, the
443 <p>Additionally, the {@link android.animation.LayoutTransition} class enables automatic transition
445 layout, create a {@link android.animation.LayoutTransition} object and set it on
446 any {@link android.view.ViewGroup} by calling {@link
449 animations, call {@link android.animation.LayoutTransition#setAnimator setAnimator()} on the {@link
450 android.animation.LayoutTransition} and provide a custom {@link android.animation.Animator},
451 such as a {@link android.animation.ValueAnimator} or {@link android.animation.ObjectAnimator}
469 <p>New {@link android.widget.AbsListView#CHOICE_MODE_MULTIPLE_MODAL} mode for {@link
471 from a {@link android.widget.ListView} or {@link android.widget.GridView}. When used in
476 <p>To enable multiple-choice selection, call {@link
478 {@link android.widget.AbsListView.MultiChoiceModeListener MultiChoiceModeListener} with {@link
482 Action Mode. The system notifies the {@link android.widget.AbsListView.MultiChoiceModeListener
483 MultiChoiceModeListener} when items are selected by calling {@link
499 <p>New methods to set the view properties include: {@link android.view.View#setAlpha
500 setAlpha()}, {@link
501 android.view.View#setBottom setBottom()}, {@link android.view.View#setLeft setLeft()}, {@link
502 android.view.View#setRight setRight()}, {@link android.view.View#setBottom setBottom()}, {@link
503 android.view.View#setPivotX setPivotX()}, {@link android.view.View#setPivotY setPivotY()}, {@link
504 android.view.View#setRotationX setRotationX()}, {@link android.view.View#setRotationY
505 setRotationY()}, {@link android.view.View#setScaleX setScaleX()}, {@link android.view.View#setScaleY
506 setScaleY()}, {@link android.view.View#setAlpha setAlpha()}, and others.</p>
517 view on its y-axis, supply {@link android.animation.ObjectAnimator} with the {@link
542 definitions, use one of several new {@link android.R.style#Theme_Holo Theme.Holo}
554 <li>{@link android.widget.AdapterViewAnimator}
555 <p>Base class for an {@link android.widget.AdapterView} that performs animations when switching
558 <li>{@link android.widget.AdapterViewFlipper}
559 <p>Simple {@link android.widget.ViewAnimator} that animates between two or more views that have
564 <li>{@link android.widget.CalendarView}
568 <li>{@link android.widget.ListPopupWindow}
570 suggestions when typing into an {@link android.widget.EditText} view.</p></li>
572 <li>{@link android.widget.NumberPicker}
579 <li>{@link android.widget.PopupMenu}
580 <p>Displays a {@link android.view.Menu} in a modal popup window that's anchored to a view. The
585 <li>{@link android.widget.SearchView}
591 <li>{@link android.widget.StackView}
620 <p>By default, a {@link android.view.View} has no layer specified. You can specify that the
621 view be backed by either a hardware or software layer, specified by values {@link
622 android.view.View#LAYER_TYPE_HARDWARE} and {@link android.view.View#LAYER_TYPE_SOFTWARE}, using
623 {@link android.view.View#setLayerType setLayerType()} or the <a
634 <p>For more information, see the {@link android.view.View#LAYER_TYPE_HARDWARE} and {@link
660 <p>Camcorder APIs now support the ability to record time lapse video. The {@link
666 <p>New {@link android.graphics.SurfaceTexture} allows you to capture an image stream as an OpenGL ES
667 texture. By calling {@link android.hardware.Camera#setPreviewTexture setPreviewTexture()} for your
668 {@link android.hardware.Camera} instance, you can specify the {@link
682 <p>The {@link android.media.ExifInterface} includes new fields for photo aperture, ISO, and exposure
687 <p>New {@link android.media.CamcorderProfile#hasProfile hasProfile()} method and several video
688 quality profiles (such as {@link android.media.CamcorderProfile#QUALITY_1080P}, {@link
689 android.media.CamcorderProfile#QUALITY_720P}, {@link
723 <p>You can find all of the DRM APIs in the {@link android.drm} package.</p></li>
733 see {@link android.view.KeyEvent#META_CTRL_ON} and related fields.</li>
737 querying {@link android.view.KeyCharacterMap#getKeyboardType()} and checking for {@link
740 <li>{@link android.widget.TextView} now supports keyboard-based cut, copy, paste, and select-all,
744 <li>{@link android.view.KeyEvent} adds several new methods to make it easier to check the key
745 modifier state correctly and consistently. See {@link android.view.KeyEvent#hasModifiers(int)},
746 {@link android.view.KeyEvent#hasNoModifiers()},
747 {@link android.view.KeyEvent#metaStateHasModifiers(int,int) metaStateHasModifiers()},
748 {@link android.view.KeyEvent#metaStateHasNoModifiers(int) metaStateHasNoModifiers()}.</li>
750 <li>Applications can implement custom keyboard shortcuts by subclassing {@link
751 android.app.Activity}, {@link android.app.Dialog}, or {@link android.view.View} and implementing
752 {@link android.app.Activity#onKeyShortcut onKeyShortcut()}. The framework calls this method
758 element (or with {@link android.view.MenuItem#setShortcut setShortcut()}).</li>
760 <li>Android 3.0 includes a new "virtual keyboard" device with the id {@link
786 <li>The {@link android.R.attr#splitMotionEvents android:splitMotionEvents} attribute for view groups
797 <li>The {@link android.R.attr#windowEnableSplitTouch android:windowEnableSplitTouch} style property
824 <li>New {@link android.webkit.WebViewFragment} class to create a fragment composed of a
825 {@link android.webkit.WebView}.</li>
826 <li>New {@link android.webkit.WebSettings} methods:
828 <li>{@link
830 the on-screen zoom controls while still allowing the user to zoom with finger gestures ({@link
833 <li>New {@link android.webkit.WebSettings} method, {@link
839 <li>New {@link android.webkit.WebView} methods:
841 <li>{@link android.webkit.WebView#onPause onPause()} callback, to pause any processing
844 <li>{@link android.webkit.WebView#onResume onResume()} callback, to resume processing
845 associated with the WebView, which was paused during {@link android.webkit.WebView#onPause
847 <li>{@link android.webkit.WebView#saveWebArchive saveWebArchive()} allows you to save the
849 <li>{@link android.webkit.WebView#showFindDialog showFindDialog()} initiates a text search in
896 <p>New classes, {@link android.util.JsonReader} and {@link android.util.JsonWriter}, help you
897 read and write JSON streams. The new APIs complement the {@link org.json} classes, which manipulate
900 <p>You can create an instance of {@link android.util.JsonReader} by calling
901 its constructor method and passing the {@link java.io.InputStreamReader} that feeds the JSON string.
902 Then begin reading an object by calling {@link android.util.JsonReader#beginObject()}, read a
903 key name with {@link android.util.JsonReader#nextName()}, read the value using methods
904 respective to the type, such as {@link android.util.JsonReader#nextString()} and {@link
905 android.util.JsonReader#nextInt()}, and continue doing so while {@link
908 <p>You can create an instance of {@link android.util.JsonWriter} by calling its constructor and
909 passing the appropriate {@link java.io.OutputStreamWriter}. Then write the JSON data in a manner
910 similar to the reader, using {@link android.util.JsonWriter#name name()} to add a property name
911 and an appropriate {@link android.util.JsonWriter#value value()} method to add the respective
914 <p>These classes are strict by default. The {@link android.util.JsonReader#setLenient setLenient()}
916 parse mode is also compatible with the {@link org.json}'s default parser.</p>
930 <li>{@link android.content.pm.PackageManager#FEATURE_FAKETOUCH "android.hardware.faketouch"}
940 should declare {@link
945 <p>All devices that include a touchscreen also support {@link
960 <li>{@link android.Manifest.permission#BIND_REMOTEVIEWS
964 element for an implementation of {@link android.widget.RemoteViewsService}. For example, when
965 creating an App Widget that uses {@link android.widget.RemoteViewsService} to populate a