diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index b3b6371d97370..083003236a25b 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -324,22 +324,24 @@ 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.

-

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.

+

To use filtering, select the checkbox to enable filtering, just below the +page search box. Then set the "Filter by API Level" control to the same API +Level as 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.

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, -simply select the highest available API Level.

+

If you decide that you don't want to filter the API documentation, just +disable the feature using the checkbox. By default, API Level filtering is +disabled, so that you can view the full framework API, regardless of API Level. +

Also note that the reference documentation for individual API elements -specifies the API Level at which the elements were introduced. The API Level +specifies the API Level at which each 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 class members is specified in their detailed description headers, diff --git a/docs/html/guide/practices/screens_support.jd b/docs/html/guide/practices/screens_support.jd index 1d16d886f960c..88975f8c09283 100644 --- a/docs/html/guide/practices/screens_support.jd +++ b/docs/html/guide/practices/screens_support.jd @@ -1069,28 +1069,29 @@ not. Once you've tested your application and found that it displays properly on various screen sizes, you should make sure to add the corresponding size attribute(s) to your application's manifest. --> +

+

+

Figure 3. + A typical set of AVDs for testing screens support.

+

+

As a test environment for your applications, set up a series of AVDs that emulate the screen sizes and densities you want to support. The Android SDK -includes four emulator skins to get you started. You can use the Android AVD +includes six emulator skins to get you started. You can use the Android AVD Manager or the android tool to create AVDs that use the various emulator skins and you can also set up custom AVDs to test densities other than the defaults. For general information about working with AVDs, see Android Virtual Devices.

-

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

+

The Android SDK provides a set of default emulator skins that you can use for +testing. The skins are included as part of each Android platform that you can +install in your SDK. The Android 1.6 platform offers these default skins:

QVGA (240x320, low density, small screen)
- WQVGA400 (240x400, low density, normal screen) -
- WQVGA432 (240x432, low density, normal screen) -
HVGA (320x480, medium density, normal screen)

+

The Android 2.0 platform offers all of the Android 1.6 default skins, +above, plus:

+ +

+ WQVGA400 (240x400, low density, normal screen) +
+ WQVGA432 (240x432, low density, normal screen) +

+

If you are using the android tool command line to create your AVDs, here's an example of how to specify the skin you want to use:

@@ -1130,6 +1143,12 @@ monitor. Using the default densities, the emulator skins included in the Android

QVGA, low density: 3.3"

+

+ WQVGA, low density: 3.9" +

+

+ WQVGA432, low density: 4.1" +

HVGA, medium density: 3.6"

@@ -1141,6 +1160,12 @@ monitor. Using the default densities, the emulator skins included in the Android +

+

+

Figure 4. + Resolution and density options that you can use, when creating an AVD using the AVD Manager.

+

+

You should also make sure to test your application on different physical screen sizes within a single size-density configuration. For example, according to Table 1, the minimum supported diagonal of QVGA is 2.8". @@ -1150,21 +1175,35 @@ To display this is on a 30" monitor you will need to adjust the value passed to

emulator -avd <name> -scale 0.6

-

If you would like to test your application on a screen not supported by the -built-in skins, you can either adjust an existing skin, or create a custom -resolution.

+

If you would like to test your application on a screen that uses a resolution +or density not supported by the built-in skins, you can either adjust an +existing skin, or create an AVD +that uses a custom resolution or density.

-

For example, to test on a large WVGA800 screen with medium density:

+

In the AVD Manager, you can specify a custom skin resolution or density in +the Create New AVD dialog, as shown in Figure 4, at right.

+ +

In the android tool, follow these steps to create an AVD with a +custom resolution or density:

Create an AVD based on the WVGA800 skin (using the android -tool's command line.)
Answer "yes" when asked about using custom hardware
enter "160" when asked about the value for hw.lcd.density -(120-low, 160-medium, 240-high).
Use the create avd command to create a new AVD, specifying +the --skin option with a value that references either a default +skin name (such as "WVGA800") or a custom skin resolution (such as 240x432). +Here's an example: +
```
android create avd -n <name> -t <targetID> --skin WVGA800
```
+
To specify a custom density for the skin, answer "yes" when asked whether +you want to create a custom hardware profile for the new AVD.
Continue through the various profile settings until the tool asks you to +specify "Abstracted LCD density" (hw.lcd.density). Consult Table 1, earlier in this document, and enter the appropriate +value. For example, enter "160" to use medium density for the WVGA800 screen.
Set any other hardware options and complete the AVD creation.

-

When running this AVD, the emulator will emulate a 5.8" WVGA screen.

+

In the example above (WVGA medium density), the new AVD will emulate a 5.8" +WVGA screen.

As an alternative to adjusting the emulator skin configuration, you can use the emulator skin's default density and add the -dpi-device option @@ -1172,25 +1211,6 @@ to the emulator command line when starting the AVD. For example,

emulator -avd WVGA800 -scale 96dpi -dpi-device 160

-

If you would like to test your application with a resolution not supported by -the provided skins, you can use the desired resolution in place of the skin -name. For instance, for FWQVGA you would use:

- -

android create avd ... --skin 240x432

- -

Next, you would need to set the proper density for the screen. When asked by -the tool whether you want to create a custom hardware profile for the new AVD, -enter "yes". Continue through the various profile settings until the tools asks -you to specify "Abstracted LCD density". Consult Table 1, -earlier in this document, and enter the appropriate value. For the FWQVGA -screen, the density should be "160", or medium.

- -

-

-

Figure 3. - A typical set of AVDs for testing screens support.

-

-

Screen-Compatibility Examples

diff --git a/docs/html/images/screens_support/avd-density.png b/docs/html/images/screens_support/avd-density.png new file mode 100644 index 0000000000000..e3fc36ec5c692 Binary files /dev/null and b/docs/html/images/screens_support/avd-density.png differ diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd index 15d19383b7c73..46126820410e2 100644 --- a/docs/html/sdk/android-1.5.jd +++ b/docs/html/sdk/android-1.5.jd @@ -16,7 +16,6 @@ sdk.platform.deployableDate=May 2009

Built-in Applications

-

API level
Built-in Applications
Locales
Emulator Skins
Other Notes
Framework API
1. API level