From 26aec76b58c165fa8ea7aa82aaa55d7c512a3124 Mon Sep 17 00:00:00 2001 From: Quddus Chong Date: Tue, 24 Jun 2014 10:14:12 -0700 Subject: [PATCH] docs: Updated L Preview Highlights (hopefully final). Change-Id: Ife51fb950b0e3c7f21e69024c435ca62e6906d5b --- docs/html/preview/api-overview.jd | 101 ++++++++++++++---------------- 1 file changed, 47 insertions(+), 54 deletions(-) diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index 20764be7d4943..f992bf909f54c 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -30,12 +30,7 @@ sdk.platform.apiLevel=20
  • WebView updates
    • -
  • User Input -
      -
    1. IME bug fixes and improvements
      2. -
    -
    • -
  • Animation & Graphics +
  • Graphics
    1. Support for OpenGL ES 3.1
    2. Android Extension Pack
      3. @@ -82,6 +77,11 @@ sdk.platform.apiLevel=20
    3. Testing and accessibility improvements
    • +
  • IME +
      +
    1. Easier switching between input languages
      2. +
    +
  • Manifest Declarations
    1. Declarable required features
      2. @@ -297,11 +297,9 @@ notification object, attach the replacement notification to it through the

      Notifications metadata

      The L Developer Preview uses metadata associated with your app notifications -to sort the notifications more intelligently. The metadata you set also -controls how the system presents your app notifications when the user is in Do -Not Disturb mode. To set the metadata, call the following methods in -{@code android.app.Notification.Builder} when you construct the -notification:

      +to sort the notifications more intelligently. To set the metadata, call the +following methods in {@code android.app.Notification.Builder} when you +construct the notification:

      • {@code setCategory()}. Depending on the message category, this tells @@ -322,11 +320,11 @@ people as being more important.

        • In previous releases, the Recents screen could only display a single task for each app that the user interacted with -most recently. The L Developer Preview enables your app to open more tasks as +most recently. Now your app can open more tasks as needed for additional concurrent activities for documents. -This feature facilitates multitasking -by letting users quickly switch between individual activities and documents -from the Recents screen, with a consistent switching experience across all apps. +This feature facilitates multitasking by letting users quickly switch between +individual activities and documents from the Recents screen, with a consistent +switching experience across all apps. Examples of such concurrent tasks might include open tabs in a web browser app, documents in a productivity app, concurrent matches in a game, or chats in a messaging app. Your app can manage its tasks @@ -362,35 +360,12 @@ as well as bug fixes. The default user-agent string for a been updated to incorporate 36.0.0.0 as the version number.

        Additionally, this release brings support for the -WebAudio, -WebGL, and -WebRTC open standards. To learn more about -the new features included in this release, see WebView for Android.

        +WebAudio, +WebGL, and +WebRTC open standards. To learn more about +the new features included in this release, see WebView for Android.

        -

        User Input

        - -

        IME bug fixes and improvements

        - -

        Beginning in the L Developer Preview, users can more easily switch between -all input -method editors (IME) supported by the platform. Performing the designated -switching action (usually touching a Globe icon on the soft keyboard) will cycle -among all such IMEs. This change takes place in -{@link android.view.inputmethod.InputMethodManager#shouldOfferSwitchingToNextInputMethod -InputMethodManager.shouldOfferSwitchingToNextInputMethod()}.

        - -

        In addition, the framework now checks whether the next IME includes a -switching mechanism at all (and, thus, whether that IME supports switching to -the IME after it). An -IME with a switching mechanism will not cycle to an IME without one. This -change takes place in -{@link android.view.inputmethod.InputMethodManager#switchToNextInputMethod -InputMethodManager.switchToNextInputMethod}. - -

        To see an example of how to use the updated IME-switching APIs, refer to the -updated soft-keyboard implementation sample in this release.

        - -

        Animation & Graphics

        +

        Graphics

        Support for OpenGL ES 3.1

        The L Developer Preview adds Java interfaces and native support for OpenGL @@ -761,9 +736,8 @@ $ historian.par [-p powerfile] bugreport.txt > out.html

        The L Developer Preview provides new functionality for running apps within an enterprise environment. A device administrator can -initiate a managed provisioning process to add a co-present but separate Android -work profile to a device, if the user has an existing personal account. -Apps that are associated with Android work profiles will appear alongside +initiate a managed provisioning process to add a co-present but separate managed profile to a device, if the user has an existing personal account. +Apps that are associated with managed profiles will appear alongside non-managed apps in the user’s Launcher, Recent apps screen, and notifications.

        To start the managed provisioning process, send {@code @@ -771,15 +745,11 @@ ACTION_PROVISION_MANAGED_PROFILE} in an {@link android.content.Intent}. If the call is successful, the system triggers the {@code android.app.admin.DeviceAdminReceiver. onProfileProvisioningComplete()} callback. You can then call {@code app.admin.DevicePolicyManager. setProfileEnabled()} to -enable this Android work profile.

        - -

        A device administrator can associate a user with more than one Android -work profile. To get a list of the Android work profiles associated with the -user, call {@code android.os.UserManager. getUserProfiles()}.

        +enable this managed profile.

        If you are developing a Launcher app, you can use the new {@code android.content.pm.LauncherApps} class to get a list of launchable activities -for the current user and any associated Android work profiles. Your Launcher can make +for the current user and any associated managed profiles. Your Launcher can make the managed apps visually prominent by appending a “work” badge to the icon drawable with {@code android.os.UserManager. getBadgeDrawableForUser()}.

        @@ -801,7 +771,7 @@ specially-configured device owner app, through the {@code android.app.a

        To set up a device owner, follow these steps:

          -
        1. Attach a device running an Android {@code userdebug} build to your development machine.
          2. +
        2. Attach a device running an Android {@code userdebug} build to your development machine.
        3. Install your device owner app.
        4. Create a {@code device_owner.xml} file and save it to the {@code /data/system} directory on the device. @@ -849,7 +819,7 @@ Your app can obtain a page for rendering with {@code openPage()}, then call {@code render()} to turn the opened {@code PdfRenderer.Page} into a bitmap. You can also set additional parameters if you only want to convert a portion of the document into a bitmap image (for example, to implement -tiled rendering in +tiled rendering in order to zoom in on the document).

          Testing & Accessibility

          @@ -884,6 +854,29 @@ The new {@code AccessibilityAction} class replaces the actions-related APIs previously found in {@code AccessibilityNodeInfo}.
      +

      IME

      + +

      Easier switching between input languages

      + +

      Beginning in the L Developer Preview, users can more easily switch between +all input +method editors (IME) supported by the platform. Performing the designated +switching action (usually touching a Globe icon on the soft keyboard) will cycle +among all such IMEs. This change takes place in +{@link android.view.inputmethod.InputMethodManager#shouldOfferSwitchingToNextInputMethod +InputMethodManager.shouldOfferSwitchingToNextInputMethod()}.

      + +

      In addition, the framework now checks whether the next IME includes a +switching mechanism at all (and, thus, whether that IME supports switching to +the IME after it). An +IME with a switching mechanism will not cycle to an IME without one. This +change takes place in +{@link android.view.inputmethod.InputMethodManager#switchToNextInputMethod +InputMethodManager.switchToNextInputMethod}. + +

      To see an example of how to use the updated IME-switching APIs, refer to the +updated soft-keyboard implementation sample in this release.

      +

      Manifest Declarations

      Declarable required features