From 08320015f853d014238b24716cb6cf01c5ff68bf Mon Sep 17 00:00:00 2001 From: Joe Fernandez Date: Mon, 4 Jan 2016 16:24:22 -0800 Subject: [PATCH] docs: Eclipse ADT removing and replacing mentions Batch 05, Project 01 with InfoPros b/25192800 Change-Id: I6cce84d8498ba9f0aa488b8d43b7b832e58fe899 --- .../google/play/billing/billing_integrate.jd | 40 ++++---- docs/html/google/play/licensing/setting-up.jd | 81 +++++++--------- docs/html/guide/components/aidl.jd | 14 +-- docs/html/legal.jd | 10 +- docs/html/tools/debugging/debugging-memory.jd | 93 +++---------------- docs/html/tools/help/adb.jd | 4 +- docs/html/tools/help/sdk-manager.jd | 4 +- docs/html/tools/help/zipalign.jd | 8 +- .../contacts-provider/retrieve-names.jd | 2 +- .../in-app-billing/preparing-iab-app.jd | 5 +- docs/html/training/tv/start/start.jd | 4 +- docs/html/training/volley/index.jd | 6 +- 12 files changed, 91 insertions(+), 180 deletions(-) mode change 100644 => 100755 docs/html/google/play/billing/billing_integrate.jd mode change 100644 => 100755 docs/html/google/play/licensing/setting-up.jd mode change 100644 => 100755 docs/html/guide/components/aidl.jd mode change 100644 => 100755 docs/html/legal.jd mode change 100644 => 100755 docs/html/tools/debugging/debugging-memory.jd mode change 100644 => 100755 docs/html/tools/help/adb.jd mode change 100644 => 100755 docs/html/tools/help/sdk-manager.jd mode change 100644 => 100755 docs/html/tools/help/zipalign.jd mode change 100644 => 100755 docs/html/training/contacts-provider/retrieve-names.jd mode change 100644 => 100755 docs/html/training/in-app-billing/preparing-iab-app.jd mode change 100644 => 100755 docs/html/training/tv/start/start.jd mode change 100644 => 100755 docs/html/training/volley/index.jd diff --git a/docs/html/google/play/billing/billing_integrate.jd b/docs/html/google/play/billing/billing_integrate.jd old mode 100644 new mode 100755 index 4249885177d53..c658f702dce3f --- a/docs/html/google/play/billing/billing_integrate.jd +++ b/docs/html/google/play/billing/billing_integrate.jd @@ -95,34 +95,38 @@ method calls.

To add the AIDL to your project:

    -
  1. Copy the {@code IInAppBillingService.aidl} file to your Android project. +
  2. First, download the Google Play Billing Library to your Android project: +
      +
    1. Select Tools > Android > SDK Manager.
      2. +
    2. Under Appearance & Behavior > System Settings > Android SDK, + select the SDK Tools tab to select and download Google Play Billing + Library.
    + +
  3. Next, copy the {@code IInAppBillingService.aidl} file to your project.
      -
    • If you are using Eclipse: +
    • If you are using Android Studio:
        -
      1. If you are starting from an existing Android project, open the - project in Eclipse. If you are creating a new Android project from - scratch, click File > New > - Android Application Project, then follow the - instructions in the New Android Application wizard - to create a new project in your workspace. -
        2. +
      2. Navigate to {@code src/main} in the Project tool window.
        3. -
      3. In the {@code /src} directory, click File > - New > Package, then create a - package named {@code com.android.vending.billing}. -
        4. +
      4. Select File > New > Directory and enter {@code aidl} in the + New Directory window, then select OK. -
      5. Copy the {@code IInAppBillingService.aidl} file from {@code - <sdk>/extras/google/play_billing/} and paste it into the {@code - src/com.android.vending.billing/} folder in your workspace. +
      6. Select File > New > Package and enter + {@code com.android.vending.billing} in the New Package window, then select + OK.
        7. + +
      7. Using your operating system file explorer, navigate to + {@code <sdk>/extras/google/play_billing/}, copy the + {@code IInAppBillingService.aidl} file, and paste it into the + {@code com.android.vending.billing} package in your project.
      • -
    • If you are developing in a non-Eclipse environment: Create the +
    • If you are developing in a non-Android Studio environment: Create the following directory {@code /src/com/android/vending/billing} and copy the {@code IInAppBillingService.aidl} file into this directory. Put the AIDL - file into your project and use the Ant tool to build your project so that + file into your project and use the Gradle tool to build your project so that the IInAppBillingService.java file gets generated.
    diff --git a/docs/html/google/play/licensing/setting-up.jd b/docs/html/google/play/licensing/setting-up.jd old mode 100644 new mode 100755 index f43e4aba7320f..ef9de43eff920 --- a/docs/html/google/play/licensing/setting-up.jd +++ b/docs/html/google/play/licensing/setting-up.jd @@ -6,7 +6,7 @@ parent.link=index.html
    - +

    In this document

    1. Setting Up a Publisher Account
      2. @@ -179,21 +179,24 @@ Play services.

      these steps:

        -
      1. Launch the Android SDK Manager (available under the Eclipse Window -menu or by executing {@code <sdk>/tools/android sdk}).
        2. +
      2. Launch the Android SDK Manager, available under the Android Studio Tools menu +(Tools > Android > SDK Manager) or by executing +{@code <sdk>/tools/android sdk}.
      3. Select and download Google APIs for the Android version you'd like to target (must be Android 2.2 or higher).
        4. -
      4. When the download is complete, open the AVD Manager (available under the Eclipse -Window -menu or by executing {@code <sdk>/tools/android avd}).
        5. -
      5. Click -New and set the configuration details for the new AVD.
        6. -
      6. In the dialog that appears, assign a descriptive name to the AVD and then -use the Target menu to choose the Google APIs as -the system image to run on the new AVD. Set the other configuration details as -needed and then click Create AVD to finish. The SDK tools -create the new AVD configuration, which then appears in the list of available -Android Virtual Devices.
        7. +
      7. When the download is complete, open the AVD Manager, available under the Android Studio +Tools menu (Tools > Android > AVD Manager) or by executing +{@code <sdk>/tools/android avd}.
        8. +
      8. In the Android Virtual Device Manager window, select ++ Create Virtual Device to set the configuration details for the new AVD.
        9. +
      9. In the Virtual Device Configuration window, select device hardware, then +select Next.
        10. +
      10. Select a Google API as the system image to run on the new AVD, then +select Next.
        11. +
      11. Assign a descriptive name to the AVD and then set the other configuration details as +needed.
        12. +
      12. Select Finish to create the new AVD configuration, which will appear in the +list of available Android Virtual Devices.

      If you are not familiar with AVDs or how to use them, see Managing Virtual Devices.

      above — either on an actual device or on an emulator — make sure to update your application project or build scripts as needed, so that your compiled .apk files that use licensing are deployed into that environment. -In particular, if you are developing in Eclipse, make sure that you set up a +In particular, if you are developing in Android Studio, make sure that you set up a Run/Debug Configuration that targets the appropriate device or AVD.

      You do not need to make any changes to your application's @@ -323,28 +326,22 @@ across all of your projects and maintain it centrally.

      The LVL is provided as a configured library project — once you have downloaded it, you can start using it right away.

      -

      If you are working in Eclipse with ADT, you need to add the LVL to your -workspace as a new development project, in the same way as you would a new -application project.

      +

      If you are working in Android Studio, you need to add the LVL to your +project as a new module.

        -
      1. Use the New Project Wizard to create a new -project from existing sources. Select the LVL's library directory -(the directory containing the library's AndroidManifest.xml file) as the project -root.
        2. -
      2. When you are creating the library project, you can select any application -name, package, and set other fields as needed.
        3. -
      3. For the library's build target, select Android 1.5 (API level 3) or higher.
        4. +
      4. Use the New Module Wizard to import a library module by selecting +File > New > Import Module.
        5. +
      5. In the New Module window, in Source directory, enter the LVL's +library directory (the directory containing the library's AndroidManifest.xml file) +as the project root ({@code <sdk>/extras/google/play_licensing/library/AndroidManifest.xml}), +then select Next.
        6. +
      6. Select Finish to import the library module.
      -

      When created, the project is -predefined as a library project in its project.properties file, so -no further configuration is needed.

      - -

      For more information about how to create an application project or work with -library projects in Eclipse, see Managing Projects from -Eclipse with ADT.

      +

      For more information about how to work with library modules in Android Studio, see +Managing Projects from +Android Studio.

      Copying the LVL sources to your application

      @@ -369,24 +366,10 @@ build tools to include the LVL library project sources in your application at compile time. The process for adding a reference to a library project depends on your development environment, as described below.

      -

      If you are developing in Eclipse with ADT, you should already have added the -library project to your workspace, as described in the previous section. If you +

      If you are developing in Android Studio, you should already have added the +library module to your project, as described in the previous section. If you haven't done that already, do it now before continuing.

      -

      Next, open the application's project properties window, as shown below. -Select the "Android" properties group and click Add, then -choose the LVL library project (com_android_vending_licensing) and click -OK. For more information, see - -Managing Projects from Eclipse with ADT

      . - - - -

      Figure 3. If you are -working in Eclipse with ADT, you can add the LVL library project to your -application from the application's project properties.

      - -

      If you are developing using the SDK command-line tools, navigate to the directory containing your application project and open the project.properties file. Add a line to the file that specifies the diff --git a/docs/html/guide/components/aidl.jd b/docs/html/guide/components/aidl.jd old mode 100644 new mode 100755 index 0be6e6fa56b31..78fa99696b7b5 --- a/docs/html/guide/components/aidl.jd +++ b/docs/html/guide/components/aidl.jd @@ -190,11 +190,11 @@ project's {@code gen/} directory. The generated file name matches the {@code .ai with a {@code .java} extension (for example, {@code IRemoteService.aidl} results in {@code IRemoteService.java}).

      -

      If you use Eclipse, the incremental build generates the binder class almost immediately. If you -do not use Eclipse, then the Ant tool generates the binder class next time you build your -application—you should build your project with ant debug (or ant -release) as soon as you're finished writing the {@code .aidl} file, so that your code can -link against the generated class.

      +

      If you use Android Studio, the incremental build generates the binder class almost immediately. +If you do not use Android Studio, then the Gradle tool generates the binder class next time you +build your application—you should build your project with gradle assembleDebug +(or gradle assembleRelease) as soon as you're finished writing the {@code .aidl} file, +so that your code can link against the generated class.

      2. Implement the interface

      @@ -217,7 +217,7 @@ inherited from the {@code .aidl} file.

      Here is an example implementation of an interface called {@code IRemoteService} (defined by the {@code IRemoteService.aidl} example, above) using an anonymous instance:

      - + 
       private final IRemoteService.Stub mBinder = new IRemoteService.Stub() {
     public int getPid(){
@@ -324,7 +324,7 @@ href="{@docRoot}resources/samples/ApiDemos/index.html">ApiDemos.
      
 
 
 
-  
+
 
 
      Passing Objects over IPC
      
 
diff --git a/docs/html/legal.jd b/docs/html/legal.jd
old mode 100644
new mode 100755
index 5ee6b5c314952..0a685082d5d7d
--- a/docs/html/legal.jd
+++ b/docs/html/legal.jd
@@ -70,12 +70,10 @@ Policy & Terms of Service.
      
 restrictions. Such services include:
      
 
 
      
-  
      Eclipse Android Developer Tools Plugin
      
-    
      If you're developing apps with the Eclipse IDE, we offer a free plugin called the
-Android Developer Tools (ADT) to speed up your
-development and debugging. Certain code within the ADT plugin and other packages available
-from the SDK Manager require that you agree to terms and conditions for use, reproduction and
-distribution upon installation.
      
+  
      Android Studio
      
+    
      Android Studio and other packages available from the SDK manager require that you agree
+to terms and conditions
+for use, reproduction and distribution upon installation.
      
 
   
      Google Play
      
     
      Google Play is a publicly available service through which you can distribute your apps for
diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd
old mode 100644
new mode 100755
index 261df932c8d28..71c009d7ddf23
--- a/docs/html/tools/debugging/debugging-memory.jd
+++ b/docs/html/tools/debugging/debugging-memory.jd
@@ -42,7 +42,7 @@ memory usage with tools. This guide shows you how to do that.
      
 
      The simplest place to begin investigating your app’s memory usage is the runtime log messages.
 Sometimes when a GC occurs, a message is printed to
 logcat. The logcat output is also available in the
-Device Monitor or directly in IDEs such as Eclipse and Android Studio.
      
+Device Monitor or directly in an IDE such as Android Studio.
      
 
 
      Dalvik Log Messages
      
 
@@ -240,7 +240,7 @@ can view real-time updates to your app's heap in Android Studio's
 
 
      Memory Monitor in Android Studio
      
 
      Use Android Studio to view your app's memory use: 
      
-
        
+
          
   
        1. Start your app on a connected device or emulator.
          2. 
   
        2. Open the Android run-time window, and view the free and allocated memory in the Memory
     Monitor. 
          3. 
@@ -260,7 +260,7 @@ can view real-time updates to your app's heap in Android Studio's
    
   
        3. Identify which actions in your app are likely causing too much allocation and determine where
    in your app you should try to reduce allocations and release resources.
-
      
+

    Device Monitor

      @@ -628,7 +628,7 @@ can track down problems you might have identified while viewing heap updates.

      To retrieve your heap dump from within Android Studio, use the -Memory Monitor and +Memory Monitor and HPROF viewer.

      You can also still perform these procedures in the Android monitor:

      @@ -655,10 +655,12 @@ HPROF tool. The major difference in an Android heap dump is due to the fact that number of allocations in the Zygote process. But because the Zygote allocations are shared across all app processes, they don’t matter very much to your own heap analysis.

      -

      To analyze your heap dump, you can use a standard tool like jhat or the Eclipse Memory Analyzer Tool (MAT). However, first +

      To analyze your heap dump, you can use Memory Monitor in Android Studio. +You can also use a standard tool like jhat. However, first you'll need to convert the HPROF file from Android's format to the J2SE HPROF format. You can do -this using the hprof-conv tool provided in the <sdk>/platform-tools/ +this using the hprof-conv tool provided in the +<sdk>/platform-tools/ directory. Simply run the hprof-conv command with two arguments: the original HPROF file and the location to write the converted HPROF file. For example:

      @@ -666,11 +668,9 @@ file and the location to write the converted HPROF file. For example:

      hprof-conv heap-original.hprof heap-converted.hprof -

      Note: If you're using the version of DDMS that's integrated into -Eclipse, you do not need to perform the HPROF conversation—it performs the conversion by -default.

      -

      You can now load the converted file in MAT or another heap analysis tool that understands + +

      You can now load the converted file into a heap analysis tool that understands the J2SE HPROF format.

      When analyzing your heap, you should look for memory leaks caused by:

      @@ -682,77 +682,6 @@ reference to the container Activity or Context. -

      Using the Eclipse Memory Analyzer Tool

      - -

      The Eclipse Memory Analyzer Tool (MAT) is just one -tool that you can use to analyze your heap dump. It's also quite powerful so most of its -capabilities are beyond the scope of this document, but here are a few tips to get you started. - -

      Once you open your converted HPROF file in MAT, you'll see a pie chart in the Overview, -showing what your largest objects are. Below this chart, are links to couple of useful features:

      - -
        -
      • The Histogram view shows a list of all classes and how many instances - there are of each. -

        You might want to use this view to find extra instances of classes for which you know there - should be only a certain number. For example, a common source of leaks is additional instance of - your {@link android.app.Activity} class, for which you should usually have only one instance - at a time. To find a specific class instance, type the class name into the <Regex> - field at the top of the list. -

        When you find a class with too many instances, right-click it and select - List objects > with incoming references. In the list that - appears, you can determine where an instance is retained by right-clicking it and selecting - Path To GC Roots > exclude weak references.

        -
        • - -
      • The Dominator tree shows a list of objects organized by the amount - of retained heap. -

        What you should look for is anything that's retaining a portion of heap that's roughly - equivalent to the memory size you observed leaking from the GC logs, - heap updates, or allocation - tracker. -

        When you see something suspicious, right-click on the item and select - Path To GC Roots > exclude weak references. This opens a - new tab that traces the references to that object which is causing the alleged leak.

        - -

        Note: Most apps will show an instance of - {@link android.content.res.Resources} near the top with a good chunk of heap, but this is - usually expected when your app uses lots of resources from your {@code res/} directory.

        -
        • -
      - - - -

      Figure 4. The Eclipse Memory Analyzer Tool (MAT), -showing the Histogram view and a search for "MainActivity".

      - -

      For more information about MAT, watch the Google I/O 2011 presentation, -Memory management for Android apps, -which includes a walkthrough using MAT beginning at about 21:10. -Also refer to the Eclipse Memory -Analyzer documentation.

      - -

      Comparing heap dumps

      - -

      You may find it useful to compare your app's heap state at two different points in time in order -to inspect the changes in memory allocation. To compare two heap dumps using MAT:

      - -
        -
      1. Create two HPROF files as described above, in Capturing a Heap Dump. -
      2. Open the first HPROF file in MAT (File > Open Heap Dump). -
      3. In the Navigation History view (if not visible, select Window > - Navigation History), right-click on Histogram and select - Add to Compare Basket. -
      4. Open the second HPROF file and repeat steps 2 and 3. -
      5. Switch to the Compare Basket view and click Compare the Results - (the red "!" icon in the top-right corner of the view). -
      - - - -

      Triggering Memory Leaks

      diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd old mode 100644 new mode 100755 index 2faff4f3fe5c2..06e009948d6e2 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -29,7 +29,7 @@ three components:

      • A client, which runs on your development machine. You can invoke a client from a shell -by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create +by issuing an adb command. Other Android tools such as DDMS also create adb clients.
      • A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
        • @@ -361,7 +361,7 @@ the hardware device.

        For more information about how to create an .apk file that you can install on an emulator/device instance, see Building and Running

        -

        Note that, if you are using the Eclipse IDE and have the ADT plugin installed, you do not need to use adb (or aapt) directly to install your application on the emulator/device. Instead, the ADT plugin handles the packaging and installation of the application for you.

        +

        Note that, if you are using Android Studio, you do not need to use adb (or aapt) directly to install your application on the emulator/device. Instead, Android Studio handles the packaging and installation of the application for you.

        diff --git a/docs/html/tools/help/sdk-manager.jd b/docs/html/tools/help/sdk-manager.jd old mode 100644 new mode 100755 index cc95edf6bf6a3..c8493dcfa3b5e --- a/docs/html/tools/help/sdk-manager.jd +++ b/docs/html/tools/help/sdk-manager.jd @@ -34,7 +34,7 @@ SDK checking:

      Tip: The standalone SDK Manager is still available from the -command line, but we recommend it only for use with Eclipse ADT and standalone SDK installations.

      +command line, but we recommend it only for use with standalone SDK installations.

      By default, the SDK Manager installs the latest packages and tools. Click the checkbox next to each additional SDK platform and tool that you want to install. Clear the @@ -99,7 +99,7 @@ Android Virtual Devices (AVDs) in the Android APIs (such as fragments, plus others not included in the framework at all) on devices running a platform version as old as Android 1.6. All of the activity templates available when creating -a new project with the ADT Plugin +a new project with Android Studio require this. For more information, read Support Library. diff --git a/docs/html/tools/help/zipalign.jd b/docs/html/tools/help/zipalign.jd old mode 100644 new mode 100755 index 184cdcb6ad227..c70810cd66df1 --- a/docs/html/tools/help/zipalign.jd +++ b/docs/html/tools/help/zipalign.jd @@ -16,12 +16,12 @@ when running the application.

      This tool should always be used to align your .apk file before distributing it to end-users. The Android build tools can handle -this for you. When using Eclipse with the ADT plugin, the Export Wizard -will automatically zipalign your .apk after it signs it with your private key. +this for you. Android Studio automatically aligns your .apk after it signs it with your +private key. The build scripts used -when compiling your application with Ant will also zipalign your .apk, +when compiling your application with Gradle also align your .apk, as long as you have provided the path to your keystore and the key alias in -your project {@code ant.properties} file, so that the build tools +your project {@code gradle.properties} file, so that the build tools can sign the package first.

      Caution: zipalign must only be performed diff --git a/docs/html/training/contacts-provider/retrieve-names.jd b/docs/html/training/contacts-provider/retrieve-names.jd old mode 100644 new mode 100755 index d97b81b1e3406..49d6e955536c9 --- a/docs/html/training/contacts-provider/retrieve-names.jd +++ b/docs/html/training/contacts-provider/retrieve-names.jd @@ -230,7 +230,7 @@ public class ContactsFragment extends Fragment implements {@link android.provider.ContactsContract.Contacts#DISPLAY_NAME_PRIMARY Contacts.DISPLAY_NAME_PRIMARY} requires Android 3.0 (API version 11) or later, setting your app's minSdkVersion to 10 or below generates an Android Lint warning in - Eclipse with ADK. To turn off this warning, add the annotation + Android Studio. To turn off this warning, add the annotation @SuppressLint("InlinedApi") before the definition of FROM_COLUMNS.

      Initialize the Fragment

      diff --git a/docs/html/training/in-app-billing/preparing-iab-app.jd b/docs/html/training/in-app-billing/preparing-iab-app.jd old mode 100644 new mode 100755 index ca33008d3c158..2c6e9a074d317 --- a/docs/html/training/in-app-billing/preparing-iab-app.jd +++ b/docs/html/training/in-app-billing/preparing-iab-app.jd @@ -84,9 +84,9 @@ presented with the welcome screen.

      To add the In-app Billing Version 3 library to your new In-app Billing project:

      1. Copy the {@code TrivialDrive} sample files into your Android project.
        2. -
      2. Modify the package name in the files you copied to use the package name for your project. In Eclipse, you can use this shortcut: right-click the package name, then select Refactor > Rename.
        3. +
      3. Modify the package name in the files you copied to use the package name for your project. In Android Studio, you can use this shortcut: right-click the package name, then select Refactor > Rename.
      4. Open the {@code AndroidManifest.xml} file and update the package attribute value to use the package name for your project.
        5. -
      5. Fix import statements as needed so that your project compiles correctly. In Eclipse, you can use this shortcut: press Ctrl+Shift+O in each file showing errors.
        6. +
      6. Fix import statements as needed so that your project compiles correctly. In Android Studio, you can use this shortcut: press Ctrl+Shift+O in each file showing errors.
      7. Modify the sample to create your own application. Remember to copy the Base64 public license key for your application from the Developer Console over to your {@code MainActivity.java}.
      @@ -98,7 +98,6 @@ presented with the welcome screen.
    1. In Android Studio: Create a directory named {@code aidl} under {@code src/main}, add a new package {@code com.android.vending.billing} in this directory, and import the {@code IInAppBillingService.aidl} file into this package.
      2. -
    2. In Eclipse: Import the {@code IInAppBillingService.aidl} file into your {@code /src} directory.
    3. In other dev environments: Create the following directory {@code /src/com/android/vending/billing} and copy the {@code IInAppBillingService.aidl} file into this directory.
      4. diff --git a/docs/html/training/tv/start/start.jd b/docs/html/training/tv/start/start.jd old mode 100644 new mode 100755 index 743b61b1acf7f..0ed6e15950a61 --- a/docs/html/training/tv/start/start.jd +++ b/docs/html/training/tv/start/start.jd @@ -367,7 +367,5 @@ supported by Android TV.

      For more information about using emulators see, Using the Emulator. For more information on deploying apps from Android Studio to virtual devices, see Debugging with Android - Studio. For more information about deploying apps to emulators from Eclipse with ADT, see - Building and Running from Eclipse with - ADT. + Studio.

      diff --git a/docs/html/training/volley/index.jd b/docs/html/training/volley/index.jd old mode 100644 new mode 100755 index 2cefc903cd687..6ee7d4e0ab9f1 --- a/docs/html/training/volley/index.jd +++ b/docs/html/training/volley/index.jd @@ -77,9 +77,9 @@ git clone https://android.googlesource.com/platform/frameworks/volley -
    4. Import the downloaded source into your app project as an Android library project -(as described in -Managing Projects from Eclipse with ADT, if you're using Eclipse) or make a +
    5. Import the downloaded source into your app project as an Android library module +(as described in +Managing Projects from Android Studio, if you're using Android Studio) or make a .jar file.