From 44fc1e454d9e23c83deec971310a8f2eb41cd5cd Mon Sep 17 00:00:00 2001 From: Joe Fernandez Date: Thu, 25 Feb 2016 22:10:11 -0800 Subject: [PATCH] docs: InfoPros Project 02 - New API 15 baseline - batch 01 file set Change-Id: Ied76061cb968af55efcd638341394ae710c2e7fb --- docs/html/design/handhelds/index.jd | 4 ++-- docs/html/design/patterns/navigation.jd | 9 ++++---- docs/html/design/patterns/new.jd | 5 +---- docs/html/design/patterns/widgets.jd | 12 +++++++++- docs/html/google/play/licensing/overview.jd | 6 ++--- docs/html/google/play/licensing/setting-up.jd | 22 +++---------------- docs/html/ndk/guides/mips.jd | 2 +- docs/html/ndk/guides/ndk-gdb.jd | 11 ++-------- docs/html/training/accessibility/service.jd | 5 ++--- docs/html/training/appbar/index.jd | 6 ----- 10 files changed, 28 insertions(+), 54 deletions(-) mode change 100644 => 100755 docs/html/design/handhelds/index.jd mode change 100644 => 100755 docs/html/design/patterns/navigation.jd mode change 100644 => 100755 docs/html/design/patterns/new.jd mode change 100644 => 100755 docs/html/design/patterns/widgets.jd mode change 100644 => 100755 docs/html/google/play/licensing/overview.jd mode change 100644 => 100755 docs/html/ndk/guides/mips.jd mode change 100644 => 100755 docs/html/training/accessibility/service.jd mode change 100644 => 100755 docs/html/training/appbar/index.jd diff --git a/docs/html/design/handhelds/index.jd b/docs/html/design/handhelds/index.jd old mode 100644 new mode 100755 index 81c2c19476686..4a4526cb21b86 --- a/docs/html/design/handhelds/index.jd +++ b/docs/html/design/handhelds/index.jd @@ -79,9 +79,9 @@ to allow the user to enjoy full screen content without distraction.

  • Navigation Bar

    -

    New for phones in Android 4.0, the navigation bar is present only on devices that don't have +

    The navigation bar is present only on devices that don't have the traditional hardware keys. It houses the device navigation controls Back, Home, and - Recents, and also displays a menu for apps written for Android 2.3 or earlier.

    + Recents.

    • diff --git a/docs/html/design/patterns/navigation.jd b/docs/html/design/patterns/navigation.jd old mode 100644 new mode 100755 index 703528e9ca007..abb3a7308b062 --- a/docs/html/design/patterns/navigation.jd +++ b/docs/html/design/patterns/navigation.jd @@ -11,11 +11,10 @@ page.image=/design/media/navigation_between_siblings_gmail.png

    Consistent navigation is an essential component of the overall user experience. Few things frustrate -users more than basic navigation that behaves in inconsistent and unexpected ways. Android 3.0 -introduced significant changes to the global navigation behavior. Thoughtfully following the -guidelines for Back and Up will make your app's navigation predictable and reliable for your users.

    -

    Android 2.3 and earlier relied upon the system Back button for supporting navigation within an -app. With the introduction of action bars in Android 3.0, a second navigation mechanism appeared: +users more than basic navigation that behaves in inconsistent and unexpected ways. Thoughtfully +following the guidelines for Back and Up will make your app's navigation predictable and reliable +for your users.

    +

    Action bars provide a second, standard navigation mechanism: the Up button, consisting of the app icon and a left-point caret.

    diff --git a/docs/html/design/patterns/new.jd b/docs/html/design/patterns/new.jd old mode 100644 new mode 100755 index 47b05b2912abc..df4c2ede187e5 --- a/docs/html/design/patterns/new.jd +++ b/docs/html/design/patterns/new.jd @@ -196,10 +196,7 @@ lockscreen, priority notifications, and cloud-synced notifications.

    Android 4.0 removes the need for traditional hardware keys on phones by replacing them with a virtual navigation bar that houses - the Back, Home and Recents buttons. Read the - Compatibility - pattern to learn how the OS adapts to phones with hardware buttons and - how pre-Android 3.0 apps that rely on menu keys are supported.

    + the Back, Home and Recents buttons.

    diff --git a/docs/html/design/patterns/widgets.jd b/docs/html/design/patterns/widgets.jd old mode 100644 new mode 100755 index 8d94a52e1ff3a..42f563a04c942 --- a/docs/html/design/patterns/widgets.jd +++ b/docs/html/design/patterns/widgets.jd @@ -3,6 +3,13 @@ page.tags="appwidget","home" page.metaDescription=Design guide to creating widgets that are easy to use and look great. @jd:body + +
    +

    Developer Docs

    +

    App Widgets

    +
    +     +

    Widgets are an essential aspect of home screen customization. You can imagine them as "at-a-glance" views of an app's most important data and functionality that is accessible right from the user's home screen. Users can move widgets across their home screen panels, and, if supported, resize them to tailor the amount of information within a widget to their preference.

    Widget types

    @@ -80,7 +87,10 @@ A music player widget is primarily a control widget, but also keeps the user inf

    Widget resizing

    -

    With version 3.1, Android introduced resizable widgets to the platform. Resizing allows users to adjust the height and/or the width of a widget within the constraints of the home panel placement grid. You can decide if your widget is freely resizable or if it is constrained to horizontal or vertical size changes. You do not have to support resizing if your particular widget is inherently fixed-size.

    +

    Resizing allows users to adjust the height and/or the width of a widget within the +constraints of the home panel placement grid. You can decide if your widget is freely resizable or +if it is constrained to horizontal or vertical size changes. You do not have to support resizing if +your particular widget is inherently fixed-size.

    Allowing users to resize widgets has important benefits:

    • They can fine-tune how much information they want to see on each widget.
      • diff --git a/docs/html/google/play/licensing/overview.jd b/docs/html/google/play/licensing/overview.jd old mode 100644 new mode 100755 index a2d5379e770f5..ecb384dc74ed3 --- a/docs/html/google/play/licensing/overview.jd +++ b/docs/html/google/play/licensing/overview.jd @@ -197,8 +197,7 @@ application:

      • An application can use the service only if the Google Play client is -installed on its host device and the device is running Android 1.5 (API level 3) -or higher.
        • +installed on its host device and the device is running Android 1.5 (API level 3) or higher.
      • To complete a license check, the licensing server must be accessible over the network. You can implement license caching behaviors to manage access to your application when there is no network connectivity.
        • @@ -233,8 +232,7 @@ managed on any device on any storage, including SD card.

        Although no license mechanism can completely prevent all unauthorized use, the licensing service lets you control access for most types of normal usage, -across all compatible devices, locked or unlocked, that run Android 1.5 or -higher version of the platform.

        +across all compatible devices, locked or unlocked.

        To begin adding application licensing to your application, continue to Setting Up for Licensing.

        diff --git a/docs/html/google/play/licensing/setting-up.jd b/docs/html/google/play/licensing/setting-up.jd index ef9de43eff920..f7521822d9b38 100755 --- a/docs/html/google/play/licensing/setting-up.jd +++ b/docs/html/google/play/licensing/setting-up.jd @@ -161,7 +161,7 @@ the add-on, you need to create an AVD configuration that uses that system image. However, it does provide:

          -
        • An Google Play background service that implements the +
        • A Google Play background service that implements the ILicensingService remote interface, so that your application can send license checks over the network to the licensing server.
        • A set of underlying account services that let you add an a Google account on @@ -213,24 +213,8 @@ Run/Debug Configuration that targets the appropriate device or AVD.

          You do not need to make any changes to your application's build configuration, provided that the project is already configured to compile -against a standard Android 1.5 (API level 3) or higher library. For example: - -

            -
          • If you have an existing application that is compiled against -the Android 1.5 library, you do not need to make any changes to your -build configuration to support licensing. The build target meets the minimum -requirements for licensing, so you would continue building -against the same version of the Android platform.
            • - -
          • Similarly, if you are building against Android 1.5 (API level 3) but -are using an emulator running the Google APIs Add-On API 8 as the application's -runtime environment, there is no need to change your application's build -configuration.
            • -
          - -

          In general, adding licensing to an application should have no impact -whatsoever on the application's build configuration.

          - +against a standard Android 1.5 (API level 3) or higher library. Adding licensing to an application +should have no impact whatsoever on the application's build configuration.

          Downloading the LVL

          diff --git a/docs/html/ndk/guides/mips.jd b/docs/html/ndk/guides/mips.jd old mode 100644 new mode 100755 index 2b4eea47bd5ef..d104ffec7ee68 --- a/docs/html/ndk/guides/mips.jd +++ b/docs/html/ndk/guides/mips.jd @@ -40,4 +40,4 @@ libraries that run on the CPU powering his or her device.

          Compatibility

          MIPS support requires, at minimum, Android 2.3 (Android API level 9). If your project files target an older API level, but include MIPS as a targeted platform, the NDK build script -automatically selects the right set of native platform headers/libraries for you.

          \ No newline at end of file +automatically selects the right set of native platform headers/libraries for you.

          diff --git a/docs/html/ndk/guides/ndk-gdb.jd b/docs/html/ndk/guides/ndk-gdb.jd index 6d9f9332a880b..8ce60372985d8 100755 --- a/docs/html/ndk/guides/ndk-gdb.jd +++ b/docs/html/ndk/guides/ndk-gdb.jd @@ -27,7 +27,8 @@ does not support using the legacy {@code make APP=<name>} method to build. {@code <application>} element that sets the {@code android:debuggable} attribute to {@code true}.
        • Build your app to run on Android 2.2 (Android API level 8) or higher.
          • -
        • Debug on a device or emulator running Android 2.2 or higher. For debugging purposes, the target +
        • Debug on a device or emulator running Android 2.2 or higher. + For debugging purposes, the target API level that you declare in your {@code AndroidManifest.xml} file does not matter.
        • Develop your app in a Unix shell. On Windows, use Cygwin or the experimental {@code ndk-gdb-py} Python @@ -221,14 +222,6 @@ Python version of {@code ndk-gdb}.

          cannot debug native threads properly. The debugger can only debug the main thread, abd completely ignores the execution of other threads.

          -

          Using a version of Android prior to 2.3 causes {@code ndk-gdb} to display the following message -prior to showing the GDB prompt:

          - -
          -Thread debugging is unsupported on this Android platform!
-
          - -

          If you place a breakpoint on a function executed on a non-main thread, the program exits, and GDB displays the following message:

          diff --git a/docs/html/training/accessibility/service.jd b/docs/html/training/accessibility/service.jd old mode 100644 new mode 100755 index 953c558921bf0..5b99c46be67e8 --- a/docs/html/training/accessibility/service.jd +++ b/docs/html/training/accessibility/service.jd @@ -132,7 +132,7 @@ public void onServiceConnected() { } -

          Starting with Android 4.0, there is a second option available: configure the +

          The second option is to configure the service using an XML file. Certain configuration options like {@link android.R.attr#canRetrieveWindowContent} are only available if you configure your service using XML. The same configuration options above, defined @@ -201,8 +201,7 @@ public void onAccessibilityEvent(AccessibilityEvent event) {

          Query the View Heirarchy for More Context

          -

          This step is optional, but highly useful. One of the new features in Android -4.0 (API Level 14) is the ability for an +

          This step is optional, but highly useful. The Android platform provides the ability for an {@link android.accessibilityservice.AccessibilityService} to query the view hierarchy, collecting information about the UI component that generated an event, and its parent and children. In order to do this, make sure that you set the diff --git a/docs/html/training/appbar/index.jd b/docs/html/training/appbar/index.jd old mode 100644 new mode 100755 index c62ffaf86205e..64ce94d0cf074 --- a/docs/html/training/appbar/index.jd +++ b/docs/html/training/appbar/index.jd @@ -9,12 +9,6 @@ startpage=true

          -

          Dependencies and prerequisites

          -
            -
          • Android 2.1 (API level 7) or higher
            • -
          - -

          You should also read