@@ -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 <a href="#testing">test your
application</a> on all of the new screens supported in Android 1.6.
<!--See <a href="#migrating">Migrating</a> for strategies e you can continue using the previous API level and use target API level, or you can just compile. --></p>
application</a> on all supported screens. </p>
<p>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. </p>
<h2 id="overview">Overview of Screens Support</h2>
<p>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.</p>
<p>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.</p>
<h3>Terms and Concepts</h3>
...
...
@@ -462,7 +464,7 @@ pixels</a> for more information. </p>
<h3 id="attrs">Manifest attributes for screens support</h3>
<p> Android 1.6 introduces a new manifest element,
<p> Android 1.6 introduced a new manifest element,
<p>Localized UI strings match the locales that are accessible
through Settings.</p>
<h2 id="api-changes">Emulator Skins</h2>
<h2 id="skins">Emulator Skins</h2>
<p>The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are: </p>
...
...
@@ -184,8 +185,8 @@ system to correctly determine whether an application is compatible with
the system, prior to installing the application. </p>
<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the <code><uses-sdk></code> attributes in your
application's manifest. </p>
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code><uses-sdk></code>
element in your application's manifest. </p>
<p>For more information about how to use API Level, see the <a
<p>Localized UI strings match the locales that are accessible
through Settings.</p>
<h2 id="api-changes">Emulator Skins</h2>
<h2 id="skins">Emulator Skins</h2>
<p>The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are: </p>
...
...
@@ -182,8 +183,8 @@ system to correctly determine whether an application is compatible with
the system, prior to installing the application. </p>
<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the <code><uses-sdk></code> attributes in your
application's manifest. </p>
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code><uses-sdk></code>
element in your application's manifest. </p>
<p>For more information about how to use API Level, see the <a
<p>Localized UI strings match the locales that are accessible
through Settings.</p>
<h2 id="api-changes">Emulator Skins</h2>
<h2 id="skins">Emulator Skins</h2>
<p>The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are: </p>
...
...
@@ -198,8 +199,8 @@ system to correctly determine whether an application is compatible with
the system, prior to installing the application. </p>
<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the <code><uses-sdk></code> attributes in your
application's manifest. </p>
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code><uses-sdk></code>
element in your application's manifest. </p>
<p>For more information about how to use API Level, see the <a
<li>In viewport meta tag, target-densityDpi can be specified to control the default zoom.</li>
<li><meta name="viewport" content="width=device-width,minimum-scale=1.0,maximum-scale=1.0,target-densityDpi=device-dpi"/> will ensure the page to be loaded with 100% on any dpi devices.</li>
<p><strong>2. Install the ADT Plugin for Eclipse</strong></p>
<p>If you are developing in Eclipse, set up a remote update site and install the Android Development Tools (ADT) plugin. The ADT plugin adds powerful extensions to the Eclipse IDE that help you to create and debug Android applications more easily and faster. If you use Eclipse, ADT gives you an incredible boost in developing Android
applications. </p>
<p>If you are developing in Eclipse, set up a remote update site and install the Android Development Tools (ADT) plugin.</p>
<p>For detailed instructions, see <a href="{@docRoot}sdk/eclipse-adt.html">Installing and Updating ADT</a>.</p>
<p><strong>3. Download one or more Android platforms</strong></p>
<p><strong>3. Add Android platforms to your SDK</strong></p>
<p>To develop an application, you need to download at least one Android platform component and install it into your SDK.
<p>Use the Android SDK and AVD Manager, included in the SDK starter package, to add one or more Android platforms (for example, Android 1.6 or Android 2.0) to your SDK. In most cases, you will want to download multiple platforms, so that you can build your application on the lowest version you want to support, but test against higher versions that you intend the application to run on. Information about each platform is available at left, under "Downloadable SDK Components."</p>
<p>Each downloadable platform includes an Android library and system image, as well as emulator skins, sample code and applications, and more. In most cases, you will want to download multiple platforms into your SDK, so that you can build your application on the minimum version you want to support, but test it against higher versions that you intend the application to run on.</p>
<p>For more information about how to add platforms and other SDK components, see <a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a>.</p>
<p>While you are downloading platforms, make sure to download the latest documentation package. The documentation covers all versions of the API and lets you filter out those versions that your application won't support. </p>
<p><strong>4. Get the latest documentation</strong></p>
<p>To download platforms or any other SDK component, use the Android SDK and AVD Manager tool, included in the SDK starter package. For more information, see <a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a>. Detailed information about individual platforms and other components are provided in the navigation bar at left, under "Downloadable SDK Components."</p>
<p>If you develop while offline, use the Android SDK and AVD Manager to download the latest documentation package. The documentation covers all versions of the API and lets you filter out those versions that your application won't support. Once installed, the documentation is also available to you directly from the Eclipse IDE. </p>
<p><strong>5. Download other SDK components</strong></p>
<p>You can use the Android SDK and AVD Manager to download other SDK components, such as the SDK add-ons. An SDK add-on provides a development environment for an Android external library or a customized Android system image. For example, the Google APIs Add-On lets you develop an application that takes advantage of the Google Maps external library. </p>
<p><strong>4. Download other SDK components</strong></p>
<p>In addition to Android platforms, you can also download SDK add-ons and a local version of the Android developer documentation to your SDK environment. </p>
<p>An SDK add-on provides a development environment for an Android external
library or a customized (but fully compliant) Android system image. You can install an add-on if you want to make use of its external library in your application. For example, the Google APIs Add-On lets you develop an application that takes advantage of the Google Maps external library. </p>
<p>Use the Android SDK and AVD Manager tool to download add-ons and other components into your SDK. </p>
<p><strong>5. Get started with an application project</strong></p>
<p><strong>6. Get started with an application project</strong></p>
<p>Once you've set up your SDK, the next step is to start a new application project or move existing applications into the new SDK.</p>
