Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Android Eclipse ADT update and removals - Batch 04

Browse Source 
b/25192800

Change-Id: Ic3927136a09da29c5931ccaa6ba5ce76ace75096
This commit is contained in:
Joe Fernandez
2015-12-18 09:56:48 -08:00
parent d8ecc59f76
commit 2460971aee
28 changed files with 134 additions and 209 deletions
Download Patch File Download Diff File Expand all files Collapse all files

120
docs/html/about/versions/android-1.6.jd Normal file → Executable file
View File

@@ -63,7 +63,7 @@ SDK</a>.</p>
<h2 id="features">Platform Highlights</h2>
<p>For a list of new user features and platform highlights, see the <a
href="http://developer.android.com/about/versions/android-{@sdkPlatformVersion}-highlights.html">Android
href="http://developer.android.com/about/versions/android-{@sdkPlatformVersion}-highlights.html">Android
{@sdkPlatformVersion} Platform Highlights</a> document.</p>
@@ -125,11 +125,11 @@ function toggleDiv(link) {
<dd>
<p>Requires SDK Tools r6 or higher.</p>
</dd>
<dt>Tools:</dt>
<dt>Tools:</dt>
<dd>
<ul>
<ul>
<li>Adds support for library projects in the Ant build system.</li>
</ul>
</ul>
</dd>
</dl>
</div>
@@ -146,33 +146,33 @@ function toggleDiv(link) {
<p>Requires SDK Tools r4 or higher.</p>
</dd>
<dt>API related:</dt>
<dt>API related:</dt>
<dd>
<ul>
<ul>
<li>Properly exposes CDMA-related constants in <code><a href="{@docRoot}reference/android/telephony/TelephonyManager.html">android.telephony.TelephonyManager</a></code>: <code>DATA_ACTIVITY_DORMANT</code>,
<code>PHONE_TYPE_CDMA</code>, <code>NETWORK_TYPE_CDMA</code>,
<code>NETWORK_TYPE_EVDO_0</code>, <code>NETWORK_TYPE_EVDO_A</code>, and
<code>NETWORK_TYPE_1xRTT</code>.</li>
</ul>
<code>NETWORK_TYPE_1xRTT</code>.</li>
</ul>
</dd>
<dt>System image:</dt>
<dt>System image:</dt>
<dd>
<ul>
<li>Fixes bug so that Bitmap's density is now propagated through Parcelable.</li>
<li>Fixes NinePatchDrawable to properly scale its reported padding for compatibility mode.</li>
<li>Fixes TextView to properly compute styled font metrics based on the screen density.</li>
<ul>
<li>Fixes bug so that Bitmap's density is now propagated through Parcelable.</li>
<li>Fixes NinePatchDrawable to properly scale its reported padding for compatibility mode.</li>
<li>Fixes TextView to properly compute styled font metrics based on the screen density.</li>
<li>Updates kernel to 2.6.29, to match kernel on commercially
available Android-powered devices.</li>
</ul>
available Android-powered devices.</li>
</ul>
</dd>
<dt>Tools:</dt>
<dt>Tools:</dt>
<dd>
<ul>
<ul>
<li>Adds new Ant build system with support for Emma instrumentation projects
(code coverage).</li>
<li>Fixes emulator skins to properly emulate d-pad in landscape mode.</li>
<li>Fixes density rendering in the layout editor in ADT.</li>
</ul>
(code coverage).</li>
<li>Fixes emulator skins to properly emulate d-pad in landscape mode.</li>
<li>Fixes density rendering in the layout editor in ADT.</li>
</ul>
</dd>
</dl>
</div>
@@ -227,8 +227,8 @@ href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API Level
<li><code>OvershootInterpolator</code></li>
</ul>
</li>
<li>New XML attribute <code>android:onClick</code> to specify a View's
<a href="/reference/android/view/View.OnClickListener.html">View.OnClickListener</a>
<li>New XML attribute <code>android:onClick</code> to specify a View's
<a href="/reference/android/view/View.OnClickListener.html">View.OnClickListener</a>
from a layout file.
</li>
<li>New support for dealing with varying screen densities. Density
@@ -236,8 +236,8 @@ information is associated with Bitmap and Canvas for performing the
correct scaling. The framework will automatically scale bitmaps and
nine-patches based on the density the resource was found under and the
density of the screen, etc.
</li><p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>&lt;uses-sdk&gt;</code>
</li><p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>&lt;uses-sdk&gt;</code>
element in your application's manifest. </p>
</ul>
@@ -295,33 +295,33 @@ determining the density of the current device screen.</li>
<h3 id="AndroidManifest">Android Manifest elements</h3>
<ul>
<li>New <a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
&lt;supports-screens>}</a> element lets you specify the device screen sizes that your
<li>New <a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
&lt;supports-screens>}</a> element lets you specify the device screen sizes that your
application is designed and tested to support, where "size" is a combination
of resolution and density. If your application is run on a device whose screen
size is not specified in the <code>&lt;supports-screen&gt;</code> element, the system
of resolution and density. If your application is run on a device whose screen
size is not specified in the <code>&lt;supports-screen&gt;</code> element, the system
displays the application in <em>compatibility mode</em>, which performs best-effort scaling
of the application UI to match the resolution and density of the screen.
of the application UI to match the resolution and density of the screen.
<p>The attributes available for defining an application's screen support are:
<ul>
<li><code>smallScreen</code>: Boolean value that indicates whether the
application is designed to run on devices with small screens.
application is designed to run on devices with small screens.
Examples: QVGA low density; VGA high density.
</li>
<li><code>normalScreens</code>: Boolean value that indicates whether
the application is designed to run on devices with normal screens.
<li><code>normalScreens</code>: Boolean value that indicates whether
the application is designed to run on devices with normal screens.
Examples: WQVGA low density; HVGA medium density; WVGA high density.
</li>
<li><code>largeScreens</code>: Boolean value that indicates whether
the application is designed to run on devices with significantly
<li><code>largeScreens</code>: Boolean value that indicates whether
the application is designed to run on devices with significantly
larger screens, such that special care may be required on
the application's part to make proper use of the screen area.
the application's part to make proper use of the screen area.
Examples: VGA medium density; WVGA medium density.
</li>
<li><code>anyDensity</code>: Boolean value that indicates whether
<li><code>anyDensity</code>: Boolean value that indicates whether
the application can accommodate any screen density.
</li>
<li><code>resizable</code>: Boolean value that indicates whether
@@ -338,21 +338,21 @@ determining the density of the current device screen.</li>
on devices that offer the required features. The element supports these
attributes:
<ul>
<li><code>name</code>: The name of the feature required by the application. Currently accepts
"android.hardware.camera" and "android.hardware.camera.autofocus" values, which specify that a
<li><code>name</code>: The name of the feature required by the application. Currently accepts
"android.hardware.camera" and "android.hardware.camera.autofocus" values, which specify that a
camera and camera autofocus are required, respectively.</li>
<li><code>glEsVersion</code>: Indicates the minimum version of OpenGL ES required.</li>
</ul>
</li>
<li>New attributes for the
<li>New attributes for the
<a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code &lt;uses-sdk>}</a> element:
<ul>
<li><code>targetSdkVersion</code>: Indicates the API Level that the application is targeting.
It is able to run on older versions (down to minSdkVersion), but was explicitly tested to
work with the version specified here. Specifying this version allows the platform to
disable compatibility code that is not required or enable newer features that are not
<li><code>targetSdkVersion</code>: Indicates the API Level that the application is targeting.
It is able to run on older versions (down to minSdkVersion), but was explicitly tested to
work with the version specified here. Specifying this version allows the platform to
disable compatibility code that is not required or enable newer features that are not
available to older applications. </li>
<li><code>maxSdkVersion</code>: Indicates the maximum API Level on which an application is
<li><code>maxSdkVersion</code>: Indicates the maximum API Level on which an application is
designed to run. <strong>Important:</strong> Please read the <a
href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code>&lt;uses-sdk&gt;</code></a>
documentation before using this attribute. </li>
@@ -366,13 +366,13 @@ determining the density of the current device screen.</li>
<ul>
<li>{@link android.Manifest.permission#CHANGE_WIFI_MULTICAST_STATE
CHANGE_WIFI_MULTICAST_STATE}: Allows applications to enter Wi-Fi
CHANGE_WIFI_MULTICAST_STATE}: Allows applications to enter Wi-Fi
Multicast mode.
</li>
<li>{@link android.Manifest.permission#GLOBAL_SEARCH}: Allows the
<li>{@link android.Manifest.permission#GLOBAL_SEARCH}: Allows the
global search system to access the data of a specified content provider.
</li>
<li>{@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}:
</li>
<li>{@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}:
Allows an application to install a location provider into the Location Manager.
</li>
<li>READ_HISTORY_BOOKMARKS:
@@ -380,13 +380,13 @@ determining the density of the current device screen.</li>
and bookmarks.
</li>
<li>WRITE_HISTORY_BOOKMARKS:
Allows an application to write (but not read) the user's browsing history
Allows an application to write (but not read) the user's browsing history
and bookmarks.
</li>
<li>{@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE WRITE_EXTERNAL_STORAGE}:
<li>{@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE WRITE_EXTERNAL_STORAGE}:
Allows an application to write to external storage. Applications using API Level 3
and lower will be implicitly granted this permission (and this will be visible to
the user); Applications using API Level 4 or higher must explicitly request this
and lower will be implicitly granted this permission (and this will be visible to
the user); Applications using API Level 4 or higher must explicitly request this
permission.
</li>
</ul>
@@ -394,8 +394,8 @@ determining the density of the current device screen.</li>
<h3 id="api-diff">API differences report</h3>
<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API
<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API
Differences Report</a>.</p>
<h2 id="apps">Built-in Applications</h2>
@@ -438,8 +438,8 @@ built-in applications:</p>
<p>The system image included in the downloadable platform provides a variety of
built-in locales. In some cases, region-specific strings are available for the
locales. In other cases, a default version of the language is used. The
languages that are available in the Android {@sdkPlatformVersion} system
image are listed below (with <em>language</em>_<em>country/region</em>
languages that are available in the Android {@sdkPlatformVersion} system
image are listed below (with <em>language</em>_<em>country/region</em>
locale descriptor).</p>
<table style="border:0;margin-bottom:0;padding-bottom:0;">
@@ -479,13 +479,13 @@ locale descriptor).</p>
</tr>
</table>
<p>Localized UI strings match the locales that are accessible
<p>Localized UI strings match the locales that are accessible
through Settings.</p>
<h2 id="skins">Emulator Skins</h2>
<p>The downloadable platform includes a set of emulator skins that you can
use for modeling your application in different screen sizes and resolutions.
<p>The downloadable platform includes a set of emulator skins that you can
use for modeling your application in different screen sizes and resolutions.
The emulator skins are: </p>
<ul>

2
docs/html/about/versions/android-4.2.jd Normal file → Executable file
View File

@@ -549,7 +549,7 @@ the default signature of the <code>root()</code> function defines.</p>
</dl>
<p class="note"><strong>Note:</strong> Although Filterscript support is in the platform, developer
support will be available in ADT and SDK Tools Release 21.0.1. </p>
support will be available in SDK Tools Release 21.0.1. </p>
<p>For a detailed view of all API changes in Android 4.2, see the

5
docs/html/guide/topics/manifest/uses-sdk-element.jd Normal file → Executable file
View File

@@ -543,10 +543,7 @@ download other platform versions as necessary. </p>
<p>To access the updater, use the <code>android</code> command-line tool,
located in the &lt;sdk&gt;/tools directory. You can launch the SDK updater by
executing <code>android sdk</code>. You can
also simply double-click the android.bat (Windows) or android (OS X/Linux) file.
In ADT, you can also access the updater by selecting
<strong>Window</strong>&nbsp;>&nbsp;<strong>Android SDK
Manager</strong>.</p>
also simply double-click the android.bat (Windows) or android (OS X/Linux) file.</p>
<p>To run your application against different platform versions in the emulator,
create an AVD for each platform version that you want to test. For more

2
docs/html/guide/topics/ui/custom-components.jd Normal file → Executable file
View File

@@ -451,7 +451,7 @@ them is extending an EditText View to make a lined notepad. This is not a
perfect example, and the APIs for doing this might change from this early
preview, but it does demonstrate the principles.</p>
<p>If you haven't done so already, import the
NotePad sample into Eclipse (or
NotePad sample into Android Studio (or
just look at the source using the link provided). In particular look at the definition of
<code>MyEditText</code> in the <a
href="{@docRoot}resources/samples/NotePad/src/com/example/android/notepad/NoteEditor.html">NoteEditor.java</a>

3
docs/html/guide/topics/ui/declaring-layout.jd Normal file → Executable file
View File

@@ -54,9 +54,6 @@ application can create View and ViewGroup objects (and manipulate their properti
<div class="sidebox-wrapper">
<div class="sidebox">
<ul>
<li>The <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT
Plugin for Eclipse</a> offers a layout preview of your XML &mdash;
with the XML file opened, select the <strong>Layout</strong> tab.</li>
<li>You should also try the
<a href="{@docRoot}tools/debugging/debugging-ui.html#hierarchyViewer">Hierarchy Viewer</a> tool,
for debugging layouts &mdash; it reveals layout property values,

4
docs/html/guide/webapps/debugging.jd Normal file → Executable file
View File

@@ -53,9 +53,7 @@ the device throws an error, as well as log messages written from your applicatio
those written using JavaScript {@code console} APIs.</p>
<p>To run logcat and view messages, execute
{@code adb logcat} from your Android SDK {@code tools/} directory, or, from DDMS, select
<strong>Device > Run logcat</strong>. When using the <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT
plugin for Eclipse</a>, you can also view logcat messages by opening the Logcat view, available from
<strong>Window > Show View > Other > Android > Logcat</strong>.</p>
<strong>Device > Run logcat</strong>.</p>
<p>See <a href="{@docRoot}tools/debugging/debugging-log.html">Debugging</a>
for more information about <codelogcat</code>.</p>
</div>

24
docs/html/ndk/guides/ndk-build.jd Normal file → Executable file
View File

@@ -8,7 +8,6 @@ page.title=ndk-build
<ol>
<li><a href="#int">Internals</a></li>
<li><a href="#ifc">Invoking from the Command Line</a></li>
<li><a href="#ife">Invoking from Eclipse</a></li>
<li><a href="#6432">64-Bit and 32-Bit Toolchains</a></li>
<li><a href="#req">Requirements</a></li>
</ol>
@@ -85,29 +84,6 @@ $ ndk-build clean
don't want to {@code cd} to it in your terminal.</dd>
</dl>
<h2 id="ife">Invoking from Eclipse</h2>
<p>To build from Eclipse, make sure that you have configured it as described in
<a href="{@docRoot}ndk/guides/setup.html#configure">Setup</a>. If you
wish to build using the default <code>ndk-build</code> command, with no
options, you can just build your project just as you would any Android project.
To get Eclipse to add any of the options described above, follow these steps:</p>
<ol type="1">
<li>In the <em>Project Explorer</em> pane, right-click your project name.</li>
<li>Select <strong>Properties</strong>.</li>
<li>Click <strong>C/C++ Build</strong>.</li>
<li>Under the <em>Builder Settings</em> tab, uncheck <strong>Use default build command</strong>.</li>
<li>In the <em>Build command</em> field, enter the entire build string as if you were typing it on
the command line.</li>
<li>Click <strong>OK</strong>.</li>
</ol>
Figure 1 shows an example of an entered string.<br>
<br>
<img src="./images/NDK_build_string.png"
srcset="./images/NDK_build_string@2x.png 2x"
alt="enter the build string next to 'Build command'"
height="152" width="501">
<p style="clear:both"><b>Figure 1.</b> Specifying a debug build from within
Eclipse</p>
<p><a class="anchor" id="dvr"></a> </p>
<h3>Debuggable versus Release builds</h3>
<p>Use the <code>NDK_DEBUG</code> option and, in certain cases,

5
docs/html/ndk/guides/ndk-gdb.jd Normal file → Executable file
View File

@@ -32,10 +32,7 @@ API level that you declare in your {@code AndroidManifest.xml} file does not mat
<li>Develop your app in a Unix shell. On Windows, use <a href="https://www.cygwin.com/">Cygwin</a>
or the experimental {@code ndk-gdb-py} <a href="https://www.python.org/">Python</a>
implementation.</li>
<li>Use GNU Make 3.81 or higher.</li>
<li>If you are building your app from
<a href="{@docRoot}sdk/installing/installing-adt.html">Eclipse</a>, build it
using version 0.9.7 or higher of the ADT plug-in.</li>
<li>Use GNU Make 3.81 or higher.</li></ul>
<h2 id="use">Usage</h2>
To invoke the {@code ndk-gdb} script, change into the application directory or any directory under

2
docs/html/tools/help/android.jd Normal file → Executable file
View File

@@ -17,7 +17,7 @@ parent.link=index.html
"{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>.</li>
</ul>
<p>If you are using Android Studio or Eclipse, the <code>android</code> tool's features are
<p>If you are using Android Studio, the <code>android</code> tool's features are
integrated into the IDE, so you should not need to use this tool directly. </p>
<p class="note"><strong>Note:</strong> The documentation of options below is not exhaustive

3
docs/html/tools/help/avd-manager.jd Normal file → Executable file
View File

@@ -8,9 +8,6 @@ and manage Android Virtual Devices (AVDs), which are required by the
<p>You can launch the AVD Manager in one of the following ways:</p>
<ul>
<li>In Eclipse: select <strong>Window &gt; Android Virtual Device Manager</strong>, or click
the AVD Manager icon in the toolbar.</li>
<li>In Android Studio: select <strong>Tools &gt; Android &gt; AVD Manager</strong>, or click
the AVD Manager icon in the toolbar.</li>

6
docs/html/tools/help/index.jd Normal file → Executable file
View File

@@ -133,7 +133,7 @@ files after they have been signed.</dd>
WYSIWYG editor. It also previews stretched versions of the image, and highlights the area in which
content is allowed.</dd>
<dt><a href="{@docRoot}tools/help/vector-asset-studio.html">Vector Asset Studio</a></dt>
<dt><a href="{@docRoot}tools/help/vector-asset-studio.html">Vector Asset Studio</a></dt>
<dd>Helps you add material icons and import Scalable Vector Graphic (SVG) files into your
Android Studio project as a drawable resource.</dd>
@@ -160,8 +160,8 @@ device.</p>
<p>The other platform tools, such as <a href="{@docRoot}guide/components/aidl.html">aidl</a>,
<code>aapt</code>, <code>dexdump</code>, and <code>dx</code>, are typically called by the Android
build tools or Android Development Tools (ADT), so you rarely need to invoke these tools directly.
As a general rule, you should rely on the build tools or the ADT plugin to call them as needed.</p>
build tools, so you rarely need to invoke these tools directly.
As a general rule, you should rely on the build tools to call them as needed.</p>
<p class="note"><strong>Note:</strong> The Android SDK provides additional shell tools that can
be accessed through <code>adb</code>, such as <a href="{@docRoot}tools/help/bmgr.html">bmgr</a> and

11
docs/html/tools/help/layoutopt.jd Normal file → Executable file
View File

@@ -4,13 +4,18 @@ parent.link=index.html
@jd:body
<p class="note"><strong>Note: </strong>The Android <code>layoutopt</code> tool has been replaced by the {@code lint} tool beginning in ADT and SDK Tools revision 16. The {@code lint} tool reports UI layout performance issues in a similar way as <code>layoutopt</code>, and detects additional problems.</p>
<p>For more information about using {@code lint}, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a> and the <a href="{@docRoot}tools/help/lint.html">lint reference documentation</a>.</p>
<p class="note"><strong>Note: </strong>The Android <code>layoutopt</code> tool has been replaced
by the {@code lint} tool beginning in SDK Tools revision 16. The {@code lint} tool reports UI
layout performance issues in a similar way as <code>layoutopt</code>, and detects additional problems.</p>
<p>For more information about using {@code lint}, see
<a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a> and the
<a href="{@docRoot}tools/help/lint.html">lint reference documentation</a>.</p>
<p><code>layoutopt</code> is a command-line tool that helps you optimize the
layouts and layout hierarchies of your applications.<p>
<p>This document is a reference to the available command line options. For more information and sample
<p>This document is a reference to the available command line options. For more information and
sample
output of the tool, see <a
href="{@docRoot}tools/debugging/debugging-ui.html#layoutopt">Optimizing layouts with
layoutopt</a>.</p>

4
docs/html/tools/help/monitor.jd Normal file → Executable file
View File

@@ -47,6 +47,4 @@ encapsulates the following tools:</p>
<p>Start an Android emulator or connect an Android device via USB cable, and connect Device
Monitor to the device by selecting it in the <strong>Devices</strong> window.</p>
<p class="note"><strong>Note:</strong> Only one debugger can be connected to your device at a time.
If you're using ADT, you may need to close the debugging tool before launching the Device Monitor
in order for the device to be fully debuggable.</p>
<p class="note"><strong>Note:</strong> Only one debugger can be connected to your device at a time.</p>

25
docs/html/tools/help/systrace.jd Normal file → Executable file
View File

@@ -30,33 +30,12 @@ of these methods.</p>
<h2 id="gui">User Interface</h2>
<p>The Systrace tool can be run from the
<a href="{@docRoot}tools/help/adt.html">Android Developer Tools</a> (ADT) in Eclipse,
<a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>,
<p>The Systrace tool can be run from
<a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>
or the Android <a href="{@docRoot}tools/help/monitor.html">Device Monitor</a>.
<p>To run the Systrace capture user interface:</p>
<div class="toggle-content closed">
<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)">
<img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt=""
/>Using Eclipse</a></p>
<div class="toggle-content-toggleme">
<ol>
<li>In Eclipse, open an Android application project.</li>
<li>Switch to the DDMS perspective, by selecting <strong>Window &gt; Perspectives &gt;
DDMS</strong>.</li>
<li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no
devices are listed, make sure your device is connected via USB cable and that debugging is
enabled on the device.</li>
<li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png"
style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li>
<li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
</ol>
</div>
</div>
<div class="toggle-content closed">
<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)">
<img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt=""

2
docs/html/tools/revisions/studio.jd Normal file → Executable file
View File

@@ -254,7 +254,7 @@ Android Studio, as denoted by revision number. </p>
<li>Integrated the <a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>
into Android Studio to simplify package and tools access and provide update notifications.
<p class="note"><strong>Note:</strong> The standalone SDK Manager is still available from
the command line, but is recommended for use with only Eclipse ADT and standalone SDK
the command line, but is recommended for use only with standalone SDK
installations. </p> </li>
<li>Added the <code>finger</code> command in the emulator console to simulate
<a href="{@docRoot}tools/studio/studio-features.html#finger-print">fingerprint</a>

10
docs/html/tools/testing/activity_testing.jd Normal file → Executable file
View File

@@ -66,8 +66,8 @@ parent.link=index.html
<h2>See Also</h2>
<ol>
<li>
<a href="{@docRoot}tools/testing/testing_eclipse.html">
Testing from Eclipse with ADT</a>
<a href="{@docRoot}training/testing/unit-testing/local-unit-tests.html">
Building Local Unit Tests</a>
</li>
<li>
<a href="{@docRoot}tools/testing/testing_otheride.html">
@@ -215,9 +215,9 @@ parent.link=index.html
</ul>
<h2 id="NextSteps">Next Steps</h2>
<p>
To learn how to set up and run tests in Eclipse, please refer to
<a href="{@docRoot}tools/testing/testing_eclipse.html">Testing from Eclipse with ADT</a>.
If you're not working in Eclipse, refer to
To learn how to set up and run tests in Android Studio, please refer to
<a href="{@docRoot}training/testing/unit-testing/local-unit-tests.html">Building Local Unit Tests</a>.
If you're not working in Android Studio, refer to
<a href="{@docRoot}tools/testing/testing_otheride.html">Testing from Other IDEs</a>.
</p>
<p>

11
docs/html/training/custom-views/create-view.jd Normal file → Executable file
View File

@@ -61,8 +61,7 @@ well-designed class, though, a custom view should:
existing view
subclasses, such as {@link android.widget.Button}.</p>
<p>To allow the <a href="{@docRoot}guide/developing/tools/adt.html">Android Developer Tools
</a> to interact with your view, at a minimum you must provide a constructor that takes a
<p>To allow Android Studio to interact with your view, at a minimum you must provide a constructor that takes a
{@link android.content.Context} and an {@link android.util.AttributeSet} object as parameters.
This constructor allows the layout editor to create and edit an instance of your view.</p>
@@ -146,16 +145,10 @@ enable this behavior in your custom view, you must:
<p>In order to avoid having to repeat the long namespace URI, the sample uses an {@code
xmlns} directive. This
directive assigns the alias {@code custom} to the namespace {@code
http://schemas.android.com/apk/res-auto}. You can choose any alias
http://schemas.android.com/apk/res/com.example.customviews}. You can choose any alias
you want for your
namespace.</p>
<p class="note"><strong>Note:</strong> If you are not using Gradle to build
your project, your {@code xlmns} URI cannot include {@code res-auto}.
Instead, the URI must contain the fully qualified name of your project. In
this example, the non-Gradle URI would be:
{@code http://schemas.android.com/apk/res/com.example.customviews}.</p>
<p>Notice the name of the XML tag that adds the custom view to the layout. It is the fully
qualified name of the
custom view class. If your view class is an inner class, you must further qualify it with the name of the view's outer class.

2
docs/html/training/custom-views/index.jd Normal file → Executable file
View File

@@ -48,7 +48,7 @@ own views that are robust and reusable.</p>
<dl>
<dt><b><a href="create-view.html">Creating a View Class</a></b></dt>
<dd>Create a class that acts like a built-in view, with custom
attributes and support from the <a href="http://developer.android.com/sdk/eclipse-adt.html">ADT</a> layout editor.
attributes and support from the <a href="http://developer.android.com/sdk/installing/studio-layout.html">Android Studio</a> layout editor.
</dd>
<dt><b><a href="custom-drawing.html">Custom Drawing</a></b></dt>

3
docs/html/training/design-navigation/wireframing.jd Normal file → Executable file
View File

@@ -78,9 +78,6 @@ previous.link=ancestral-temporal.html
<li>What's the learning curve? Professional vector illustration tools may have a steep learning curve, while tools designed for wireframing may offer a smaller set of features that are more relevant to the task.</li>
</ul>
<p>Lastly, the XML Layout Editor that comes with the <a href="{@docRoot}tools/help/adt.html">Android Development Tools (ADT)</a> plugin for Eclipse can often be used for prototyping. However, you should be careful to focus more on the high-level layout and less on visual design details at this point.</p>
<h2 id="wireframe-digital">Create Digital Wireframes</h2>
<p>After sketching out layouts on paper and choosing a digital wireframing tool that works for you, you can create the digital wireframes that will serve as the starting point for your application's visual design. Below are example wireframes for our news application, corresponding one-to-one with our screen maps from earlier in this lesson.</p>

12
docs/html/training/multiple-apks/api.jd Normal file → Executable file
View File

@@ -153,11 +153,11 @@ include library projects are beyond the scope of this lesson, you can get up to
their creation at the following links:</p>
<ul>
<li><a
href="{@docRoot}tools/projects/projects-eclipse.html#SettingUpLibraryProject">Setting up
a library project (Eclipse)</a></li>
href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects
from Android Studio</a></li>
<li><a
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Setting up
a library project (Command line)</a></li>
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects
from the Command Line</a></li>
</ul>
@@ -176,7 +176,7 @@ to the library section without screwing anything up.</p>
<h2 id="CreateAPKs">Create New APK Projects</h2>
<p>There should be a separate Android project for each APK you’re going to release. For easy
organization, place the library project and all related APK projects under the same parent folder.
organization, place the library project and all related APK projects under the same parent folder.
Also remember that each APK needs to have the same package name, although they don’t necessarily
need to share the package name with the library. If you were to have 3 APKs following the scheme
described earlier, your root directory might look like this:</p>
@@ -278,7 +278,7 @@ green &#8805; blue. Therefore we can effectively collapse the chart to look lik
</table>
<p>
Now, let’s further assume that the Red APK has some requirement on it that the other two don’t.
Now, let’s further assume that the Red APK has some requirement on it that the other two don’t.
<a href="{@docRoot}google/play/filters.html">Filters on Google Play</a> page of
the Android Developer guide has a whole list of possible culprits. For the
sake of example, let’s assume that red requires a front-facing camera. In fact, the entire point of

12
docs/html/training/multiple-apks/multiple.jd Normal file → Executable file
View File

@@ -169,7 +169,7 @@ boot, you also have swanky codenames for each one, since "Have we tested red on
easier to ask your cubie than "Have we tested the 3-to-10 xlarge APK against the Xoom?" Print this
chart out and hand it to every person working on your codebase. Life just got a lot easier.</p>
<h2 id="CreateLibrary">Put All Common Code and Resources in a Library Project.</h2>
<h2 id="CreateLibrary">Put All Common Code and Resources in a Library Project</h2>
<p>Whether you’re modifying an existing Android application or starting one from scratch, this is
the first thing that you should do to the codebase, and by the far the most important. Everything
@@ -182,11 +182,11 @@ include library projects are beyond the scope of this lesson, you can get up to
their creation at the following links:</p>
<ul>
<li><a
href="{@docRoot}tools/projects/projects-eclipse.html#SettingUpLibraryProject">Setting up
a library project (Eclipse)</a></li>
href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects
from Android Studio</a></li>
<li><a
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Setting up
a library project (Command line)</a></li>
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects
from the Command Line</a></li>
</ul>
<p>If you’re converting an existing application to use multiple APK support,
@@ -204,7 +204,7 @@ to the library section without screwing anything up.</p>
<h2 id="CreateAPKs">Create New APK Projects</h2>
<p>There should be a separate Android project for each APK you’re going to release. For easy
organization, place the library project and all related APK projects under the same parent folder.
organization, place the library project and all related APK projects under the same parent folder.
Also remember that each APK needs to have the same package name, although they don’t necessarily
need to share the package name with the library. If you were to have 3 APKs following the scheme
described earlier, your root directory might look like this:</p>

16
docs/html/training/multiple-apks/screensize.jd Normal file → Executable file
View File

@@ -58,7 +58,7 @@ without sacrificing compatibility or usability on the smaller screens. It may s
though multiple APK support is the best solution, but this often isn’t the case. The <a
href="{@docRoot}google/play/publishing/multiple-apks.html#ApiLevelOptions">Using Single APK
Instead</a> section of the multiple APK developer guide includes some useful information on how to
accomplish this with a single APK, including use of our support library. You should also read the
accomplish this with a single APK, including use of our support library. You should also read the
guide to <a href="{@docRoot}guide/practices/screens_support.html">supporting multiple screens</a>,
and there’s even a <a
href="http://android-developers.blogspot.com/2011/03/fragments-for-all.html">support library</a> you
@@ -118,7 +118,7 @@ everything else". Coloring in the chart also makes intra-team communication eas
now simply refer to each APK as "blue", "green", or "red", no matter how many different screen types
it covers.</p>
<h2 id="CreateLibrary">Put All Common Code and Resources in a Library Project.</h2>
<h2 id="CreateLibrary">Put All Common Code and Resources in a Library Project</h2>
<p>Whether you’re modifying an existing Android application or starting one from scratch, this is
the first thing that you should do to the codebase, and by the far the most important. Everything
that goes into the library project only needs to be updated once (think language-localized strings,
@@ -130,11 +130,11 @@ include library projects are beyond the scope of this lesson, you can get up to
their creation at the following links:</p>
<ul>
<li><a
href="{@docRoot}tools/projects/projects-eclipse.html#SettingUpLibraryProject">Setting up
a library project (Eclipse)</a></li>
href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects
from Android Studio</a></li>
<li><a
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Setting up
a library project (Command line)</a></li>
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects
from the Command Line</a></li>
</ul>
@@ -156,7 +156,7 @@ to the library section without screwing anything up.</p>
<h2 id="CreateAPKs">Create New APK Projects</h2>
<p>There should be a separate Android project for each APK you’re going to release. For easy
organization, place the library project and all related APK projects under the same parent folder.
organization, place the library project and all related APK projects under the same parent folder.
Also remember that each APK needs to have the same package name, although they don’t necessarily
need to share the package name with the library. If you were to have 3 APKs following the scheme
described earlier, your root directory might look like this:</p>
@@ -295,7 +295,7 @@ makes things needlessly complicated, and increases the opportunity for errors.
Also note that instead of taking advantage of the default values (small and
normal are always true by default), the manifests explicitly set the value for
each screen size. This can save you headaches down the line. For instance, a manifest with a
target SDK of &lt; 9 will have xlarge automatically set to false, since that size didn’t exist yet.
target SDK of &lt; 9 will have xlarge automatically set to false, since that size didn’t exist yet.
So be explicit!
</p>

16
docs/html/training/multiple-apks/texture.jd Normal file → Executable file
View File

@@ -73,7 +73,7 @@ application.</p>
<h2 id="ChartReqs">Chart Your Requirements</h2>
<p>The Android Developer Guide provides a handy reference of some of common supported textures on
the <a href="{@docRoot}guide/topics/manifest/supports-gl-texture-element.html">supports-gl-texture
page</a>. This page also contains some hints as to which phones (or families of phones) support
@@ -113,11 +113,11 @@ include library projects are beyond the scope of this lesson, you can get up to
their creation at the following links:</p>
<ul>
<li><a
href="{@docRoot}tools/projects/projects-eclipse.html#SettingUpLibraryProject">Setting up
a library project (Eclipse)</a></li>
href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects
from Android Studio</a></li>
<li><a
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Setting up
a library project (Command line)</a></li>
href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects
from the Command Line</a></li>
</ul>
<p>If you’re converting an existing application to use multiple APK support,
@@ -135,7 +135,7 @@ to the library section without screwing anything up.</p>
<h2 id="CreateAPKs">Create New APK Projects</h2>
<p>There should be a separate Android project for each APK you’re going to release. For easy
organization, place the library project and all related APK projects under the same parent folder.
organization, place the library project and all related APK projects under the same parent folder.
Also remember that each APK needs to have the same package name, although they don’t necessarily
need to share the package name with the library. If you were to have 3 APKs following the scheme
described earlier, your root directory might look like this:</p>
@@ -194,7 +194,7 @@ device.</p>
<tr>
<td class="blueCell">ETC1</td>
<td class="blueCell">ETC1</td>
<td class="blueCell">ETC1</td>
<td class="blueCell">ETC1</td>
</tr>
<tr>
<td></td>
@@ -290,7 +290,7 @@ densities: '120' '160' '240'
supports-screens and compatible-screens, and that you don’t have unintended "uses-feature" values
that were added as a result of permissions you set in the manifest. In the example above, the APK
will be invisible to most, if not all devices.</p>
<p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.telephony was implicitly added. Since most (if not all) xlarge devices are tablets without telephony hardware in them, Google Play will filter out this APK in these cases, until future devices come along which are both large enough to report as xlarge screen size, and possess telephony hardware.
<p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.telephony was implicitly added. Since most (if not all) xlarge devices are tablets without telephony hardware in them, Google Play will filter out this APK in these cases, until future devices come along which are both large enough to report as xlarge screen size, and possess telephony hardware.
</p>
<p>Fortunately this is easily fixed by adding the following to your manifest:</p>
<pre>

9
docs/html/training/wearables/apps/index.jd Normal file → Executable file
View File

@@ -66,10 +66,9 @@ activity, the Wear home screen is displayed instead of your activity in ambient
need to show persistent content on versions prior to Android 5.1, create a notification in the
context stream instead.</p>
<p class="note"><b>Note:</b> We recommend using Android Studio for Android Wear development
as it provides project setup, library inclusion, and packaging conveniences that aren't available
in ADT. The rest of this training assumes you're using Android Studio.
</p>
<p class="note"><b>Note:</b> We recommend using Android Studio for Android Wear development,
as it provides project setup, library inclusion, and packaging conveniences. The rest of this
training assumes you're using Android Studio.</p>
<h2>Lessons</h2>
<dl>
@@ -92,4 +91,4 @@ in ADT. The rest of this training assumes you're using Android Studio.
users install the companion handheld app from the Google Play store.</dd>
<dt><a href="{@docRoot}training/wearables/apps/bt-debugging.html">Debugging over Bluetooth</a></dt>
<dd>Learn how to debug your wearable over Bluetooth instead of USB.</dd>
</dl>
</dl>

12
docs/html/training/wearables/apps/layouts.jd Normal file → Executable file
View File

@@ -199,12 +199,6 @@ dependencies {
<a href="{@docRoot}reference/android/support/wearable/view/package-summary.html">Wear API
reference documentation</a> for the classes above.</p>
<h3 id="UiLibEclipse">Download the Wearable UI library for Eclipse ADT</h3>
<p>If you are using the ADT plugin for Eclipse, download the
<a href="{@docRoot}shareables/training/wearable-support-lib.zip">Wearable UI library</a> to
include the Wearable UI library as a dependency in your project.</p>
<p class="note"><strong>Note:</strong> We recommend
<a href="{@docRoot}sdk/index.html">Android Studio</a> for Android Wear app
development.</p>
<p class="note"><strong>Note:</strong> We recommend using <a
href="{@docRoot}sdk/index.html">Android Studio</a> for Android Wear development, as
it provides project setup, library inclusion, and packaging conveniences.</p>

8
docs/html/training/wearables/ui/index.jd Normal file → Executable file
View File

@@ -36,9 +36,9 @@ UI patterns:</p>
provides classes that help you implement these patterns and create layouts that work on
both round and square Android Wear devices.</p>
<p class="note"><b>Note:</b> We recommend using Android Studio for Android Wear development
as it provides project setup, library inclusion, and packaging conveniences that aren't available
in ADT. This training assumes you are using Android Studio.</p>
<p class="note"><b>Note:</b> We recommend using Android Studio for Android Wear development,
as it provides project setup, library inclusion, and packaging conveniences. This training assumes
you are using Android Studio.</p>
<h2>Lessons</h2>
@@ -55,4 +55,4 @@ in ADT. This training assumes you are using Android Studio.</p>
<dd>Learn how to display confirmation animations when users complete actions.</dd>
<dt><a href="{@docRoot}training/wearables/ui/exit.html">Exiting Full-Screen Activities</a></dt>
<dd>Learn how to implement the long-press-to-dismiss UI pattern to exit full-screen activities.</dd>
</dl>
</dl>

6
docs/html/training/wearables/watch-faces/index.jd Normal file → Executable file
View File

@@ -45,9 +45,9 @@ app. This class also covers design considerations and implementation tips to ens
designs integrate with system UI elements and are power-efficient.</p>
<p class="note"><strong>Note:</strong> We recommend using <a
href="{@docRoot}sdk/index.html">Android Studio</a> for Android Wear development as
it provides project setup, library inclusion, and packaging conveniences that aren't available
in the Eclipse Android Developer Tools. This training assumes you are using Android Studio.</p>
href="{@docRoot}sdk/index.html">Android Studio</a> for Android Wear development, as
it provides project setup, library inclusion, and packaging conveniences. This training assumes
you are using Android Studio.</p>
<h2>Lessons</h2>

8
docs/html/training/wearables/watch-faces/service.jd Normal file → Executable file
View File

@@ -87,11 +87,9 @@ implement watch faces. Browse the
<a href="{@docRoot}reference/android/support/wearable/watchface/package-summary.html">API reference
documentation</a> for the Wearable Support Library.</p>
<h3 id="LibEclipse">Download the Wearable Support Library for Eclipse ADT</h3>
<p>If you are using the ADT plugin for Eclipse, download the
<a href="{@docRoot}shareables/training/wearable-support-lib.zip">Wearable Support Library</a> and
include it as a dependency in your project.</p>
<p class="note"><strong>Note:</strong> We recommend using <a
href="{@docRoot}sdk/index.html">Android Studio</a> for Android Wear development, as
it provides project setup, library inclusion, and packaging conveniences.</p>
<h3 id="Permissions">Declare Permissions</h3>