From 4e2c9dc74b74b1ba10793177475a599f75fbb18b Mon Sep 17 00:00:00 2001 From: Scott Main Date: Tue, 23 Jul 2013 19:35:17 -0700 Subject: update all links to the support library Change-Id: I173e3690148e5de3020bfdca8087906faa56b13b --- docs/html/guide/topics/ui/accessibility/apps.jd | 8 ++++---- docs/html/guide/topics/ui/accessibility/checklist.jd | 2 +- docs/html/guide/topics/ui/accessibility/services.jd | 4 ++-- docs/html/guide/topics/ui/controls/pickers.jd | 8 ++++---- docs/html/guide/topics/ui/dialogs.jd | 2 +- docs/html/guide/topics/ui/layout/listview.jd | 2 +- docs/html/guide/topics/ui/notifiers/notifications.jd | 2 +- 7 files changed, 14 insertions(+), 14 deletions(-) (limited to 'docs/html/guide/topics') diff --git a/docs/html/guide/topics/ui/accessibility/apps.jd b/docs/html/guide/topics/ui/accessibility/apps.jd index 13b4538..da24d03 100644 --- a/docs/html/guide/topics/ui/accessibility/apps.jd +++ b/docs/html/guide/topics/ui/accessibility/apps.jd @@ -351,7 +351,7 @@ following approaches:

  • If your application targets Android 4.0 (API level 14) and higher, override and implement the accessibility methods listed above directly in your custom view class.
  • If your custom view is intended to be compatible with Android 1.6 (API Level 4) and above, add -the Android Support Library, revision 5 or +the Android Support Library, revision 5 or higher, to your project. Then, within your custom view class, call the {@link android.support.v4.view.ViewCompat#setAccessibilityDelegate ViewCompat.setAccessibilityDelegate()} method to implement the accessibility methods @@ -490,7 +490,7 @@ appropriate feedback to users.

    The example code below shows how override these three methods by using {@link android.support.v4.view.ViewCompat#setAccessibilityDelegate ViewCompat.setAccessibilityDelegate()}. Note that this sample code requires that the Android -Support Library for API Level 4 (revision +Support Library for API Level 4 (revision 5 or higher) is added to your project.

    @@ -534,7 +534,7 @@ ViewCompat.setAccessibilityDelegate(new AccessibilityDelegateCompat() {
 
 
    In applications targeting Android 4.0 (API Level 14) and higher, you can implement these methods
 directly in your custom view class. For another example of this approach, see the Android
-Support Library (revision 5 or higher)
+Support Library (revision 5 or higher)
 sample {@code AccessibilityDelegateSupportActivity} in
 ({@code <sdk>/extras/android/support/v4/samples/Support4Demos/}).
    
 
@@ -594,7 +594,7 @@ methods.
    
   example implementation of this accessibility feature, see
   {@code AccessibilityNodeProviderActivity} in the ApiDemos sample project. You can implement a
   virtual view hierarchy that is compatible with Android 1.6 and later by using the
-  Support Library with the
+  Support Library with the
   {@link android.support.v4.view.ViewCompat#getAccessibilityNodeProvider
   ViewCompat.getAccessibilityNodeProvider()} method and providing an implementation with
   {@link android.support.v4.view.accessibility.AccessibilityNodeProviderCompat}.
    
diff --git a/docs/html/guide/topics/ui/accessibility/checklist.jd b/docs/html/guide/topics/ui/accessibility/checklist.jd
index 9473d1b..960cca2 100644
--- a/docs/html/guide/topics/ui/accessibility/checklist.jd
+++ b/docs/html/guide/topics/ui/accessibility/checklist.jd
@@ -73,7 +73,7 @@ helps you focus on the key development issues to get the details of accessibilit
     your application, 
     implement accessibility interfaces for your custom views and provide content descriptions.
     For custom controls that are intended to be compatible with versions of Android back to 1.6,
-    use the Support Library to implement
+    use the Support Library to implement
     the latest accessibility features.
  • No audio-only feedback: Audio feedback must always have a secondary feedback mechanism to support users who are deaf or hard of hearing. For example, a sound alert diff --git a/docs/html/guide/topics/ui/accessibility/services.jd b/docs/html/guide/topics/ui/accessibility/services.jd index 2a6fe7a..4bd752f 100644 --- a/docs/html/guide/topics/ui/accessibility/services.jd +++ b/docs/html/guide/topics/ui/accessibility/services.jd @@ -55,7 +55,7 @@ accessibility service.

    The ability for you to build and deploy accessibility services was introduced with Android 1.6 (API Level 4) and received significant improvements with Android 4.0 (API Level 14). The Android - Support Library was also updated with + Support Library was also updated with the release of Android 4.0 to provide support for these enhanced accessibility features back to Android 1.6. Developers aiming for widely compatible accessibility services are encouraged to use the Support Library and develop for the more advanced accessibility features introduced in @@ -448,7 +448,7 @@ android.accessibilityservice.AccessibilityService} and can be used as a base for accessibility services that are compatible with Android 1.6 (API Level 4) and higher.

  • TaskBackService - This service is based on the enhanced accessibility APIs introduced in Android 4.0 (API Level -14). However, you can use the Android Support +14). However, you can use the Android Support Libary to substitute classes introduced in later API levels (e.g., {@link android.view.accessibility.AccessibilityRecord}, {@link android.view.accessibility.AccessibilityNodeInfo} diff --git a/docs/html/guide/topics/ui/controls/pickers.jd b/docs/html/guide/topics/ui/controls/pickers.jd index a0e7afb..4c55840 100644 --- a/docs/html/guide/topics/ui/controls/pickers.jd +++ b/docs/html/guide/topics/ui/controls/pickers.jd @@ -47,11 +47,11 @@ such as in a basic dialog on handsets or as an embedded part of the layout on la

    Although {@link android.app.DialogFragment} was first added to the platform in Android 3.0 (API level 11), if your app supports versions of Android older than 3.0—even as low as Android 1.6—you can use the {@link android.support.v4.app.DialogFragment} class that's available in -the support library for backward +the support library for backward compatibility.

    Note: The code samples below show how to create dialogs for a time -picker and date picker using the support +picker and date picker using the support library APIs for {@link android.support.v4.app.DialogFragment}. If your app's {@code minSdkVersion} is 11 or higher, you can instead use the platform version of {@link android.app.DialogFragment}.

    @@ -67,7 +67,7 @@ fragment's {@link android.support.v4.app.DialogFragment#onCreateDialog onCreateD

    Note: If your app supports versions of Android older than 3.0, be sure you've set up your Android project with the support library as described in Setting Up a Project to Use a +href="{@docRoot}tools/support-library/setup.html">Setting Up a Project to Use a Library.

    Extending DialogFragment for a time picker

    @@ -172,7 +172,7 @@ fragment's {@link android.support.v4.app.DialogFragment#onCreateDialog onCreateD

    Note: If your app supports versions of Android older than 3.0, be sure you've set up your Android project with the support library as described in Setting Up a Project to Use a +href="{@docRoot}tools/support-library/setup.html">Setting Up a Project to Use a Library.

    Extending DialogFragment for a date picker

    diff --git a/docs/html/guide/topics/ui/dialogs.jd b/docs/html/guide/topics/ui/dialogs.jd index 7f48eac..09767bf 100644 --- a/docs/html/guide/topics/ui/dialogs.jd +++ b/docs/html/guide/topics/ui/dialogs.jd @@ -97,7 +97,7 @@ object. If you'd like to create a date or time picker, you should instead read t Because the {@link android.app.DialogFragment} class was originally added with Android 3.0 (API level 11), this document describes how to use the {@link android.support.v4.app.DialogFragment} class that's provided with the Support Library. By adding this library +href="{@docRoot}tools/support-library/index.html">Support Library. By adding this library to your app, you can use {@link android.support.v4.app.DialogFragment} and a variety of other APIs on devices running Android 1.6 or higher. If the minimum version your app supports is API level 11 or higher, then you can use the framework version of {@link diff --git a/docs/html/guide/topics/ui/layout/listview.jd b/docs/html/guide/topics/ui/layout/listview.jd index 6cdd725..f8315c5 100644 --- a/docs/html/guide/topics/ui/layout/listview.jd +++ b/docs/html/guide/topics/ui/layout/listview.jd @@ -48,7 +48,7 @@ displays the results.

    Although the {@link android.support.v4.content.CursorLoader} APIs were first introduced in Android 3.0 (API level 11), they are also available in the Support Library so that your app may use them +href="{@docRoot}tools/support-library/index.html">Support Library so that your app may use them while supporting devices running Android 1.6 or higher.

    For more information about using a {@link diff --git a/docs/html/guide/topics/ui/notifiers/notifications.jd b/docs/html/guide/topics/ui/notifiers/notifications.jd index 05ec279..e0c87d7 100644 --- a/docs/html/guide/topics/ui/notifiers/notifications.jd +++ b/docs/html/guide/topics/ui/notifiers/notifications.jd @@ -94,7 +94,7 @@ page.title=Notifications

    Note: Except where noted, this guide refers to the {@link android.support.v4.app.NotificationCompat.Builder NotificationCompat.Builder} class - in the version 4 Support Library. + in the version 4 Support Library. The class {@link android.app.Notification.Builder Notification.Builder} was added in Android 3.0.

    -- cgit v1.1