diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/html/guide/appendix/api-levels.jd | 62 | ||||
| -rw-r--r-- | docs/html/guide/topics/manifest/uses-sdk-element.jd | 33 | ||||
| -rw-r--r-- | docs/html/intl/ja/index.jd | 8 | ||||
| -rw-r--r-- | docs/html/sdk/1.6_r1/requirements.jd | 2 | ||||
| -rw-r--r-- | docs/html/sdk/1.6_r1/upgrading.jd | 4 | ||||
| -rw-r--r-- | docs/html/sdk/android-1.6.jd | 205 |
6 files changed, 196 insertions, 118 deletions
diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index a4dcc5e..acf6899 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -100,8 +100,7 @@ that it supports</li> <li>It lets applications describe the framework API revision that they require</li> <li>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</li> +device, such that version-incompatible applications are not installed.</li> </ul> <p>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. </li> <li>If a <code>android:maxSdkVersion</code> 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. </li> </ul> @@ -154,7 +153,7 @@ element might look like this: </p> <code>android:minSdkVersion</code> is to tell the Android system that it is using APIs that were <em>introduced</em> 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.</p> @@ -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. </p> +and system capabilities that your application depends on. </p> <p>In some cases, changes <em>below</em> 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.</p> <p>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. </p> +platform. Even among devices that receive OTA updates, some might lag and +might not receive an update for a significant amount of time. </p> <h3 id="platform">Selecting a platform version and API Level</h3> @@ -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. </p> -<!-- -The Framework API makeup: the API available in a specific platform version is -made up of API parts introduced in previous versions, plus some parts that are -new. ---> <h2 id="filtering">Filtering the Reference Documentation by API Level</h2> <p>Reference documentation pages on the Android Developers site offer a "Filter -by API Level" control in the top-right area of each page. </p> - -<p>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 <code>minSdkVersion</code> attribute in its manifest -file </p> - -<p>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. </p> - -<p>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 +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 <code>android:minSdkVersion</code> attribute of its manifest file. </p> + +<p>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. </p> + +<p>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.</p> <p>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.</p> - -<p>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. </p> +Level. If you do not want to use filtering reference documentation, +simply select the highest available API Level. </p> + +<p>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. </p> diff --git a/docs/html/guide/topics/manifest/uses-sdk-element.jd b/docs/html/guide/topics/manifest/uses-sdk-element.jd index ee8d03d..aa1e8ae 100644 --- a/docs/html/guide/topics/manifest/uses-sdk-element.jd +++ b/docs/html/guide/topics/manifest/uses-sdk-element.jd @@ -36,30 +36,27 @@ and minor versions).</p> <dd> <dl class="attr"> <dt><a name="min"></a>{@code android:minSdkVersion}</dt> - <dd>An integer designating the minimum level of the Android API that's required - for the application to run. + <dd>An integer designating the minimum API Level required + for the application to run. The Android system will prevent the user from installing + the application if the system's API Level is lower than the value specified in + this attribute. You should always declare this attribute. - <p>Prior to installing an application, the Android system checks the value of this - attribute and allows the installation only if it - is less than or equal to the API Level used by the system itself.</p> - - <p>If you do not declare this attribute, then a value of "1" is assumed, which + <p class="caution"><strong>Caution:</strong> + If you do not declare this attribute, then a value of "1" is assumed, which indicates that your application is compatible with all versions of Android. If your - application is <em>not</em> universally compatible (for instance if it uses APIs - introduced in Android 1.5) and you have not declared the proper <code>minSdkVersion</code>, - then when installed on a system with a lower API Level, the application - will crash during runtime. For this reason, be certain to declare the appropriate API Level + application is <em>not</em> compatible with all versions (for instance, it uses APIs + introduced in API Level 3) and you have not declared the proper <code>minSdkVersion</code>, + then when installed on a system with an API Level less than 3, the application will crash + during runtime when attempting to access the unavailable APIs. For this reason, + be certain to declare the appropriate API Level in the <code>minSdkVersion</code> attribute.</p> </dd> <dt><a name="max"></a>{@code android:maxSdkVersion}</dt> - <dd>An integer designating the maximum level of the Android API that the application is - compatible with. You can use this to ensure your application is filtered out - of later versions of the platform when you know you have incompatibility with them.</p> - - <p>Prior to installing an application, the Android system checks the value of this - attribute and allows the installation only it - is greater than or equal to the API Level used by the system itself.</p> + <dd>An integer designating the maximum API Level on which the application is + designed to run. The Android system will prevent the user from installing the + application if the system's API Level is higher than the value specified + in this attribute. <p>Introduced in: API Level 4</p> </dd> diff --git a/docs/html/intl/ja/index.jd b/docs/html/intl/ja/index.jd index 71811de..3ed2357 100644 --- a/docs/html/intl/ja/index.jd +++ b/docs/html/intl/ja/index.jd @@ -118,10 +118,10 @@ home=true 'sdk': { 'layout':"imgLeft", 'icon':"sdk-small.png", - 'name':"SDK 1.5 r3", - 'img':"sdk-large.png", - 'title':"Android 1.5 SDK", - 'desc': "<p>Android 1.5 SDK の最新バージョンが公開されました。このリリースには Android 1.5 用の API、最新版デベロッパーツール、複数プラットフォーム(バージョン)サポート、そして Google API のアドオンが含まれています。</p><p><a href='{@docRoot}sdk/1.5_r3/index.html'>Android 1.5 SDK をダウンロード »</a></p>" + 'name':"SDK 1.6 r1", + 'img':"donut-android.png", + 'title':"Android 1.6 SDK", + 'desc': "<p>Android 1.6 SDK の最新バージョンが公開されました。このリリースには Android 1.6 用の API、最新版デベロッパーツール、複数プラットフォーム(バージョン)サポート、そして Google API のアドオンが含まれています。</p><p><a href='{@docRoot}sdk/1.6_r1/index.html'>Android 1.6 SDK をダウンロード »</a></p>" }, 'io': { diff --git a/docs/html/sdk/1.6_r1/requirements.jd b/docs/html/sdk/1.6_r1/requirements.jd index 781ee32..8e698fa 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 <ul> <li>Windows XP (32-bit) or Vista (32- or 64-bit)</li> <li>Mac OS X 10.4.8 or later (x86 only)</li> - <li>Linux (tested on Linux Ubuntu Dapper Drake)</li> + <li>Linux (tested on Linux Ubuntu Hardy Heron)</li> </ul> <h3>Supported Development Environments</h3> diff --git a/docs/html/sdk/1.6_r1/upgrading.jd b/docs/html/sdk/1.6_r1/upgrading.jd index 2f9cc73..ebe6a95 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 <a href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code><uses-configuration></code>.</a> -element in the application's manifest file. Also see the <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code> +element in the application's manifest file. Also see the <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a> 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 -<a href="{@docRoot}guide/topics/manifest/supports-screen-element.html"><code><supports-screen></code> +<a href="{@docRoot}guide/topics/manifest/supports-screen-element.html"><code><supports-screen></code></a> element in their manifest files. As part of testing, you should evaluate how your application is displayed in Compatibility Mode on different screens. </p> </li> diff --git a/docs/html/sdk/android-1.6.jd b/docs/html/sdk/android-1.6.jd index 29dceec..5dd2d95 100644 --- a/docs/html/sdk/android-1.6.jd +++ b/docs/html/sdk/android-1.6.jd @@ -11,7 +11,7 @@ page.title=Android 1.6 Version Notes <ul> <li><a href="#overview">Overview</a> -<li><a href="#features">New Features</a> +<li><a href="#features">Release Highlights</a> <li><a href="#apps">Built-in Applications</a> <li><a href="#locs">Locales</a> <li><a href="#api-changes">API Changes</a> @@ -20,9 +20,9 @@ page.title=Android 1.6 Version Notes <h2 id="overview">Overview</h2> <p>The Android 1.6 system delivered in the SDK (as library and system image) is -the development counterpart to the Android 1.6 production system image, -deployable to Android-powered handsets starting September 2009. The system is fully -compliant and includes no external libraries.</p> +the development counterpart to the Android 1.6 production system image, which is +deployable to Android-powered handsets starting October 2009. The system is +fully compliant and includes no external libraries. </p> <p>The Android 1.6 system delivers an updated version of the framework API. As with previous versions, the Android 1.6 API @@ -32,11 +32,11 @@ system to correctly determine whether an application is compatible with the system, prior to installing the application. </p> <p>For more information about how to use API Level, see the <a -href="{@docRoot}guide/developing/">API Levels</a> document. </p> +href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p> -<h2 id="features">New Features</h2> +<h2 id="features">Highlights</h2> -<p>For a list of new system features, see the <a +<p>For a list of new user features and platform highlights, see the <a href="http://developer.android.com/sdk/android-1.6-highlights.html">Android 1.6 Platform Highlights</a> document.</p> @@ -139,22 +139,45 @@ available in the Android 1.6 system image are listed below (with </tr> </table> -<p>Localized UI strings match the locales that are displayable in -the emulator, accessible through the device Settings application.</p> +<p>Localized UI strings match the locales that are accessible +through Settings.</p> <h2 id="api-changes">API Changes</h2> -<h3 style="padding-top:0">Overview</h3> - -<ul> - -<li>Search framework</li> +<h4 id="UIFramework">UI framework</h4> + <ul> + <li>New classes in {@link android.view.animation} + to control the behavior of animations: + <ul> + <li><code>AnticipateInterpolator</code></li> + <li><code>AnticipateOvershootInterpolator</code></li> + <li><code>BounceInterpolator</code></li> + <li><code>OvershootInterpolator</code></li> + </ul> + </li> + <li>New XML attribute <code>android:onClick</code> to specify a View's +<a href="/reference/android/view/View.OnClickListener.html">View.OnClickListener</a> +from a layout file. + </li> + <li>New support for dealing with varying screen densities. Density +information is associated with Bitmap and Canvas for performing the +correct scaling. The framework will automatically scale bitmaps and +nine-patches based on the density the resource was found under and the +density of the screen, etc. + </li> + </ul> + +<h4>Search framework</h4> <ul> - <li>Applications can now expose relevant content to users as search suggestions in the Quick Search Box, a new device-wide search capability that is accessible from the home screen. To support this, the search framework adds new attributes to the searchable metadata file. For complete information, see the {@link android.app.SearchManager SearchManager} documentation.</li> + <li>Applications can now expose relevant content to users as search +suggestions in the Quick Search Box, a new device-wide search capability that is +accessible from the home screen. To support this, the search framework adds new +attributes to the searchable metadata file. For complete information, see the +{@link android.app.SearchManager SearchManager} documentation. + </li> </ul> -</li> -<li>Accessibility framework</li> +<h4>Accessibility framework</h4> <ul> <li>New {@link android.view.accessibility android.accessibility} package that includes classes for capturing accessibility events and forwarding them to @@ -163,73 +186,139 @@ an {@link android.accessibilityservice AccessibilityService} handler. </li> that lets your application track user events and provide visual, audible, or haptic feedback to the user. </li> </ul> -</li> -<li>Gestures</li> +<h4>Gesture Input</h4> <ul> <li>New {@link android.gesture gesture} API for creating, recognizing, loading, and saving gestures.</li> </ul> -</li> -<li>Text-to-speech</li> +<h4>Text-to-speech</h4> <ul> - <li>New package {@link android.speech.tts android.speech.tts} provides + <li>New {@link android.speech.tts android.speech.tts} package provides classes for synthesizing speech from text, for immediate playback or to create a sound file.</li> </ul> -</li> - -<li>Permissions</li> - <ul> - - <li>New permissions for -{@link android.Manifest.permission#CHANGE_WIFI_MULTICAST_STATE CHANGE_WIFI_MULTICAST_STATE}, -{@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}, -{@link android.Manifest.permission#READ_HISTORY_BOOKMARKS READ_HISTORY_BOOKMARKS}, -{@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE WRITE_EXTERNAL_STORAGE}, and -{@link android.Manifest.permission#WRITE_HISTORY_BOOKMARKS WRITE_HISTORY_BOOKMARKS}.</li> - </ul> -</li> -<li>Graphics</li> +<h4>Graphics</h4> <ul> <li>Classes in {@link android.graphics android.graphics} now support scaling for different screen densities.</li> </ul> -</li> -<li>Telephony</li> +<h4>Telephony</h4> <ul> <li>New {@link android.telephony.SmsManager SmsManager} and other classes for sending and receiving SMS messages.</li> </ul> -</li> -<li>Utilities</li> +<h4>Utilities</h4> <ul> <li>New {@link android.util.DisplayMetrics DisplayMetrics} fields for determining the density of the current device screen.</li> </ul> -</li> - -<li>Application-defined support for various screen densities</li> - <p>Applications can now use a new element in their manifest files, <a -href="{@docRoot}guide/topics/manifest/supports-screen-element.html"><supports- -screen></a> to indicate to the specific screen resolutions/densities that -they are designed to support. When the application is installed on a device -whose screen is not explicitly supported by the application, the system -runs the application in Compatibility Mode, where possible. </p> -</li> -</ul> - -<h3 id="api-diff">API Change Details</h3> - -<p>For a detailed view of API changes in this platform (API Level 4), see the <a -href="{@docRoot}sdk/api_diff/4/changes.html">API Differences Report</a>.</p> - - +<h4 id="AndroidManifest">Android Manifest elements</h4> + + <ul> + <li>New <a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code + <supports-screens>}</a> element lets you specify the device screen sizes that your + application is designed and tested to support, where "size" is a combination + of resolution and density. If your application is run on a device whose screen + size is not specified in the <code><supports-screen></code> element, the system + displays the application in <em>compatibility mode</em>, which performs best-effort scaling + of the application UI to match the resolution and density of the screen. + + <p>The attributes available for defining an application's screen support are: + + <ul> + + <li><code>smallScreen</code>: Boolean value that indicates whether the + application is designed to run on devices with small screens. + Examples: QVGA low density; VGA high density. + </li> + <li><code>normalScreens</code>: Boolean value that indicates whether + the application is designed to run on devices with normal screens. + Examples: WQVGA low density; HVGA medium density; WVGA high density. + </li> + <li><code>largeScreens</code>: Boolean value that indicates whether + the application is designed to run on devices with significantly + larger screens, such that special care may be required on + the application's part to make proper use of the screen area. + Examples: VGA medium density; WVGA medium density. + </li> + <li><code>anyDensity</code>: Boolean value that indicates whether + the application can accommodate any screen density. + </li> + <li><code>resizable</code>: Boolean value that indicates whether + the application can expand its layout to fit slightly larger screens. + </li> + </ul> + </p> + </li> + + <li>New <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code <uses-feature>}</a> + element lets an application specify hardware (or other) + features that it requires to function normally. When an application + specifies such features, the system allows the application to be installed only + on devices that offer the required features. The element supports these + attributes: + <ul> + <li><code>name</code>: The name of the feature required by the application. Currently accepts + "android.hardware.camera" and "android.hardware.camera.autofocus" values, which specify that a + camera and camera autofocus are required, respectively.</li> + <li><code>glEsVersion</code>: Indicates the minimum version of OpenGL ES required.</li> + </ul> + </li> + <li>New attributes for the + <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code <uses-sdk>}</a> element: + <ul> + <li><code>maxSdkVersion</code>: This indicates the maximum API Level on which an application is + designed to run. If an application declares this attribute, the Android system prevents the user + from installing the application if the system's API Level is higher than the value specified in + this attribute. </li> + <li><code>targetSdkVersion</code>: This indicates the API Level that the application is targeting. + It is able to run on older versions (down to minSdkVersion), but was explicitly tested to + work with the version specified here. Specifying this version allows the platform to + disable compatibility code that is not required or enable newer features that are not + available to older applications. </li> + </ul> + </li> + + </li> + </ul> + +<h4>New Permissions</h4> + + <ul> + <li>{@link android.Manifest.permission#CHANGE_WIFI_MULTICAST_STATE + CHANGE_WIFI_MULTICAST_STATE}: Allows applications to enter Wi-Fi + Multicast mode. + </li> + <li>{@link android.Manifest.permission#GLOBAL_SEARCH}: Allows the + global search system to access the data of a specified content provider. + </li> + <li>{@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}: + Allows an application to install a location provider into the Location Manager. + </li> + <li>{@link android.Manifest.permission#READ_HISTORY_BOOKMARKS READ_HISTORY_BOOKMARKS}: + Allows an application to read (but not write) the user's browsing history + and bookmarks. + </li> + <li>{@link android.Manifest.permission#WRITE_HISTORY_BOOKMARKS WRITE_HISTORY_BOOKMARKS}: + Allows an application to write (but not read) the user's browsing history + and bookmarks. + </li> + <li>{@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE WRITE_EXTERNAL_STORAGE}: + Allows an application to write to external storage. Applications using API Level 3 + and lower will be implicitly granted this permission (and this will be visible to + the user); Applications using API Level 4 or higher must explicitly request this + permission. + </li> + </ul> +<h3 id="api-diff">API Change Details</h3> +<p>For a detailed view of API changes in Android 1.6 (API Level 4), see the <a +href="{@docRoot}sdk/api_diff/4/changes.html">API Differences Report</a>.</p> |