From 1432cd874af2250f021d2e21d0ae048be08cbdc7 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Fri, 1 May 2009 10:02:17 -0700 Subject: AI 148183: Add missing android namespace to minSdkVersion BUG=1819430 Automated import of CL 148183 --- docs/html/sdk/RELEASENOTES.jd | 8 ++++---- docs/html/sdk/android-1.1.jd | 10 +++++----- docs/html/sdk/android-1.5.jd | 14 +++++++------- 3 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd index ed82b6bc6064..db932158cd0d 100644 --- a/docs/html/sdk/RELEASENOTES.jd +++ b/docs/html/sdk/RELEASENOTES.jd @@ -207,7 +207,7 @@ looks like this: 

<manifest>
   ...
-  <uses-sdk minSdkVersion="2" />
+  <uses-sdk android:minSdkVersion="2" />
   ...
 </manifest>
@@ -219,11 +219,11 @@ function properly on their devices, especially if it uses APIs introduced in Android 1.1.

If your application uses APIs introduced in Android 1.1 but does not declare -<uses-sdk minSdkVersion="2" />, then it will run properly on +<uses-sdk android:minSdkVersion="2" />, then it will run properly on Android 1.1 devices but not on Android 1.0 devices.

If your application does not use any new APIs introduced in Android 1.1, you -can indicate Android 1.0 compatibility by removing minSdkVersion or +can indicate Android 1.0 compatibility by removing android:minSdkVersion or setting the attribute to "1". However, before publishing your application, you must make sure to compile your application against the Android 1.0 system image (available in the Android 1.0 SDK), to ensure that it builds and functions @@ -271,7 +271,7 @@ for authentication to the server.

Developers should note that the registration service for MapView is now active and Google Maps is actively enforcing the Maps API Key requirement. For information about how to register for a Maps API Key, see - + Obtaining a Maps API Key.

USB Drivers for Windows

diff --git a/docs/html/sdk/android-1.1.jd b/docs/html/sdk/android-1.1.jd index ce75e60fdee6..8123fa8dad0e 100644 --- a/docs/html/sdk/android-1.1.jd +++ b/docs/html/sdk/android-1.1.jd @@ -35,17 +35,17 @@ system to correctly determine whether an application is compatible with the system, prior to installing the application.

Applications indicate the lowest system API Level that they are compatible with by adding -a value to the minSdkVersion attribute. +a value to the android:minSdkVersion attribute. The value of the attribute is an integer corresponding to an API Level identifier. Prior to installing an application, the system checks the value of -minSdkVersion and allows the install only +android:minSdkVersion and allows the install only if the referenced integer is less than or equal to the API Level integer stored in the system itself.

If you use the Android 1.1 system image to build an application compatible with Android-powered devices running the Android 1.1 platform, you must set the -minSdkVersion attribute to "2" in order to specify that your application +android:minSdkVersion attribute to "2" in order to specify that your application is compatible only with devices using the Android 1.1 (or greater) system image.

@@ -68,14 +68,14 @@ your application will function properly on their devices, especially if it uses APIs introduced in Android 1.1.

If your application uses APIs introduced in Android 1.1 but does not -declare <uses-sdk minSdkVersion="2" />, then it will +declare <uses-sdk android:minSdkVersion="2" />, then it will run properly on Android 1.1 devices but not on Android 1.0 devices. In the latter case, the application will crash at runtime when it tries to use the Android 1.1 APIs.

If your application does not use any new APIs introduced in Android 1.1, you can indicate Android 1.0 compatibility by removing -minSdkVersion or setting the attribute to "1". However, +android:minSdkVersion or setting the attribute to "1". However, before publishing your application, you must make sure to compile your application against the Android 1.0 system image (available in the Android 1.0 SDK), to ensure that it builds and functions properly for diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd index df52b6268b26..addd64465fb6 100644 --- a/docs/html/sdk/android-1.5.jd +++ b/docs/html/sdk/android-1.5.jd @@ -38,10 +38,10 @@ the system, prior to installing the application.

Applications can reference a specific API Level value in their manifest files, to indicate the minimum version of the Android system required to run the application. To reference a minimum API Level, applications -can add a minSdkVersion attribute in their manifest files. +can add an android:minSdkVersion attribute in their manifest files. The value of the attribute is an integer corresponding to an API Level identifier. Prior to installing an application, the system then checks the value of -minSdkVersion and allows the install only +android:minSdkVersion and allows the install only if the referenced integer is less than or equal to the API Level integer stored in the system itself.

@@ -51,10 +51,10 @@ general, you should compile your application against the lowest possible version of the platform that your application can support. After you determine the lowest version, you should ensure that your application's manifest file defines the API Level of the lowest compatible platform version in the -minSdkVersion attribute. +android:minSdkVersion attribute.

After compiling your application, you should make sure to test it on the -platform specified in the application's minSdkVersion attribute. To +platform specified in the application's android:minSdkVersion attribute. To ensure forward-compatibility, you should also run the application on platforms using a higher API Level than that used by your application. To run your application against different platform versions in the emulator, you create an @@ -76,7 +76,7 @@ attribute looks like this: 

<manifest>
   ...
-  <uses-sdk minSdkVersion="3" />
+  <uses-sdk android:minSdkVersion="3" />
   ...
 </manifest>
@@ -88,7 +88,7 @@ important if your application uses APIs or system features introduced in Android 1.5.

If your application uses APIs introduced in Android 1.5 but does not -declare <uses-sdk minSdkVersion="3" />, then it will +declare <uses-sdk android:minSdkVersion="3" />, then it will run properly on Android 1.5 devices but not on Android 1.0 devices. In the latter case, the application will crash at runtime when it tries to use the Android 1.5 APIs.

@@ -108,7 +108,7 @@ new APIs introduced since Android 1.0, you can remove the attribute or set it to "1". However, before publishing your application, you must make sure to compile your application against the Android library that corresponds to the application's -minSdkVeresion value.

+android:minSdkVeresion value.

Built-in Applications

-- cgit v1.2.3-59-g8ed1b