<supports-screen> element, the system
+ of resolution and density. If your application is run on a device whose screen
+ size is not specified in the <supports-screen> element, the system
displays the application in compatibility mode, 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.
The attributes available for defining an application's screen support are:
smallScreen: 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.
- normalScreens: Boolean value that indicates whether - the application is designed to run on devices with normal screens. +normalScreens: 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.
- largeScreens: Boolean value that indicates whether - the application is designed to run on devices with significantly +largeScreens: 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.
- anyDensity: Boolean value that indicates whether +anyDensity: Boolean value that indicates whether the application can accommodate any screen density.resizable: Boolean value that indicates whether @@ -338,21 +338,21 @@ determining the density of the current device screen.
on devices that offer the required features. The element supports these
attributes:
name: The name of the feature required by the application. Currently accepts - "android.hardware.camera" and "android.hardware.camera.autofocus" values, which specify that a +name: 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.glEsVersion: Indicates the minimum version of OpenGL ES required.
-
-
-
-
targetSdkVersion: 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 +targetSdkVersion: 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.
- maxSdkVersion: Indicates the maximum API Level on which an application is +maxSdkVersion: Indicates the maximum API Level on which an application is designed to run. Important: Please read the<uses-sdk>documentation before using this attribute.
@@ -366,13 +366,13 @@ determining the density of the current device screen.
- {@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. -
- {@link android.Manifest.permission#GLOBAL_SEARCH}: Allows the +
- {@link android.Manifest.permission#GLOBAL_SEARCH}: Allows the global search system to access the data of a specified content provider. - -
- {@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}: + +
- {@link android.Manifest.permission#INSTALL_LOCATION_PROVIDER INSTALL_LOCATION_PROVIDER}: Allows an application to install a location provider into the Location Manager.
- READ_HISTORY_BOOKMARKS: @@ -380,13 +380,13 @@ determining the density of the current device screen. and bookmarks.
- 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. -
- {@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE WRITE_EXTERNAL_STORAGE}: +
- {@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.
API differences report
-For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
-the previous version, see the API
+ For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
+the previous version, see the API
Differences Report.Built-in Applications
@@ -438,8 +438,8 @@ built-in applications:
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 language_country/region +languages that are available in the Android {@sdkPlatformVersion} system +image are listed below (with language_country/region locale descriptor).
Localized UI strings match the locales that are accessible +
Localized UI strings match the locales that are accessible through Settings.
Emulator Skins
-The downloadable platform includes a set of emulator skins that you can -use for modeling your application in different screen sizes and resolutions. +
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:
-
diff --git a/docs/html/about/versions/android-4.2.jd b/docs/html/about/versions/android-4.2.jd
old mode 100644
new mode 100755
index 76acb8a013859..f9fb359c23a22
--- a/docs/html/about/versions/android-4.2.jd
+++ b/docs/html/about/versions/android-4.2.jd
@@ -549,7 +549,7 @@ the default signature of the
- The ADT - Plugin for Eclipse offers a layout preview of your XML — - with the XML file opened, select the Layout tab.
- You should also try the
Hierarchy Viewer tool,
for debugging layouts — it reveals layout property values,
diff --git a/docs/html/guide/webapps/debugging.jd b/docs/html/guide/webapps/debugging.jd
old mode 100644
new mode 100755
index 3c95fc265194c..a74797df3bd36
--- a/docs/html/guide/webapps/debugging.jd
+++ b/docs/html/guide/webapps/debugging.jd
@@ -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.
To run logcat and view messages, execute {@code adb logcat} from your Android SDK {@code tools/} directory, or, from DDMS, select -Device > Run logcat. When using the ADT -plugin for Eclipse, you can also view logcat messages by opening the Logcat view, available from -Window > Show View > Other > Android > Logcat.
+Device > Run logcat.See Debugging for more information about
- Internals
- Invoking from the Command Line -
- Invoking from Eclipse
- 64-Bit and 32-Bit Toolchains
- Requirements
- In the Project Explorer pane, right-click your project name. -
- Select Properties. -
- Click C/C++ Build. -
- Under the Builder Settings tab, uncheck Use default build command. -
- In the Build command field, enter the entire build string as if you were typing it on -the command line. -
- Click OK. -
- Develop your app in a Unix shell. On Windows, use Cygwin or the experimental {@code ndk-gdb-py} Python implementation. -
- Use GNU Make 3.81 or higher. -
- If you are building your app from -Eclipse, build it -using version 0.9.7 or higher of the ADT plug-in. +
- Use GNU Make 3.81 or higher.
- In Eclipse: select Window > Android Virtual Device Manager, or click - the AVD Manager icon in the toolbar. -
- In Android Studio: select Tools > Android > AVD Manager, or click the AVD Manager icon in the toolbar. diff --git a/docs/html/tools/help/index.jd b/docs/html/tools/help/index.jd old mode 100644 new mode 100755 index 955cf959e1e2b..f984f2e8ce653 --- a/docs/html/tools/help/index.jd +++ b/docs/html/tools/help/index.jd @@ -133,7 +133,7 @@ files after they have been signed. WYSIWYG editor. It also previews stretched versions of the image, and highlights the area in which content is allowed. -
- Vector Asset Studio +
- Vector Asset Studio
- Helps you add material icons and import Scalable Vector Graphic (SVG) files into your Android Studio project as a drawable resource. @@ -160,8 +160,8 @@ device.
- In Eclipse, open an Android application project. -
- Switch to the DDMS perspective, by selecting Window > Perspectives > - DDMS. -
- In the Devices 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. -
- Click the Systrace icon
at the top of the Devices panel to configure tracing.
- - Set the tracing options and click OK to start the trace. -
- Integrated the SDK Manager
into Android Studio to simplify package and tools access and provide update notifications.
Note: 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.
- Added the
fingercommand in the emulator console to simulate fingerprint diff --git a/docs/html/tools/testing/activity_testing.jd b/docs/html/tools/testing/activity_testing.jd old mode 100644 new mode 100755 index 8baa35de88e8e..6109c060a8019 --- a/docs/html/tools/testing/activity_testing.jd +++ b/docs/html/tools/testing/activity_testing.jd @@ -66,8 +66,8 @@ parent.link=index.htmlSee Also
- - - Testing from Eclipse with ADT + + Building Local Unit Tests
-
@@ -215,9 +215,9 @@ parent.link=index.html
Next Steps
- To learn how to set up and run tests in Eclipse, please refer to -Testing from Eclipse with ADT. - If you're not working in Eclipse, refer to + To learn how to set up and run tests in Android Studio, please refer to +Building Local Unit Tests. + If you're not working in Android Studio, refer to Testing from Other IDEs.
diff --git a/docs/html/training/custom-views/create-view.jd b/docs/html/training/custom-views/create-view.jd old mode 100644 new mode 100755 index d9eebf5ff5dab..1b26ddf936e31 --- a/docs/html/training/custom-views/create-view.jd +++ b/docs/html/training/custom-views/create-view.jd @@ -61,8 +61,7 @@ well-designed class, though, a custom view should: existing view subclasses, such as {@link android.widget.Button}.
-To allow the Android Developer Tools - to interact with your view, at a minimum you must provide a constructor that takes a +
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.
@@ -146,16 +145,10 @@ enable this behavior in your custom view, you must: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.
-Note: 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}.
-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. diff --git a/docs/html/training/custom-views/index.jd b/docs/html/training/custom-views/index.jd old mode 100644 new mode 100755 index 87cd0b0fe8e6d..f732adbcc453c --- a/docs/html/training/custom-views/index.jd +++ b/docs/html/training/custom-views/index.jd @@ -48,7 +48,7 @@ own views that are robust and reusable.
- Creating a View Class
- Create a class that acts like a built-in view, with custom - attributes and support from the ADT layout editor. + attributes and support from the Android Studio layout editor.
- Custom Drawing diff --git a/docs/html/training/design-navigation/wireframing.jd b/docs/html/training/design-navigation/wireframing.jd old mode 100644 new mode 100755 index 1801f91f6c186..201d9e40826f5 --- a/docs/html/training/design-navigation/wireframing.jd +++ b/docs/html/training/design-navigation/wireframing.jd @@ -78,9 +78,6 @@ previous.link=ancestral-temporal.html
- 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.
-Lastly, the XML Layout Editor that comes with the Android Development Tools (ADT) 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.
- -Create Digital Wireframes
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.
diff --git a/docs/html/training/multiple-apks/api.jd b/docs/html/training/multiple-apks/api.jd old mode 100644 new mode 100755 index f43dcaeddc5c5..504b4e3ffb000 --- a/docs/html/training/multiple-apks/api.jd +++ b/docs/html/training/multiple-apks/api.jd @@ -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:
- Setting up -a library project (Eclipse) +href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects +from Android Studio
- Setting up -a library project (Command line) +href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects +from the Command Line
- Setting up -a library project (Eclipse) +href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects +from Android Studio
- Setting up -a library project (Command line) +href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects +from the Command Line
- Setting up -a library project (Eclipse) +href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects +from Android Studio
- Setting up -a library project (Command line) +href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects +from the Command Line
- Setting up -a library project (Eclipse) +href="{@docRoot}sdk/installing/create-project.html#SettingUpLibraryModule">Managing Projects +from Android Studio
- Setting up -a library project (Command line) +href="{@docRoot}tools/projects/projects-cmdline.html#SettingUpLibraryProject">Managing Projects +from the Command Line
- Debugging over Bluetooth
- Learn how to debug your wearable over Bluetooth instead of USB. -
- Learn how to display confirmation animations when users complete actions.
- Exiting Full-Screen Activities
- Learn how to implement the long-press-to-dismiss UI pattern to exit full-screen activities. - \ No newline at end of file + diff --git a/docs/html/training/wearables/watch-faces/index.jd b/docs/html/training/wearables/watch-faces/index.jd old mode 100644 new mode 100755 index a329fda071bc9..aac49d38ce699 --- a/docs/html/training/wearables/watch-faces/index.jd +++ b/docs/html/training/wearables/watch-faces/index.jd @@ -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.
root() function defines.
Note: Although Filterscript support is in the platform, developer -support will be available in ADT and SDK Tools Release 21.0.1.
+support will be available in SDK Tools Release 21.0.1.For a detailed view of all API changes in Android 4.2, see the diff --git a/docs/html/guide/topics/manifest/uses-sdk-element.jd b/docs/html/guide/topics/manifest/uses-sdk-element.jd old mode 100644 new mode 100755 index 642b820d1eb65..a20fde0992f15 --- a/docs/html/guide/topics/manifest/uses-sdk-element.jd +++ b/docs/html/guide/topics/manifest/uses-sdk-element.jd @@ -543,10 +543,7 @@ download other platform versions as necessary.
To access the updater, use the android command-line tool,
located in the <sdk>/tools directory. You can launch the SDK updater by
executing android sdk. 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
-Window > Android SDK
-Manager.
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 diff --git a/docs/html/guide/topics/ui/custom-components.jd b/docs/html/guide/topics/ui/custom-components.jd old mode 100644 new mode 100755 index b146098db713d..b7249c56ea0ba --- a/docs/html/guide/topics/ui/custom-components.jd +++ b/docs/html/guide/topics/ui/custom-components.jd @@ -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.
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
MyEditText in the NoteEditor.java
diff --git a/docs/html/guide/topics/ui/declaring-layout.jd b/docs/html/guide/topics/ui/declaring-layout.jd
old mode 100644
new mode 100755
index d557e7fa6e05e..2d4134d2405fc
--- a/docs/html/guide/topics/ui/declaring-layout.jd
+++ b/docs/html/guide/topics/ui/declaring-layout.jd
@@ -54,9 +54,6 @@ application can create View and ViewGroup objects (and manipulate their properti
-
-
Invoking from Eclipse
-To build from Eclipse, make sure that you have configured it as described in
-Setup. If you
-wish to build using the default ndk-build 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:
-
-
-
-
-Figure 1. Specifying a debug build from within -Eclipse
Debuggable versus Release builds
Use the NDK_DEBUG option and, in certain cases,
diff --git a/docs/html/ndk/guides/ndk-gdb.jd b/docs/html/ndk/guides/ndk-gdb.jd
old mode 100644
new mode 100755
index b15e67e728577..6d9f9332a880b
--- a/docs/html/ndk/guides/ndk-gdb.jd
+++ b/docs/html/ndk/guides/ndk-gdb.jd
@@ -32,10 +32,7 @@ API level that you declare in your {@code AndroidManifest.xml} file does not mat
Usage
To invoke the {@code ndk-gdb} script, change into the application directory or any directory under diff --git a/docs/html/tools/help/android.jd b/docs/html/tools/help/android.jd old mode 100644 new mode 100755 index 0d7d2aaca8c11..fa359e99e559e --- a/docs/html/tools/help/android.jd +++ b/docs/html/tools/help/android.jd @@ -17,7 +17,7 @@ parent.link=index.html "{@docRoot}tools/help/sdk-manager.html">SDK Manager. -If you are using Android Studio or Eclipse, the android tool's features are
+
If you are using Android Studio, the android tool's features are
integrated into the IDE, so you should not need to use this tool directly.
Note: The documentation of options below is not exhaustive diff --git a/docs/html/tools/help/avd-manager.jd b/docs/html/tools/help/avd-manager.jd old mode 100644 new mode 100755 index 20f6253cdbf6e..b3dcad56823d9 --- a/docs/html/tools/help/avd-manager.jd +++ b/docs/html/tools/help/avd-manager.jd @@ -8,9 +8,6 @@ and manage Android Virtual Devices (AVDs), which are required by the
You can launch the AVD Manager in one of the following ways:
-
-
The other platform tools, such as aidl,
aapt, dexdump, and dx, 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.
Note: The Android SDK provides additional shell tools that can
be accessed through adb, such as bmgr and
diff --git a/docs/html/tools/help/layoutopt.jd b/docs/html/tools/help/layoutopt.jd
old mode 100644
new mode 100755
index 1a183263f1b9e..1bc6c64aad4b4
--- a/docs/html/tools/help/layoutopt.jd
+++ b/docs/html/tools/help/layoutopt.jd
@@ -4,13 +4,18 @@ parent.link=index.html
@jd:body
-
Note: The Android layoutopt 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 layoutopt, and detects additional problems.
For more information about using {@code lint}, see Improving Your Code with lint and the lint reference documentation.
+Note: The Android layoutopt 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 layoutopt, and detects additional problems.
For more information about using {@code lint}, see +Improving Your Code with lint and the +lint reference documentation.
layoutopt is a command-line tool that helps you optimize the
layouts and layout hierarchies of your applications.
-
This document is a reference to the available command line options. For more information and sample +
This document is a reference to the available command line options. For more information and +sample output of the tool, see Optimizing layouts with layoutopt.
diff --git a/docs/html/tools/help/monitor.jd b/docs/html/tools/help/monitor.jd old mode 100644 new mode 100755 index 5f7b5ce9a19b0..aafeb919593a2 --- a/docs/html/tools/help/monitor.jd +++ b/docs/html/tools/help/monitor.jd @@ -47,6 +47,4 @@ encapsulates the following tools:Start an Android emulator or connect an Android device via USB cable, and connect Device Monitor to the device by selecting it in the Devices window.
-Note: 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.
+Note: Only one debugger can be connected to your device at a time.
diff --git a/docs/html/tools/help/systrace.jd b/docs/html/tools/help/systrace.jd old mode 100644 new mode 100755 index 2a8e86f47264d..6aefffe94fdfd --- a/docs/html/tools/help/systrace.jd +++ b/docs/html/tools/help/systrace.jd @@ -30,33 +30,12 @@ of these methods.User Interface
-The Systrace tool can be run from the -Android Developer Tools (ADT) in Eclipse, -Android Studio, +
The Systrace tool can be run from +Android Studio or the Android Device Monitor.
To run the Systrace capture user interface:
--
-
Create New APK Projects
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:
@@ -278,7 +278,7 @@ green ≥ blue. Therefore we can effectively collapse the chart to look lik-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. Filters on Google Play 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 diff --git a/docs/html/training/multiple-apks/multiple.jd b/docs/html/training/multiple-apks/multiple.jd old mode 100644 new mode 100755 index ccee397eb6f14..25015643b54b6 --- a/docs/html/training/multiple-apks/multiple.jd +++ b/docs/html/training/multiple-apks/multiple.jd @@ -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.
-Put All Common Code and Resources in a Library Project.
+Put All Common Code and Resources in a Library Project
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:
If you’re converting an existing application to use multiple APK support, @@ -204,7 +204,7 @@ to the library section without screwing anything up.
Create New APK Projects
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:
diff --git a/docs/html/training/multiple-apks/screensize.jd b/docs/html/training/multiple-apks/screensize.jd old mode 100644 new mode 100755 index c7941c4b4e604..a482f673d2f22 --- a/docs/html/training/multiple-apks/screensize.jd +++ b/docs/html/training/multiple-apks/screensize.jd @@ -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 Using Single APK Instead 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 supporting multiple screens, and there’s even a support library 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. -Put All Common Code and Resources in a Library Project.
+Put All Common Code and Resources in a Library Project
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:
Create New APK Projects
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:
@@ -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 < 9 will have xlarge automatically set to false, since that size didn’t exist yet. +target SDK of < 9 will have xlarge automatically set to false, since that size didn’t exist yet. So be explicit! diff --git a/docs/html/training/multiple-apks/texture.jd b/docs/html/training/multiple-apks/texture.jd old mode 100644 new mode 100755 index c49cc9546b26d..3ffd64f05360c --- a/docs/html/training/multiple-apks/texture.jd +++ b/docs/html/training/multiple-apks/texture.jd @@ -73,7 +73,7 @@ application.Chart Your Requirements
- +The Android Developer Guide provides a handy reference of some of common supported textures on the supports-gl-texture page. 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:
If you’re converting an existing application to use multiple APK support, @@ -135,7 +135,7 @@ to the library section without screwing anything up.
Create New APK Projects
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:
@@ -194,7 +194,7 @@ device.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. +
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.
Fortunately this is easily fixed by adding the following to your manifest:
diff --git a/docs/html/training/wearables/apps/index.jd b/docs/html/training/wearables/apps/index.jd old mode 100644 new mode 100755 index e2a71de639c95..da83cfaeacbd3 --- a/docs/html/training/wearables/apps/index.jd +++ b/docs/html/training/wearables/apps/index.jd @@ -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. -Note: 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. -
+Note: 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.
Lessons
-
@@ -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.
Download the Wearable UI library for Eclipse ADT
- -If you are using the ADT plugin for Eclipse, download the -Wearable UI library to -include the Wearable UI library as a dependency in your project.
- -Note: We recommend -Android Studio for Android Wear app -development.
+Note: We recommend using Android Studio for Android Wear development, as +it provides project setup, library inclusion, and packaging conveniences.
diff --git a/docs/html/training/wearables/ui/index.jd b/docs/html/training/wearables/ui/index.jd old mode 100644 new mode 100755 index f82d29ce1162c..c43e16595ce5c --- a/docs/html/training/wearables/ui/index.jd +++ b/docs/html/training/wearables/ui/index.jd @@ -36,9 +36,9 @@ UI patterns: provides classes that help you implement these patterns and create layouts that work on both round and square Android Wear devices. -Note: 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.
+Note: 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.
Lessons
@@ -55,4 +55,4 @@ in ADT. This training assumes you are using Android Studio.Note: We recommend using Android Studio 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.
+href="{@docRoot}sdk/index.html">Android Studio for Android Wear development, as +it provides project setup, library inclusion, and packaging conveniences. This training assumes +you are using Android Studio.Lessons
diff --git a/docs/html/training/wearables/watch-faces/service.jd b/docs/html/training/wearables/watch-faces/service.jd old mode 100644 new mode 100755 index 578e8c01474ad..e94ee56670492 --- a/docs/html/training/wearables/watch-faces/service.jd +++ b/docs/html/training/wearables/watch-faces/service.jd @@ -87,11 +87,9 @@ implement watch faces. Browse the API reference documentation for the Wearable Support Library. -Download the Wearable Support Library for Eclipse ADT
- -If you are using the ADT plugin for Eclipse, download the -Wearable Support Library and -include it as a dependency in your project.
+Note: We recommend using Android Studio for Android Wear development, as +it provides project setup, library inclusion, and packaging conveniences.