From 4c8a16a43905e92dd24ee0d9860d20d270d77977 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Thu, 10 Sep 2009 10:45:41 -0700 Subject: [PATCH] Minor changes to api levels doc and upgrading doc. Change Linux "tested on" to Hardy Heron. Change-Id: I24a0c3cb5c15e3725fecb5c64d8aa6de17c76cbd --- docs/html/guide/appendix/api-levels.jd | 56 +++++++++++--------------- docs/html/sdk/1.6_r1/requirements.jd | 2 +- docs/html/sdk/1.6_r1/upgrading.jd | 4 +- 3 files changed, 27 insertions(+), 35 deletions(-) diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index a4dcc5e0c76c7..acf68997d70d7 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -100,8 +100,7 @@ that it supports
  • It lets applications describe the framework API revision that they require
  • It lets the system negotiate the installation of applications on the user's -device, such that version-incompatible applications are not installed on a -user's device
    • +device, such that version-incompatible applications are not installed.

    Each Android platform version stores its API Level identifier internally, in @@ -137,7 +136,7 @@ must be less than or equal to the system's API Level integer. If not declared, the system assumes that the application requires API Level 1.

  • If a android:maxSdkVersion attribute is declared, its value must be equal to or greater than the system's API Level integer. -in the system itself. If not declared, the system assumes that the application +If not declared, the system assumes that the application has no maximum API Level.
    • @@ -154,7 +153,7 @@ element might look like this:

    android:minSdkVersion is to tell the Android system that it is using APIs that were introduced in the API Level specified. If the application were to be somehow installed on a platform with a lower API Level, -then it would crash at run-time when it tries to access APIs that don't exist. +then it would crash at run-time when it tried to access APIs that don't exist. The system prevents such an outcome by not allowing the application to be installed if the lowest API Level it requires is higher than that of the platform version on the target device.

    @@ -194,7 +193,7 @@ receive over-the-air (OTA) system updates. The user may install your application and use it successfully, then later receive an OTA update to a new version of the Android platform. Once the update is installed, your application will run in a new run-time version of the environment, but one that has the API -and system capabilities that it depends on.

    +and system capabilities that your application depends on.

    In some cases, changes below the API, such those in the underlying system itself, may affect your application when it is run in the new @@ -222,8 +221,8 @@ unable to run on those platforms.

    Although it's unlikely that an Android-powered device would be downgraded to a previous version of the platform, it's important to realize that there are likely to be many devices in the field that run earlier versions of the -platform. Even among devices that receive OTA updates, some might lag and not -receive an update for a significant amount of time.

    +platform. Even among devices that receive OTA updates, some might lag and +might not receive an update for a significant amount of time.

    Selecting a platform version and API Level

    @@ -285,39 +284,32 @@ you are using a physical device for testing, ensure that you know the API Level of the Android platform it runs. See the table at the top of this document for a list of platform versions and their API Levels.

    -

    Filtering the Reference Documentation by API Level

    Reference documentation pages on the Android Developers site offer a "Filter -by API Level" control in the top-right area of each page.

    +by API Level" control in the top-right area of each page. You can use the +control to show documentation only for parts of the API that are actually +accessible to your application, based on the API Level that it specifies in +the android:minSdkVersion attribute of its manifest file.

    -

    The "Filter by API Level" lets you show documentation only for parts of the -API that are actually accessible to your application, based on the API Level -that it specifies in the minSdkVersion attribute in its manifest -file

    +

    To use filtering, set the control to the same API Level as that specified +by your application. Notice that APIs introduced in a later API Level are +then grayed out and their content is masked, since they would not be +accessible to your application.

    -

    When you filter the reference documentation by an API level, only the APIs -available at that API level are shown. APIs introduced in a later API level are -grayed out and their content is masked, since they would not be accessible to -your application.

    - -

    Note that filtering by API Level in the documentation does not provide a view -of what is new or introduced in each API Level. Filtering simply provides a way +

    Filtering by API Level in the documentation does not provide a view +of what is new or introduced in each API Level — it simply provides a way to view the entire API associated with a given API Level, while excluding API elements introduced in later API Levels.

    By default, API Level filtering is enabled and set to show the latest API -Level. If you do not want to use filtering reference documentation, select the -highest available API Level.

    +Level. If you do not want to use filtering reference documentation, +simply select the highest available API Level.

    -

    Note that the reference documentation for API elements also specifies the API -Level at which the element was introduced. The API Level for packages and -classes is specified as "Since <api level>" at the top-right corner of the -content area on each documentation page. The API Level for each class member is -specified in the member's detailed description section header, at the right -margin.

    +

    Also note that the reference documentation for individual API elements +specifies the API Level at which the elements were introduced. The API Level +for packages and classes is specified as "Since <api level>" at the +top-right corner of the content area on each documentation page. The API Level +for class members is specified in their detailed description headers, +at the right margin.

    diff --git a/docs/html/sdk/1.6_r1/requirements.jd b/docs/html/sdk/1.6_r1/requirements.jd index 781ee3278dedc..8e698fa5b4b2b 100644 --- a/docs/html/sdk/1.6_r1/requirements.jd +++ b/docs/html/sdk/1.6_r1/requirements.jd @@ -11,7 +11,7 @@ Android applications using the Android SDK tools included in Android

    Supported Development Environments

    diff --git a/docs/html/sdk/1.6_r1/upgrading.jd b/docs/html/sdk/1.6_r1/upgrading.jd index 2f9cc7308f84e..ebe6a95c8ee94 100644 --- a/docs/html/sdk/1.6_r1/upgrading.jd +++ b/docs/html/sdk/1.6_r1/upgrading.jd @@ -219,7 +219,7 @@ hardware capabilities. If you find dependencies, you can design around them by building in alternate support or graceful degradation, or you can specify them as hardware requirements in a <uses-configuration>. -element in the application's manifest file. Also see the <uses-feature> +element in the application's manifest file. Also see the <uses-feature> manifest element, which lets your application declare a requirement for specific features, such as an OpenGL ES version or a camera that has autofocus capability. @@ -258,7 +258,7 @@ AVDs that emulate different screen resolutions and densities. Also note that, starting with Android 1.6, the platform provides a Compatibility Mode that automatically scales the UI of applications if they do not explicitly indicate support for the current screen in the -<supports-screen> +<supports-screen> element in their manifest files. As part of testing, you should evaluate how your application is displayed in Compatibility Mode on different screens.