From c89312091e291c3e0cdb3cb7df3f76250fce7d22 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Mon, 6 May 2013 16:38:42 -0700 Subject: delete obsolete tips/references to cupcake Change-Id: Ib1ddb19c42840aa830acd85a89e78c149e2f66e9 --- docs/html/guide/guide_toc.cs | 3 - docs/html/guide/topics/appwidgets/index.jd | 13 --- .../guide/topics/resources/providing-resources.jd | 102 +-------------------- docs/html/tools/building/building-cmdline.jd | 4 +- docs/html/tools/building/building-eclipse.jd | 4 +- docs/html/tools/debugging/ddms.jd | 1 - docs/html/tools/debugging/debugging-tracing.jd | 1 - docs/html/tools/testing/activity_test.jd | 12 --- 8 files changed, 6 insertions(+), 134 deletions(-) diff --git a/docs/html/guide/guide_toc.cs b/docs/html/guide/guide_toc.cs index d7aacbf817e6..f3d937a25f68 100644 --- a/docs/html/guide/guide_toc.cs +++ b/docs/html/guide/guide_toc.cs @@ -521,9 +521,6 @@
  • Screen Compatibility Mode
    • -
  • diff --git a/docs/html/guide/topics/appwidgets/index.jd b/docs/html/guide/topics/appwidgets/index.jd index cdbf827fdf59..cabbe9060f72 100644 --- a/docs/html/guide/topics/appwidgets/index.jd +++ b/docs/html/guide/topics/appwidgets/index.jd @@ -466,19 +466,6 @@ AppWidgetProvider methods as appropriate. -

    Note: In Android 1.5, there is a known issue -in which the -onDeleted() method will not be called when it should be. To work -around this issue, -you can implement {@link -android.appwidget.AppWidgetProvider#onReceive(Context,Intent) -onReceive()} as described in this - -Group post -to receive the onDeleted() callback. -

    -

    The most important AppWidgetProvider callback is {@link android.appwidget.AppWidgetProvider#onUpdate(android.content.Context, android.appwidget.AppWidgetManager, int[]) onUpdate()} because it is called when diff --git a/docs/html/guide/topics/resources/providing-resources.jd b/docs/html/guide/topics/resources/providing-resources.jd index 5097cc4ce5ca..aec7fa70f7b0 100644 --- a/docs/html/guide/topics/resources/providing-resources.jd +++ b/docs/html/guide/topics/resources/providing-resources.jd @@ -21,14 +21,8 @@ device configurations

  • Creating alias resources
    • -
  • Providing the Best Device Compatibility with Resources -
      -
    1. Providing screen resource compatibility for Android -1.5
      2. -
    -
    • +
  • Providing the Best Device Compatibility with Resources
  • How Android Finds the Best-matching Resource
    • -
  • Known Issues

    • See also

    @@ -783,9 +777,6 @@ orientation" described above.

    1.6 or higher). See the Android API levels document for more information about these values.

    -

    Caution: Android 1.5 and 1.6 only match resources -with this qualifier when it exactly matches the platform version. See the section below about Known Issues for more information.

    @@ -970,70 +961,7 @@ greater, you do not need default drawable resources when you provide al resources with the screen density qualifier. Even without default drawable resources, Android can find the best match among the alternative screen densities and scale the bitmaps as necessary. However, for the best experience on all types of devices, you should -provide alternative drawables for all three types of density. If your {@code minSdkVersion} is -less than 4 (Android 1.5 or lower), be aware that the screen size, density, and aspect -qualifiers are not supported on Android 1.5 or lower, so you might need to perform additional -compatibility for these versions.

    - - -

    Providing screen resource compatibility for Android 1.5

    - -

    Android 1.5 (and lower) does not support the following configuration qualifers:

    -
    -
    Density
    -
    {@code ldpi}, {@code mdpi}, {@code ldpi}, and {@code nodpi}
    -
    Screen size
    -
    {@code small}, {@code normal}, and {@code large}
    -
    Screen aspect
    -
    {@code long} and {@code notlong}
    -
    - -

    These configuration qualifiers were introduced in Android 1.6, so Android 1.5 (API level 3) and -lower does not support them. If you use these configuration qualifiers and do not provide -corresponding default resources, then an Android 1.5 device might use any one of the resource -directories named with the above screen configuration qualifiers, because it ignores these -qualifiers and uses whichever otherwise-matching drawable resource it finds first.

    - -

    For example, if your application supports Android 1.5 and includes drawable resources for -each density type ({@code drawable-ldpi/}, {@code drawable-mdpi/}, and {@code drawable-ldpi/}), -and does not include default drawable resources ({@code drawable/}), then -an Android 1.5 will use drawables from any one of the alternative resource directories, which -can result in a user interface that's less than ideal.

    - -

    So, to provide compatibility with Android 1.5 (and lower) when using the screen configuration -qualifiers:

    -
      -
    1. Provide default resources that are for medium-density, normal, and notlong screens. - -

      Because all Android 1.5 devices have medium-density, normal, not-long screens, you can -place these kinds of resources in the corresponding default resource directory. For example, put all -medium density drawable resources in {@code drawable/} (instead of {@code drawable-mdpi/}), -put {@code normal} size resources in the corresponding default resource directory, and {@code -notlong} resources in the corresponding default resource directory.

      -
      2. - -
    2. Ensure that your SDK Tools version -is r6 or greater. - -

      You need SDK Tools, Revision 6 (or greater), because it includes a new packaging tool that -automatically applies an appropriate version qualifier to any -resource directory named with a qualifier that does not exist in Android 1.0. For example, because -the density qualifier was introduced in Android 1.6 (API level 4), when the packaging tool -encounters a resource directory using the density qualifier, it adds {@code v4} to the directory -name to ensure that older versions do not use those resources (only API level 4 and higher support -that qualifier). Thus, by putting your medium-density resources in a directory without the -{@code mdpi} qualifier, they are still accessible by Android 1.5, and any device that supports the -density qualifer and has a medium-density screen also uses the default resources (which are mdpi) -because they are the best match for the device (instead of using the {@code ldpi} or {@code hdpi} -resources).

      -
      3. -
    - -

    Note: Later versions of Android, such as API level 8, -introduce other configuration qualifiers that older version do not support. To provide the best -compatibility, you should always include a set of default resources for each type of resource -that your application uses, as discussed above to provide the best device compatibility.

    +provide alternative drawables for all three types of density.

    @@ -1162,29 +1090,3 @@ type, and input method), while drawable-en has only one parameter t

    To learn more about how to use resources in your application, continue to Accessing Resources.

    - - - - -

    Known Issues

    - -

    Android 1.5 and 1.6: Version qualifier performs exact match, instead of best match

    - -

    The correct behavior is for the system to match resources marked with a version qualifier equal -to or less than the platform version on the device, but on Android 1.5 and 1.6, (API level 3 and 4), -there is a bug that causes the system to match resources marked with the version qualifier -only when it exactly matches the version on the device.

    - -

    The workaround: To provide version-specific resources, abide by this behavior. However, -because this bug is fixed in versions of Android available after 1.6, if -you need to differentiate resources between Android 1.5, 1.6, and later versions, then you only need -to apply the version qualifier to the 1.6 resources and one to match all later versions. Thus, this -is effectively a non-issue.

    - -

    For example, if you want drawable resources that are different on each Android 1.5, 1.6, -and 2.0.1 (and later), create three drawable directories: {@code drawable/} (for 1.5 and lower), -{@code drawable-v4} (for 1.6), and {@code drawable-v6} (for 2.0.1 and later—version 2.0, v5, -is no longer available).

    - - diff --git a/docs/html/tools/building/building-cmdline.jd b/docs/html/tools/building/building-cmdline.jd index e0d0d3fbcd65..b65fc786bd8d 100644 --- a/docs/html/tools/building/building-cmdline.jd +++ b/docs/html/tools/building/building-cmdline.jd @@ -244,8 +244,8 @@ adb -s emulator-5554 install path/to/your/app.apk

    Be certain to create multiple AVDs upon which to test your application. You should have one AVD for each platform and screen type with which your application is compatible. For instance, if - your application compiles against the Android 1.5 (API Level 3) platform, you should create an - AVD for each platform equal to and greater than 1.5 and an AVD for each screen type you support, then test your application on each one.

    diff --git a/docs/html/tools/building/building-eclipse.jd b/docs/html/tools/building/building-eclipse.jd index 304aa7e903a1..7a4367ac3205 100644 --- a/docs/html/tools/building/building-eclipse.jd +++ b/docs/html/tools/building/building-eclipse.jd @@ -69,8 +69,8 @@ parent.link=index.html

    Be certain to create multiple AVDs upon which to test your application. You should have one AVD for each platform and screen type with which your application is compatible. For instance, if - your application compiles against the Android 1.5 (API Level 3) platform, you should create an - AVD for each platform equal to and greater than 1.5 and an AVD for each screen type you support, then test your application on each one.

    diff --git a/docs/html/tools/debugging/ddms.jd b/docs/html/tools/debugging/ddms.jd index f641aad8d43e..d2fb47a111c5 100644 --- a/docs/html/tools/debugging/ddms.jd +++ b/docs/html/tools/debugging/ddms.jd @@ -192,7 +192,6 @@ parent.link=index.html

    Before you start method profiling in DDMS, be aware of the following restrictions: