From eeb0b2514a8b4f175a9ef16a319437a61aedb8f3 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Thu, 22 Oct 2009 16:08:32 -0700 Subject: doc change: incorporate comments on SDK docs and structure. Bug: 2160782 --- docs/html/guide/appendix/api-levels.jd | 3 +- docs/html/guide/practices/screens_support.jd | 66 ++++++++++++++----------- docs/html/guide/tutorials/localization/index.jd | 5 +- docs/html/sdk/adding-components.jd | 13 ++--- docs/html/sdk/adt-notes.jd | 4 +- docs/html/sdk/android-1.5.jd | 11 +++-- docs/html/sdk/android-1.6.jd | 15 +++--- docs/html/sdk/android-2.0.jd | 26 +++------- docs/html/sdk/eclipse-adt.jd | 14 ------ docs/html/sdk/index.jd | 26 ++++------ docs/html/sdk/installing.jd | 64 ++++++++++++------------ 11 files changed, 113 insertions(+), 134 deletions(-) (limited to 'docs') diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index 3f3b6c6..b3b6371 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -119,7 +119,8 @@ on which the application is able to run. The default value is "1".
  • android:targetSdkVersion — Specifies the API Level on which the application is designed to run. In some cases, this allows the application to use manifest elements or behaviors defined in the target -API Level, rather than those in the minimum API Level.
    • +API Level, rather than being restricted to using only those defined +for the minimum API Level.
  • android:maxSdkVersion — Specifies the maximum API Level on which the application is able to run.
    • diff --git a/docs/html/guide/practices/screens_support.jd b/docs/html/guide/practices/screens_support.jd index 09347a6..1d16d88 100644 --- a/docs/html/guide/practices/screens_support.jd +++ b/docs/html/guide/practices/screens_support.jd @@ -61,9 +61,7 @@ earlier, you should read this document and consider how you may need to adapt your application for proper display on new devices that offer different screens and that are running Android 1.6 or later. In most cases, only minor adjustments are needed, however you should make sure to test your -application on all of the new screens supported in Android 1.6. - -

    +application on all supported screens.

    In particular, if you have an existing application that you would like to make available for users of devices with small screens (such as QVGA), please @@ -73,7 +71,11 @@ information about how to do that.

    Overview of Screens Support

    -

    The sections below provide an overview of the Android platform's support for multiple screens, including an introduction to terms and concepts used in this document and in the API, a summary of the screen configurations that the platform supports, and an overview of the API and underlying screen-compatibility features.

    +

    The sections below provide an overview of the Android platform's support for +multiple screens, including an introduction to terms and concepts used in this +document and in the API, a summary of the screen configurations that the +platform supports, and an overview of the API and underlying +screen-compatibility features.

    Terms and Concepts

    @@ -462,7 +464,7 @@ pixels for more information.

    Manifest attributes for screens support

    -

    Android 1.6 introduces a new manifest element, +

    Android 1.6 introduced a new manifest element, <supports-screens>, whose attributes you can use to control the display of your application on different classes of device screens, as listed @@ -631,8 +633,8 @@ appropriate attributes to false.

    Resource directory qualifiers for screen size and density

    -

    Android 1.6 supports new resource directory qualifiers for selecting -resources based on the characteristics of the screen on which your application +

    Android supports resource directory qualifiers for controlling the selection +of resources based on the characteristics of the screen on which your application is running. You can use these qualifiers to provide size- and density-specific resources in your application. For more information about the generalized sizes and densities that correspond to the qualifiers, see Table @@ -693,14 +695,14 @@ to the baseline screen configuration. Platform version -v4 -Resources that are for use only on Android 1.6 (API Level 4) or higher -platform versions. If your application is designed to run on both Android 1.5 -(or lower) and Android 1.6 (and higher), you can use this qualifier to tag -resources that should be excluded when your application is running on Android -1.5 or earlier. Using this qualifier is necessary in some cases, if the older -platform is inadvertently loading resources from an Android 1.6 resources -directory. +v<api-level> +Resources that are for use only on a specific API Level or higher. For +example, if your application is designed to run on both Android 1.5 (API Level +3) and Android 1.6 (API Level 4 and higher), you can use the -v4 +qualifier to tag any resources that should be excluded when your application is +running on Android 1.5 (API Level 3). Using the version qualifier is necessary +in some cases, if the older platform is inadvertently loading resources from a +directory containing resources for a newer platform. @@ -975,8 +977,8 @@ Here's how to do that:

    android:minSdkVersion attribute as it is. You do not need to increment the value of the attribute to support new devices and multiple screens. -
  • Extend compatibility for Android 1.6 devices by adding a new attribute -— android:targetSdkVersion — to the +
  • Extend compatibility for Android 1.6 (and higher) devices by adding +a new attribute — android:targetSdkVersion — to the uses-sdk element. Set the value of the attribute to "4". This allows your application to "inherit" the platform's multiple screens support, even though it is technically using an earlier version @@ -988,11 +990,12 @@ later, this is where you will add them.
    • the Android 1.6 (API Level 4) library, rather than against the Android 1.5 (or earlier) library. You will not be able to compile your application against the older platform because of the new manifest attribute. -
  • Set up AVDs for testing your application on Android 1.6. Create AVDs that -use the screen sizes and densities that you want to support. When you create the -AVDs, make sure to select the Android 1.6 platform as the system image to run. -For more information, see How to Test Your Application on -Multiple Screens, below.
    • +
  • Set up AVDs for testing your application on Android 1.6 and higher +releases. Create AVDs that use the screen sizes and densities that you want to +support. When you create the AVDs, make sure to select the Android 1.6 or higher +platform as the system image to run. For more information, see How to Test Your Application on Multiple Screens, +below.
  • Set up AVDs for testing your application on Android 1.5 (or earlier platform). You need AVDs running the older platforms you are targeting, so that you can test for compatibility and ensure that there are no functional @@ -1018,10 +1021,11 @@ qualifiers. Qualifiers must be arranged in a proscribed order. See Alternate Resources for more information.
  • Note that if you add size- or density-specific resource directories -tagged with any of the Android 1.6 qualifiers listed in this document, you -should make sure to also tag those directories with the v4 -qualifier. This ensures that those resources will be ignored when the -application is run on Android 1.5 or lower platform versions.

    • +tagged with any of the resource qualifiers listed in this document, you should +make sure to also tag those directories with the v<api-level> +qualifier (for example, -v4). This ensures that those resources +will be ignored when the application is run on Android 1.5 or lower platform +versions.

  • If your application does not offer support (such as custom layouts) for @@ -1074,14 +1078,20 @@ the defaults. For general information about working with AVDs, see Android Virtual Devices.

    -

    The Android 1.6 SDK includes these emulator skins, which represent the -primary screen configurations that your should test:

    +

    The Android 1.6 and higher platforms in the SDK include these emulator skins, +which represent the primary screen configurations that your should test: