diff --git a/docs/html/guide/components/activities.jd b/docs/html/guide/components/activities.jd index b4617fb9d82de..5e6917bac0f5a 100644 --- a/docs/html/guide/components/activities.jd +++ b/docs/html/guide/components/activities.jd @@ -4,12 +4,6 @@ page.tags=activity,intent
-

Quickview

- -

In this document

  1. Creating an Activity diff --git a/docs/html/guide/components/bound-services.jd b/docs/html/guide/components/bound-services.jd index 653c7a0b785e8..4215f0f29dce9 100644 --- a/docs/html/guide/components/bound-services.jd +++ b/docs/html/guide/components/bound-services.jd @@ -6,12 +6,6 @@ parent.link=services.html
      -

      Quickview

      -
        -
      • A bound service allows other components to bind to it, in order to interact with it and -perform interprocess communication
      • -
      • A bound service is destroyed once all clients unbind, unless the service was also started
      • -

      In this document

      1. The Basics
      2. diff --git a/docs/html/guide/components/fragments.jd b/docs/html/guide/components/fragments.jd index 32c9f99628580..0cc5f7268f8a2 100644 --- a/docs/html/guide/components/fragments.jd +++ b/docs/html/guide/components/fragments.jd @@ -5,15 +5,6 @@ parent.link=activities.html
        - -

        Quickview

        -
          -
        • Fragments decompose application functionality and UI into reusable modules
        • -
        • Add multiple fragments to a screen to avoid switching activities
        • -
        • Fragments have their own lifecycle, state, and back stack
        • -
        • Fragments require API Level 11 or greater
        • -
        -

        In this document

        1. Design Philosophy
        2. diff --git a/docs/html/guide/components/processes-and-threads.jd b/docs/html/guide/components/processes-and-threads.jd index c8c376417a4dd..e7ef7ba3fa10e 100644 --- a/docs/html/guide/components/processes-and-threads.jd +++ b/docs/html/guide/components/processes-and-threads.jd @@ -5,13 +5,6 @@ page.tags=lifecycle,background
          -

          Quickview

          -
            -
          • Every application runs in its own process and all components of the application run in that -process, by default
          • -
          • Any slow, blocking operations in an activity should be done in a new thread, to avoid slowing -down the user interface
          • -

          In this document

            diff --git a/docs/html/guide/components/services.jd b/docs/html/guide/components/services.jd index da01d2c5ecb5e..6e22be8e2f566 100644 --- a/docs/html/guide/components/services.jd +++ b/docs/html/guide/components/services.jd @@ -3,14 +3,6 @@ page.title=Services
              -

              Quickview

              -
                -
              • A service can run in the background to perform work even while the user is in a different -application
              • -
              • A service can allow other components to bind to it, in order to interact with it and -perform interprocess communication
              • -
              • A service runs in the main thread of the application that hosts it, by default
              • -

              In this document

              1. The Basics
              2. diff --git a/docs/html/guide/components/tasks-and-back-stack.jd b/docs/html/guide/components/tasks-and-back-stack.jd index f818873ab2567..e054313e8f3e5 100644 --- a/docs/html/guide/components/tasks-and-back-stack.jd +++ b/docs/html/guide/components/tasks-and-back-stack.jd @@ -5,14 +5,6 @@ parent.link=activities.html
                -

                Quickview

                -
                  -
                • All activities belong to a task
                • -
                • A task contains a collection of activities in the order in which the user interacts with -them
                • -
                • Tasks can move to the background and retain the state of each activity in order for users -to perform other tasks without losing their work
                • -

                In this document

                  diff --git a/docs/html/training/cloudsync/backupapi.jd b/docs/html/training/cloudsync/backupapi.jd index a5436c6d2eec6..fd35ada63bda3 100644 --- a/docs/html/training/cloudsync/backupapi.jd +++ b/docs/html/training/cloudsync/backupapi.jd @@ -41,7 +41,7 @@ new devices using the Backup API.

                  Register for the Android Backup Service

                  This lesson requires the use of the Android Backup + href="{@docRoot}google/backup/index.html">Android Backup Service, which requires registration. Go ahead and register here. Once that's done, the service pre-populates an XML tag for insertion in your Android diff --git a/docs/html/training/cloudsync/index.jd b/docs/html/training/cloudsync/index.jd index eb7df3d641721..cf7117c3a12d0 100644 --- a/docs/html/training/cloudsync/index.jd +++ b/docs/html/training/cloudsync/index.jd @@ -6,6 +6,16 @@ startpage=true @jd:body +

                  +
                  + +

                  Dependencies and prerequisites

                  +
                    +
                  • Android 2.2 (API level 8) and higher
                  • +
                  +
                  +
                  +

                  By providing powerful APIs for internet connectivity, the Android framework helps you build rich cloud-enabled apps that sync their data to a remote web service, making sure all your devices always stay in sync, and your valuable