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

am 5da1430e: am a402fa5f: am f26726b1: am 63d5c3e1: am d16db79e: docs: workflow index [CP]

Browse Source 
* commit '5da1430e7e838e7a36482d605ee3fad121afe0f6':
  docs: workflow index [CP]
This commit is contained in:
Rich Slogar
2014-12-08 19:38:25 +00:00
committed by Android Git Automerger
parent 0622234bcc 5da1430e7e
commit 44176d92e0
1 changed files with 50 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

129
docs/html/tools/workflow/index.jd
View File

@@ -2,14 +2,14 @@ page.title=Introduction
@jd:body @jd:body
<p>To develop apps for Android devices, you use a set of tools that are included in the Android SDK. <p>To develop apps for Android devices, you use a set of tools that are included in the Android SDK.
Once you've downloaded and installed the SDK, you can access these tools right from your Eclipse IDE, Once you've downloaded Android Studio and the Android SDK tools you can access these tools directly.
through the ADT plugin, or from the command line. Developing with Eclipse is the preferred method because You can also access most of the SDK tools from the command line. Developing with Android Studio is the
it can directly invoke the tools that you need while developing applications.</p> preferred method because it can directly invoke the tools that you need while developing applications.</p>
<p>However, you may choose to develop with another IDE or a simple text editor and invoke the <p>However, you may choose to develop with another IDE or a simple text editor and invoke the
tools on the command line or with scripts. This is a less streamlined way to develop because you tools on the command line or with scripts. This is a less streamlined way to develop because you
will sometimes have to call command line tools manually, but you will have access to the same will sometimes have to call command line tools manually, but you will have access to the same
number of features that you would have in Eclipse.</p> number of features that you would have in Android Studio.</p>
<div class="figure" style="width:461px"> <div class="figure" style="width:461px">
<img src="{@docRoot}images/developing/developing_overview.png" <img src="{@docRoot}images/developing/developing_overview.png"
@@ -20,57 +20,65 @@ it can directly invoke the tools that you need while developing applications.</p
</p> </p>
</div> </div>
<p>The basic steps for developing applications (with or without Eclipse) are shown in figure 1. The <h2>App Workflow</h2>
development steps encompass four development phases, which include:</p>
<p>The basic steps for developing applications (with or without Android Studio) are shown in
figure 1. The development steps encompass four development phases, which include:</p>
<ul> <ul>
<li><strong>Setup</strong> <li><strong>Environment Setup</strong>
<p>During this phase you install and set up your development environment. You also create <p>During this phase you install and set up your development environment. You also create
Android Virtual Devices (AVDs) and connect hardware devices on which you can install your Android Virtual Devices (AVDs) and connect hardware devices on which you can install your
applications.</p> applications.</p>
<p>See <a href="{@docRoot}tools/devices/index.html">Managing Virtual Devices</a> <p>See <a href="{@docRoot}tools/workflow/devices/index.html">Managing Virtual Devices</a>
and <a href="{@docRoot}tools/device.html">Using Hardware Devices</a> for more and <a href="{@docRoot}tools/workflow/device.html">Using Hardware Devices</a> for more
information. information.
</li> </li>
<li><strong>Development</strong> <li><strong>Project Setup and Development</strong>
<p>During this phase you set up and develop your Android project, which contains all of the <p>During this phase you set up and develop your Android Studio project and application modules,
source code and resource files for your application. For more information, see which contain all of the source code and resource files for your application. For more
<a href="{@docRoot}tools/projects/index.html">Create an Android project</a>.</p> information, see
<a href="{@docRoot}tools/workflow/projects/index.html">Create an Android project</a>.</p>
</li> </li>
<li><strong>Debugging and Testing</strong> <li><strong>Building, Debugging and Testing</strong>
<p>During this phase you build your project into a debuggable <code>.apk</code> package that you <p>During this phase you build your project into a debuggable <code>.apk</code> package(s)
can install and run on the emulator or an Android-powered device. If you are using Eclipse, that you can install and run on the emulator or an Android-powered device. Android Studio uses
builds are generated each time you project is saved. If you're using another IDE, a build system based on <a href="http://www.gradle.org/" target="_android">Gradle</a>
you can build your project using Ant and install it on a device using that provides flexibility, customized build variants, dependency resolution, and much more.
<a href="{@docRoot}tools/help/adb.html">adb</a>. For more information, see If you're using another IDE, you can build your project using Gradle and install it on a device
<a href="{@docRoot}tools/building/index.html">Build and run your application</a>.</p> using <a href="{@docRoot}tools/help/adb.html">adb</a>. For more information, see
<p>Next, you debug your application using a JDWP-compliant debugger along with the debugging <a href="{@docRoot}tools/workflow/building/index.html">Build and run your application</a>.</p>
and logging tools that are provided with the Android SDK. Eclipse already comes packaged with <p>Next, with Android Studio you debug your application using the
a compatible debugger. For more information see, <a href="{@docRoot}tools/help/monitor.html">Android Debug Monitor</a> and device log messages
<a href="{@docRoot}tools/debugging/index.html">Debug your application with the (<a href="{@docRoot}tools/help/logcat.html">logact</a>) along with the IntelliJ IDEA intelligent
SDK debugging and logging tools</a>.</p> coding features. You can also use a JDWP-compliant debugger along with the debugging and logging
tools that are provided with the Android SDK. For more information see
<a href="{@docRoot}tools/debugging/index.html">Debug your application with the SDK debugging and logging tools</a>.</p>
<p>Last, you test your application using various Android SDK testing tools. For more <p>Last, you test your application using various Android SDK testing tools. For more
information, see <a href="{@docRoot}tools/testing/index.html">Test your application information, see <a href="{@docRoot}tools/testing/index.html">Test your application
with the Testing and Instrumentation framework</a>.</p> with the Testing and Instrumentation framework</a>.</p>
</li> </li>
<li><strong>Publishing</strong> <li><strong>Publishing</strong>
<p>During this phase you configure and build your application for release and distribute your <p>During this phase you configure and build your application for release and distribute your
application to users. For more information, see application to users. For more information, see
<a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing Overview</a>.</p> <a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing
Overview</a>.</p>
</li> </li>
</ul> </ul>
<h2 id="EssentialTools">Essential command line tools</h2> <h2 id="EssentialTools">Essential command line tools</h2>
<p>When developing in IDEs or editors other than Eclipse, be familiar with <p>When developing in IDEs or editors other than Android Studio, be familiar with
all of the tools below, because you will have to run them from the command line.</p> all of the tools below, because you will have to run them from the command line or script.</p>
<dl> <dl>
<dt><a href="{@docRoot}tools/help/android.html">android</a></dt> <dt><a href="{@docRoot}tools/help/android.html">android</a></dt>
<dd>Create and update Android projects and create, move, and delete AVDs.</dd> <dd>Create and update Android projects and create, move, and delete AVDs.</dd>
<dt><a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a></dt> <dt><a href="{@docRoot}tools/help/emulator.html">Android Emulator</a></dt>
<dd>Run your Android applications on an emulated Android platform.</dd> <dd>Run your Android applications on an emulated Android platform.</dd>
@@ -84,9 +92,9 @@ development steps encompass four development phases, which include:</p>
source and third-party tools:</p> source and third-party tools:</p>
<dl> <dl>
<dt>Ant</dt> <dt><a href="http://www.gradle.org/">Gradle</a> </dt>
<dd>To compile and build your Android project into an installable .apk file.</dd> <dd>To compile and build your Android project into an installable .apk file(s).</dd>
<dt>Keytool</dt> <dt>Keytool</dt>
@@ -99,52 +107,15 @@ development steps encompass four development phases, which include:</p>
JDK.</dd> JDK.</dd>
</dl> </dl>
<p>If you are using Eclipse and ADT, tools such as <code>adb</code> and <code>android</code> <p>If you are using Android Studio, tools such as <code>adb</code> and <code>android</code>
are automatically called by Eclipse and ADT so you don't have to manually invoke these tools. are automatically called by Android Studio so you don't have to manually invoke these tools.
You need to be familiar with <code>adb</code>, however, because certain functions are not You need to be familiar with <code>adb</code>, however, because certain functions are not
accessible from accessible from Android Studio, such as the <code>adb</code> shell commands. You might also
Eclipse, such as the <code>adb</code> shell commands. You might also need to call Keytool and need to call Keytool and Jarsigner to sign your applications, but you can set up Android Studio
Jarsigner to to do this automatically as well.</p>
sign your applications, but you can set up Eclipse to do this automatically as well.</p>
<p>For more information on the tools provided with the Android SDK, see the <p>For more information on the tools provided with the Android SDK, see the
<a href="{@docRoot}tools/index.html">Tools</a> section of the documentation.</p> <a href="{@docRoot}tools/help/index.html">Tools</a> section of the documentation.</p>
<h2 id="ThirdParty">Other Third-Party Development Tools</h2>
<p>
The tools described in this section are not developed by the Android SDK team. The Android Dev Guide
does not provide documentation for these tools. Please refer to the linked documents in each
section for documentation.
</p>
<h3 id="IntelliJ">Developing in IntelliJ IDEA</h3>
<div style="float: right">
<img alt="The IntelliJ graphical user interface" height="500px"
src="{@docRoot}images/developing/intellijidea_android_ide.png"/>
</div>
<p>
IntelliJ IDEA is a powerful Java IDE from JetBrains that provides
full-cycle Android development support in both the free Community
Edition and the Ultimate edition.
</p>
<p>
The IDE ensures compatibility with the latest Android SDK and offers a
smart code editor with completion, quick navigation between code and
resources, a graphical debugger, unit testing support using Android
Testing Framework, and the ability to run applications in either the
emulator or a USB-connected device.
</p>
<p>
<strong>Links:</strong>
</p>
<ul>
<li>
<a href="http://www.jetbrains.com/idea">IntelliJ IDEA official website</a>
</li>
<li>
<a href="http://www.jetbrains.com/idea/features/google_android.html">Android support in IntelliJ IDEA</a>
</li>
<li>
<a href="http://wiki.jetbrains.net/intellij/Android">IntelliJ IDEA Android Tutorials</a>
</li>
</ul>