A fragment must always be embedded in an activity and the fragment's lifecycle is directly -affected by the activity's lifecycle. For example, when the activity is paused, so are all +affected by the host activity's lifecycle. For example, when the activity is paused, so are all fragments in it, and when the activity is destroyed, so are all fragments. However, while an activity is running (it is in the resumed lifecycle state), you can manipulate each fragment independently, such as add or remove them. When you perform such a -fragment transaction, you can it to a back stack managed by the +fragment transaction, you can also add it to a back stack that's managed by the activity—each back stack entry in the activity is a record of the fragment transaction that occurred. The back stack allows the user to reverse a fragment transaction (navigate backwards), by pressing the BACK key.
diff --git a/docs/html/sdk/preview/start.jd b/docs/html/sdk/preview/start.jd index be1e84b5b650e..ec01d0c4ae62b 100644 --- a/docs/html/sdk/preview/start.jd +++ b/docs/html/sdk/preview/start.jd @@ -3,10 +3,9 @@ page.title=Getting Started with the Android 3.0 PreviewWelcome to Android 3.0!
-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.
+Android 3.0 is the next major release of the Android platform and is optimized for larger screen +devices, particularly tablets. We're offering a preview SDK so you can get a head-start developing +applications for it or simply test and optimize your existing application for upcoming devices.
Be aware that:
When you have an existing application and you want to maintain compatibility with older versions of Android.
When you want to upgrade your application to use APIs introduced in Android 3.0 or - create an all new application targeted to tablet devices.
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.
We're working hard to resolve the performance issues and it will improve in future releases. -Unfortunately, the emulator will perform slowly during your trial with the preview SDK. Please -continue to use the emulator to evaluate your application's appearance and functionality on Android -3.0.
+Unfortunately, the emulator will perform slowly during your trial with the preview SDK. For the time +being, the emulator is still best way to evaluate your application's appearance and functionality on +Android 3.0.Tip: To improve the startup time for the emulator, enable snapshots for the AVD when you create it with the SDK and AVD Manager (there's a checkbox in @@ -83,7 +82,8 @@ used to quickly relaunch the AVD next time. However, when you choose to save a s emulator will be slow to close, so you might want to enable Save to snapshot only for the first time you launch the AVD.
-The following known issues occur for Android 3.0 AVDs that are loaded in the emulator:
If you've already developed an application for Android, there are a few things you can do -to optimize it for a tablet experience, without changing the minimum platform version required (you -don't need to change the manifest {@code minSdkVersion}).
+to optimize it for a tablet-style experience, without changing the minimum platform version required +(you don't need to change the manifest {@code minSdkVersion}).Note: All Android applications are forward-compatible, so there's nothing you have to do—if your application is a good citizen of the Android APIs, your app should work fine on devices running Android 3.0. However, in order to provide users -a better experience when running your app on an Android 3.0 tablet, we recommend that you update -your application to adapt to the new system theme and optimize your application for larger -screens.
+a better experience when running your app on an Android 3.0 tablet or similar-size device, we +recommend that you update your application to adapt to the new system theme and optimize your +application for larger screens.Here's what you can do to optimize your application for tablets running Android 3.0:
@@ -189,10 +189,10 @@ for Screen Independence. -If you want to develop something truly for tablets running Android 3.0, then you need to use new -APIs available in Android 3.0. This section introduces some of the new features that you +
If you want to develop something truly for tablet-type devices running Android 3.0, then you need +to use new APIs available in Android 3.0. This section introduces some of the new features that you should use.
The first thing to do when you create a project with the Android 3.0 preview is set the
- Additionally, you should decide whether your application is for only tablet devices
(specifically, xlarge devices) or for devices of all sizes that may run Android 3.0.Publishing your app for tablets only
+Publishing your app for tablet-type devices only