From c44f3907c4a45a1b3724535bf4aa6de7f31224ee Mon Sep 17 00:00:00 2001 From: Scott Main Date: Thu, 3 Mar 2011 16:10:21 -0800 Subject: docs: add redirects for preview docs Change-Id: Iafdaa10ea305aad3faa24e3a07ea8c2be06442f1 --- docs/html/sdk/preview/features.jd | 188 +--------------------------------- docs/html/sdk/preview/index.jd | 183 +-------------------------------- docs/html/sdk/preview/installing.jd | 64 +----------- docs/html/sdk/preview/requirements.jd | 7 +- docs/html/sdk/preview/upgrading.jd | 7 +- 5 files changed, 21 insertions(+), 428 deletions(-) diff --git a/docs/html/sdk/preview/features.jd b/docs/html/sdk/preview/features.jd index cd0dea12405b..d7ecc47ce8f4 100644 --- a/docs/html/sdk/preview/features.jd +++ b/docs/html/sdk/preview/features.jd @@ -1,186 +1,8 @@ -page.title=Introduction to Honeycomb @jd:body -

Welcome to the Honeycomb preview SDK. Honeycomb is the next major release of the Android -platform and is optimized for tablet devices. This document provides an introduction to the new -platform features and APIs available in Honeycomb.

- - -

Fragments

- -
- -

Fragment Layout. An activity with two -fragments: one with a list view, on the left, and one that displays selected content on the -right. This demo is available in the samples package.

-
- - -

A new framework component that allows you to separate distinct elements of an activity into -self-contained modules that define their own UI and lifecycle—defining what may be -considered "sub-activities".

- - -

For more information, see the Fragments developer guide.

- - -

Action Bar

- -

A replacement for the traditional title bar, which provides users quick access to global -actions and different navigation modes.

- - - -

Action Bar. An action bar with a custom logo, -tabs, and Options Menu. This demo is available in the samples package.

- -

For more information, see the Action Bar developer guide.

- - -

System Clipboard

- -

Applications can copy and paste data (beyond mere text) to and from the system-wide -clipboard.

- - - -

See {@link android.content.ClipData} and {@link android.content.ClipboardManager} -for more information. You can also see an example implementation of copy/paste in an updated -version of the NotePad application (available in the samples package).

- - -

Drag and Drop

- -

New APIs to perform drag and drop operations, leveraging the system clipboard APIs to -transport data.

- - - -

See {@link android.view.DragEvent} and {@link android.view.View.OnDragListener} for more -information.

- - -

New Animations

- -

An all new animation framework.

- - - -

See the {@link android.animation} package.

- - -

Extended App Widgets

- -

App widgets can now be more interactive and accept finger gestures.

- - - - -

Extended Status Bar Notifications

- -

The {@link android.app.Notification} class has been extended to support more content-rich -status bar notifications when on xlarge screens.

- - - - -

Plus Android 2.3

- -

Honeycomb includes all platform changes introduced for Android 2.3.

- -

To take full advantage of Honeycomb, you should also be aware of the new features -and APIs introduced for Android 2.3. To learn more, read the Android 2.3 release notes.

- - - - - - - - - - - - - - - - - - - + +

You should have already been redirected by your browser. Please go to the +Android 3.0 Platform.

\ No newline at end of file diff --git a/docs/html/sdk/preview/index.jd b/docs/html/sdk/preview/index.jd index edfa02b38980..ed8f7e0d5522 100644 --- a/docs/html/sdk/preview/index.jd +++ b/docs/html/sdk/preview/index.jd @@ -1,183 +1,2 @@ -page.title=Android 3.0 Preview SDK +sdk.redirect=true @jd:body - -

Android 3.0 is the next major release of the Android platform and is optimized for tablet -devices. We're offering a Preview SDK so you can get a head-start developing -applications for it or simply optimize your existing application for upcoming -tablets.

- - -

What is the Preview SDK?

- -

The Android 3.0 Preview SDK is an early look at the upcoming version of Android 3.0, for -developers only.

- -

The Preview SDK includes:

- - -
-

Be aware that:

- -
- - -

About emulator performance

- -

Because the Android emulator must simulate the ARM instruction set architecture on your -computer and the WXGA screen is significantly larger than what the emulator -normally handles, emulator performance is much slower than usual.

- -

In particular, initializing the emulator can be slow and can take several -minutes, depending on your hardware. When the emulator is booting there is -limited user feedback, so please be patient and continue waiting until you see -the home screen appear.

- -

We're working hard to resolve the performance issues in the emulator and it will improve in -future releases. In the meantime, we wanted to give developers access to new APIs and an basic test -environment as early as possible.

- -

Keeping in mind that performance on the emulator does not reflect the speed or performance of -apps on actual devices running Android 3.0, developing and testing on the emulator is still an -important tool in evaluating your application's appearance and functionality on the new platform. -

- - - - - -

What can I do with the preview?

- -

The Preview SDK is intended for testing existing applications on the new platform and -developing new applications with new Android 3.0 APIs.

- -

If you have an existing Android application, you don't have to do anything. Android -applications are always forward-compatible. If your application is a good citizen of the Android -APIs, your app should work fine on devices running Android 3.0 without any additional work. However, -in order to ensure proper performance and provide users a better experience when running your -application on an Android 3.0 tablet, we recommend that you perform the following:

- -
    -
  1. Test your application on Android 3.0 -

    Simply install the Android 3.0 preview in your Android SDK, create an AVD using the -Android 3.0 system image, install your application, and run some tests.

    -

    As mentioned above, your application should perform as expected. You might, however, -discover that your activity layouts are less than ideal on a large screen or some other aspects -of your application don't behave the way you expect.

    -
    2. -
  2. Inherit the new "Holographic" theme -

    Android 3.0 offers an updated set of UI widgets that are redesigned for use on larger screens -such as tablets and incorporate the new holographic theme. Your existing application can inherit -the new design simply by setting the {@code <uses-sdk>} -element's {@code android:targetSdkVersion} attribute to {@code "Honeycomb"}.

    -

    If you do not update the {@code android:targetSdkVersion} attribute and the {@code -android:minSdkVersion} is set to "9" or lower, then your application uses the widget designs -from Android 2.3 and does not inherit the holographic theme.

    -

    In order for your application to match the rest of the system UI, we highly recommend you -make this change to inherit the new widget styles and system theme. However, beware that doing so -might conflict with color or text designs you applied to your application based on the previous -system theme, so you should be sure to inspect your application UI when using the holographic -theme.

    -
    3. -
  3. Provide alternative layouts for extra large screens -

    As discussed in the guide to Supporting Multiple Screens, Android -2.3 and above support the xlarge resource qualifier, which you should use to supply -alternative layouts for extra large screens.

    -

    By providing alternative layouts for some of your activities when running on extra large -screens, you can improve the user experience of your application on a tablet without using any -new APIs.

    -

    For example, here are some things to consider when creating a new layout for tables:

    -
      -
    • Landscape layout: The "normal" orientation for tablets is usually landscape (wide), so -you should be sure that your activities offer an appropriate layout for such a wide viewing -area.
      • -
    • Button position: Consider whether the position of the most common buttons in your UI are -easily accessible while holding a tablet with two hands.
      • -
    -

    Note: You can add alternative resources for xlarge -screens without changing your {@code minSdkVersion}. For example, if you add alternative layouts in -res/layout-xlarge/ and your application is compatible with older versions, such -as Android 1.5—which doesn't support xlarge screens—this layout directory is -simply ignored by those devices.

    -
    4. -
- - -

Otherwise, if you want to develop a new application or upgrade your existing application to -use APIs added in Android 3.0, we encourage you to get started by developing against the Android -3.0 preview platform. You can get started the same way as you would for any other version of -Android.

- - -

To get started—whether testing an existing application or creating a new one—follow -the procedure in the following section to install the Preview SDK.

- - - -

How do I get it?

- -

To get the Preview SDK, you can download it using the Android SDK and AVD Manager.

- -

If you're new to Android development, start by downloading the -Android SDK starter package.

- -

Launch the Android SDK and AVD -Manager and install the following:

- - -

Note: Be sure to install the documentation component for the -Honeycomb Preview SDK. The API reference for the Android 3.0 API is not available -online.

- -

Once you have installed these components, open your SDK directory and navigate to {@code -docs/sdk/} and open {@code index.html} in your browser.

- - - -

Known issues

- -

The following known issues occur for Android 3.0 AVDs that are loaded in the emulator:

- - - - -
-

For an overview of new features in Android 3.0, read the Platform Highlights.

-
- diff --git a/docs/html/sdk/preview/installing.jd b/docs/html/sdk/preview/installing.jd index c835c49cac1a..94c6f2f9ab95 100644 --- a/docs/html/sdk/preview/installing.jd +++ b/docs/html/sdk/preview/installing.jd @@ -1,62 +1,8 @@ -page.title=Getting Started with Honeycomb @jd:body -

First, you need to set up your development environment with the new SDK Tools and preview -platform:

+ -
    -
  1. Unpack the SDK Tools r8 package you've received. -

    If you have an existing Android SDK directory, simply replace your existing {@code -tools/} directory with the one from the new package and add the {@code platform-tools/} -directory along side it (at the root of the SDK directory).

    2. -
  2. Unpack the platform package ({@code android-Froyo}) and place it in your SDK's {@code -platforms/} directory.
    3. -
  3. If you're using Eclipse, also update your Eclipse plugin using the provided archive file. -
      -
    1. Select Help > Install new software.
      2. -
    2. Click Add.
      3. -
    3. Click Archive.
      4. -
    4. Locate and select the archive file. Click OK. -

      Developer Tools now appear in the Available Software window and you can proceed -to install the plugin.

      -
      5. -
    -
    4. -
- -

Note: Beginning with SDK Tools r8 (the version you've received), -the {@code adb} tool is now located in the {@code <sdk>/platform-tools/} directory (instead -of in {@code <sdk>/tools/}). Be sure to update your {@code PATH} environment variable and any -build/debugging scripts you have.

- - - -

Set Up Your AVD and Application

- -

With your SDK now set up, follow these steps to start developing an application for -Honeycomb.

- -
    - -
  1. Create a new AVD targeted to "Android Froyo (Preview)" and with a custom skin resolution of -1280 x 800.
    2. - -
  2. Set the build target of your application to "Android Froyo (Preview)".
    3. -
  3. Set your manifest file's {@code <uses-sdk>} element to use {@code -android:minSdkVersion="Froyo"}. For example: -
    -<manifest>
-    <uses-sdk android:minSdkVersion="Froyo" />
-    ...
-</manifest>
-
    -

    "Froyo" is a provisional API Level for the Honeycomb release, used only during the preview -period. When the APIs are -finalized and the SDK is released publicly, you must update this with the appropriate API Level -integer.

    -

    Note: By providing your {@code <uses-sdk>} element in the -manifest file before the {@code <application>} element, your application will -automatically apply the new Holographic theme.

    -
    4. - -
+

You should have already been redirected by your browser. Please go to +Installing the SDK.

\ No newline at end of file diff --git a/docs/html/sdk/preview/requirements.jd b/docs/html/sdk/preview/requirements.jd index 1e6b26b9077a..b5aed80ef644 100644 --- a/docs/html/sdk/preview/requirements.jd +++ b/docs/html/sdk/preview/requirements.jd @@ -1,5 +1,8 @@ -sdk.redirect=true - @jd:body + +

You should have already been redirected by your browser. Please go to the +SDK System Requirements.

\ No newline at end of file diff --git a/docs/html/sdk/preview/upgrading.jd b/docs/html/sdk/preview/upgrading.jd index 1e6b26b9077a..1c53bdbfe07f 100644 --- a/docs/html/sdk/preview/upgrading.jd +++ b/docs/html/sdk/preview/upgrading.jd @@ -1,5 +1,8 @@ -sdk.redirect=true - @jd:body + +

You should have already been redirected by your browser. Please go to +the Android SDK.

\ No newline at end of file -- cgit v1.2.3-59-g8ed1b