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

auto import from //depot/cupcake/@132589

Browse Source
This commit is contained in:
The Android Open Source Project
2009-03-03 14:04:24 -08:00
parent 3dec7d563a
commit 076357b856
310 changed files with 4072 additions and 18131 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
docs/html/app.yaml
View File

@@ -3,36 +3,9 @@ version: 1
runtime: python
api_version: 1
# This file defines two mutually exclusive
# hander blocks:
# - a handler for use on a local dev_appserver
# during development or non-production doc build
# - a handler for use on a production gae
# instance. This handler requires that the
# docs files in the app have been compressed
# with divide_and_compress.py and that main.py
# and gae_shell/ are present.
#
# Only one of the handler blocks should be
# uncommented at any given time. By default,
# the development handler is exposed.
handlers:
# DEVELOPMENT HANDLER
# (this handler block *must* be commented
# out before pushing to a production server)
- url: /
static_dir: /
# PRODUCTION GAE HANDLER
#- url: /gae_shell/static
# static_dir: gae_shell/static
# expiration: 1d
#
#- url: /gae_shell/.*
# script: /gae_shell/shell.py
# login: admin
#
#- url: .*
# script: main.py

4
docs/html/community/index.jd
View File

@@ -4,7 +4,7 @@ page.title=Community
<div id="mainBodyFluid">
<h1>Community</h1>
<p>Welcome to the Android developers community! We're glad you're here and invite you to participate in these discussions. Before posting, please read the <a href="http://source.android.com/discuss/android-discussion-groups-charter">Groups Charter</a> that covers the community guidelines.</p>
<p>Welcome to the Android developers community! We're glad you're here and invite you to participate in these discussions. Before posting, please red the <a href="#">Groups Charter</a> that covers the community guidelines.</p>
<p class="note"><strong>Note:</strong> If you are seeking discussion about Android source code (not application development),
then please refer to the <a href="http://source.android.com/discuss">Open Source Project Mailing lists</a>.</p>
@@ -115,4 +115,4 @@ you want to read this group?" select one of the email options. </li>
</div>
</div>

2
docs/html/guide/publishing/app-signing.jd
View File

@@ -94,7 +94,7 @@ you can run Keytool manually to generate your own keystore/key and then sign you
application with Jarsigner.</li>
</ul>
<h2 id="strategies">Signing Strategies</h2>
<h2 id="strategies">Signing Strategies</h3>
<p>Some aspects of application signing may affect how you approach the development
of your application, especially if you are planning to release multiple

36
docs/html/guide/publishing/preparing.jd
View File

@@ -18,11 +18,9 @@ page.title=Preparing to Publish: A Checklist
<p>Publishing an application means testing it, packaging it appropriately, and
making it available to users of Android-powered mobile devices.</p>
<p>If you plan to publish your application for installation on
Android-powered devices, there are several things you need to do, to get
your application ready. This document highlights the significant
checkpoints for preparing your application for a successful release.
</p>
<p>If you plan to publish your application for installation on Android-powered devices,
there are several things you need to do, to get your application ready. This document
the significant checkpoints for preparing your application for a successful release. </p>
<p>If you will publish your application on Android Market, please also see <a
href="{@docRoot}guide/publishing/publishing.html#market">Publishing on Android Market</a>
@@ -69,7 +67,7 @@ testing classes and tools. You can use
{@link android.app.Instrumentation Instrumentation} to run JUnit and other
test cases, and you can use testing
tools such as the <a href="{@docRoot}guide/developing/tools/monkey.html">UI/Application
Exerciser Monkey</a>. </p>
Exerciser Monkey</a>. </p>
<ul>
<li>To ensure that your application will run properly for users, you should make
@@ -133,7 +131,7 @@ code.</li>
<h2 id="finalcompile">Before you do the final compile of your application</h2>
<h3 id="versionapp">5. Version your application</h3>
<h3 id="versionapp">5. Version Your Application</h3>
<p>Before you compile your application, you must make sure that you have defined
a version number for your application, specifying an appropriate value for both
@@ -149,8 +147,7 @@ increment both the <code>android:versionCode</code> and
element in the application's manifest file, using appropriate values. </p>
<p>For detailed information about how to define version information for your
application, see <a href="{@docRoot}guide/publishing/versioning.html">Versioning
Your Applications</a>.</p>
application, see <a href="{@docRoot}guide/publishing/versioning.html">Versioning Your Applications</a>.</p>
<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h3>
@@ -161,8 +158,7 @@ private data, as described above. </p>
<p>Before you sign your application, you need to make sure that you have a
suitable private key. For complete information about how to obtain (or generate)
a private key, see <a href="{@docRoot}guide/publishing/app-signing.html#cert">
Obtaining a Suitable Private Key</a>.</p>
a private key, see <a href="#cert">Obtaining a Private Key</a>.</p>
<p>Once you have obtained (or generated) a suitable private key, you will use it
to:</p>
@@ -170,18 +166,20 @@ to:</p>
<ul>
<li>Register for a Maps API Key (see below), if your application uses MapView
elements.</li>
<li>Sign your application for release, later in the preparation process</li>
<li>Sign your application for release</li>
</ul>
<h3 id="mapsApiKey">7. Register for a Maps API Key, if your application is using
MapView elements</h3>
<div class="sidebox" style="margin-bottom:.5em;padding:1em;"><p>
For complete information about getting a Maps API Key, see <a
<div class="sidebox" style="margin-bottom:.5em;"><p>For complete information
about getting a Maps API Key, see <a
href="{@docRoot}guide/topics/location/geo/mapkey.html">Obtaining a Maps API
Key</a>.<br></p></div>
<p>If your application uses one or more Mapview elements, you will need to
<p>If your application uses one or more
{@link-fixme com.google.android.maps.MapView Mapview} elements, you will need to
register your application with the Google
Maps service and obtain a Maps API Key, before your MapView(s) will be able to
retrieve data from Google Maps. To do so, you supply an MD5 fingerprint of your
@@ -224,20 +222,20 @@ to download Maps data. </li>
href="#signing">Signing Your Applications</a>.</p>
<h2 id="compile">Compile your application</h2>
<h2 id="compile">Compile Your Application</h2>
<p>When you've prepared your application as described in the previous sections,
you can compile your application for release. </p>
<h2 id="post-compile">After compiling your application</h2>
<h2 id="post-compile">After Compiling Your Application</h2>
<h3 id="signapp">8. Sign your application</h3>
<h3 id="signapp">8. Sign Your Application</h3>
<p>Sign your application using your private key. Signing your application
correctly is critically important. Please see <a href="#signing">Signing Your
Applications</a> for complete information. </p>
<h3 id="testapp">9. Test your compiled and signed application</h3>
<h3 id="testapp">9. Test Your Compiled and Signed Application</h3>
<p>Before you release your compiled application, you should thoroughly test it
on the target mobile device (and target network, if possible). In particular,

2
docs/html/guide/publishing/publishing.jd
View File

@@ -84,7 +84,7 @@ that it meets the requirements listed below, which are enforced by the Market
server when you upload the application.</p>
<div class="special">
<p>Requirements enforced by the Android Market server:</p>
<p>Requirements enforced by the Android Market server</p>
<ol>
<li>Your application must be signed with a cryptographic private key whose
validity period ends after <span style="color:red">22 October 2033</span>. </li>

2
docs/html/guide/topics/manifest/manifest-intro.jd
View File

@@ -51,7 +51,7 @@ profiling and other information as the application is running. These declaratio
are present in the manifest only while the application is being developed and
tested; they're removed before the application is published.</li>
<li>It declares the minimum level of the Android API that the application
<li>It declares the minimum version of the Android API that the application
requires.</li>
<li>It lists the libraries that the application must be linked against.</li>

43
docs/html/guide/topics/ui/themes.jd
View File

@@ -36,8 +36,8 @@ parent.link=index.html
<li>Create a file named <code>styles.xml</code> in the your application's <code>res/values</code> directory. Add a root <code>&lt;resources></code> node.</li>
<li>For each style or theme, add a <code>&lt;style&gt;</code> element with a unique <code>name</code> and, optionally, a <code>parent</code> attribute.
The name is used for referencing these styles later, and the parent indicates what style resource to inherit from.</li>
<li>Inside the <code>&lt;style></code> element, declare format values in one or more <code>&lt;item&gt;</code> element(s).
Each <code>&lt;item&gt;</code> identifies its style property with a <code>name</code> attribute and defines its style value inside the element.</li>
<li>Inside the <code>style</code> element, declare format values in one or more <code>&lt;item&gt;</code> element.
Each <code>item</code> identifies its style property with a <code>name</code> attribute and defines its style value inside the element.</li>
<li>You can then reference the custom resources from other XML resources, your manifest or application code.</li>
</ol>
@@ -60,7 +60,7 @@ parent.link=index.html
The <code>name</code> attribute in the <code>item</code> can refer to a standard string, a hex color value,
or a reference to any other resource type.</p>
<p>Notice the <code>parent</code> attribute in the <code>&lt;style></code> element. This attribute lets you specify a resource from which the current style will inherit values. The style can inherit from any type of resource that contains the style(s) you want. In general, your styles should always inherit (directly or indirectly) from a standard Android style resource. This way, you only have to define the values that you want to change.</p>
<p>Note the <code>parent</code> attribute in the <code>style</code> element. This attribute lets you specify a resource from which the current style will inherit values. The style can inherit from any type of resource that contains the style(s) you want. In general, your styles should always inherit (directly or indirectly) from a standard Android style resource. This way, you only have to define the values that you want to change.</p>
<p>Here's how you would reference the custom style from an XML layout, in this case, for an EditText element:</p>
@@ -72,15 +72,14 @@ or a reference to any other resource type.</p>
android:text="Hello, World!" /&gt;
</pre>
<p>Now this EditText widget will be styled as defined by the XML example above.</p>
<p>Now this EditText widget will be styled as defined by the <code>style</code> example above.</p>
<h2 id="themes">Themes</h2>
<p>Just like styles, themes are also declared in XML <code>&lt;style&gt;</code> elements, and are referenced in the same manner.
The difference is that you add a theme to an entire application or activity, via the <code>&lt;application&gt;</code>
and <code>&lt;activity&gt;</code> elements in the Android Manifest &mdash;
themes cannot be applied to individual Views.</p>
The difference is that you can add a theme style only to <code>&lt;application&gt;</code> and <code>&lt;activity&gt;</code> elements &mdash;
they cannot be applied to individual views in the layout.</p>
<p>Here's an example declaration of a theme:</p>
@@ -131,26 +130,32 @@ appear like a dialog box. In the manifest, reference an Android theme like so:</
</pre>
<p>If you like a theme, but want to slightly tweak it, just add the theme as the <code>parent</code> of your custom theme.
For example, we'll modify the <code>Theme.Dialog</code> theme. To do so, create a style
with <code>Theme.Dialog</code> as the parent:</p>
For example, we'll modify the <code>Theme.Dialog</code> theme. First, we need to import the parent of the
<code>Dialog</code> theme: <code>Theme</code>. At the top of the <code>resources</code>, add:</p>
<pre>
&lt;style name="Theme" parent="@android:Theme">
&lt;!-- no modification -->
&lt;/style>
</pre>
<p>Now create a a new theme with <code>Theme.Dialog</code> as the parent:</p>
<pre>
&lt;style name="CustomDialogTheme" parent="@android:style/Theme.Dialog">
</pre>
<p>There it is. We've inherited the Android Dialog theme so we can adjust its styles as we like.
So, for each item in the Dialog theme that we want to change, we re-define the value here and
use <var>CustomDialogTheme</var> instead of <var>Theme.Dialog</var> inside the Android Manifest.</p>
<p>There it is. We've inherited the Dialog theme, so we can adjust its styles as we like.
So, for each item in the Dialog theme that we want to override, we re-define the value under this style and
then use <var>CustomDialogTheme</var> instead of the <var>Theme.Dialog</var>.</p>
<h3 id="fromTheApp">Set the theme from the application</h3>
<p>You can also load a theme for an Activity programmatically, if needed.
To do so, use the {@link android.app.Activity#setTheme(int) setTheme()}
method. Note that, when doing so, you must be sure to set the theme <em>before</em>
instantiating any Views in the context, for example, before calling
<code>setContentView(View)</code> or <code>inflate(int, ViewGroup)</code>. This ensures that
setContentView(View) or inflate(int, ViewGroup). This ensures that
the system applies the same theme for all of your UI screens. Here's an example:</p>
<pre>
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
protected void onCreate(Bundle icicle) {
super.onCreate(icicle);
...
setTheme(android.R.style.Theme_Light);
setContentView(R.layout.linear_layout_3);
@@ -159,14 +164,14 @@ the system applies the same theme for all of your UI screens. Here's an example:
<p>If you are considering loading a theme programmatically for the main
screen of your application, note that the theme would not be applied
in any animations the system would use to start the activity, which
would take place before your application opens. In most cases, if
in any animations the system would use to show the activity, which
would take place before your application starts. In most cases, if
you want to apply a theme to your main screen, doing so in XML
is a better approach. </p>
<p>For detailed information about custom styles and themes and referencing them from your application, see
<a href="{@docRoot}guide/topics/resources/available-resources.html#stylesandthemes">Available Resource Types:
Style and Themes</a>.</p>
<a href="{@docRoot}guide/topics/resources/available-resources.html#stylesandthemes">Style
and Theme Resources</a>.</p>
<p>For information about default themes and styles available, see {@link android.R.style}.</p>

2
docs/html/guide/tutorials/views/hello-autocomplete.jd
View File

@@ -40,7 +40,7 @@ protected void onCreate(Bundle savedInstanceState) {
AutoCompleteTextView textView = (AutoCompleteTextView) findViewById(R.id.edit);
ArrayAdapter<String> adapter = new ArrayAdapter<String>(this,
android.R.layout.simple_dropdown_item_1line, COUNTRIES);
android.R.layout.simple_dropdown_item_1line, R.array.planets);
textView.setAdapter(adapter);
}
</pre>

20
docs/html/guide/tutorials/views/hello-formstuff.jd
View File

@@ -32,7 +32,7 @@ We'll make it display a message when pressed.</p>
<ol>
<li><img src="images/android.png" align="right"/>
Drag the Android image on the right (or your own image) into the
res/drawable/ directory of your project.
res/drawables/ directory of your project.
We'll use this for the button.</li>
<li>Open the layout file and, inside the LinearLayout, add the {@link android.widget.ImageButton} element:
<pre>
@@ -43,7 +43,7 @@ We'll make it display a message when pressed.</p>
android:src="@drawable/android" />
</pre>
<p>The source of the button
is from the res/drawable/ directory, where we've placed the android.png.</p>
is from the res/drawables/ directory, where we've placed the android.png.</p>
<p class="note"><strong>Tip:</strong> You can also reference some of the many built-in
images from the Android {@link android.R.drawable} resources,
like <code>ic_media_play</code>, for a "play" button image. To do so, change the source
@@ -52,7 +52,7 @@ We'll make it display a message when pressed.</p>
<li>To make the button to actually do something, add the following
code at the end of the <code>onCreate()</code> method:
<pre>
final ImageButton button = (ImageButton) findViewById(R.id.android_button);
ImageButton button = (ImageButton) findViewById(R.id.android_button);
button.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
// Perform action on clicks
@@ -84,12 +84,12 @@ defines the action to be made when the button is clicked. Here, we show a
<li>To do something with the text that the user enters, add the following code
to the end of the <code>onCreate()</code> method:
<pre>
final EditText edittext = (EditText) findViewById(R.id.edittext);
EditText edittext = (EditText) findViewById(R.id.edittext);
edittext.setOnKeyListener(new OnKeyListener() {
public boolean onKey(View v, int keyCode, KeyEvent event) {
if ((event.getAction() == KeyEvent.ACTION_DOWN) && (keyCode == KeyEvent.KEYCODE_ENTER)) {
// Perform action on key press
Toast.makeText(HelloFormStuff.this, edittext.getText(), Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, edittext.getText(), Toast.LENGTH_SHORT).show();
return true;
}
return false;
@@ -127,9 +127,9 @@ checkbox.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
// Perform action on clicks
if (checkbox.isChecked()) {
Toast.makeText(HelloFormStuff.this, "Selected", Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, "Selected", Toast.LENGTH_SHORT).show();
} else {
Toast.makeText(HelloFormStuff.this, "Not selected", Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, "Not selected", Toast.LENGTH_SHORT).show();
}
}
});
@@ -183,7 +183,7 @@ OnClickListener radio_listener = new OnClickListener() {
public void onClick(View v) {
// Perform action on clicks
RadioButton rb = (RadioButton) v;
Toast.makeText(HelloFormStuff.this, rb.getText(), Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, rb.getText(), Toast.LENGTH_SHORT).show();
}
};
</pre>
@@ -225,9 +225,9 @@ togglebutton.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
// Perform action on clicks
if (togglebutton.isChecked()) {
Toast.makeText(HelloFormStuff.this, "ON", Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, "ON", Toast.LENGTH_SHORT).show();
} else {
Toast.makeText(HelloFormStuff.this, "OFF", Toast.LENGTH_SHORT).show();
Toast.makeText(HelloImageButton.this, "OFF", Toast.LENGTH_SHORT).show();
}
}
});

1
docs/html/guide/tutorials/views/hello-gridview.jd
View File

@@ -25,7 +25,6 @@ are acquired from a {@link android.widget.ListAdapter}.</p>
android:stretchMode="columnWidth"
android:gravity="center"
/>
</pre>
</li>
<li>Open the HelloGridView Java file. Insert the following for the <code>onCreate()</code> method:
<pre>

32
docs/html/guide/tutorials/views/hello-mapview.jd
View File

@@ -16,13 +16,8 @@ First, we'll create a simple Activity that can view and navigate a map. Then we
<pre>&lt;uses-library android:name="com.google.android.maps" /></pre>
</li>
<li>We also need access to the internet in order to retrieve the Google Maps tiles,
so the application must request the {@link android.Manifest.permission#INTERNET INTERNET} permissions.
In the manifest file, add the following as a child of the <code>&lt;manifest></code> element:
<pre>&lt;uses-permission android:name="android.permission.INTERNET" /></pre>
</li>
<li>Now open the main layout file for your project. Define a layout with a com.google.android.maps.MapView
inside a android.widget.RelativeLayout:
<li>Open the layout file. Define the layout with a MapView inside a RelativeLayout:
<pre>
&lt;?xml version="1.0" encoding="utf-8"?>
@@ -37,21 +32,22 @@ First, we'll create a simple Activity that can view and navigate a map. Then we
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:clickable="true"
android:apiKey="<em>Your Maps API Key</em>"
android:apiKey="INSERT YOUR KEY HERE"
/>
&lt;/RelativeLayout>
&lt;RelativeLayout>
</pre>
<p>The <code>clickable</code> attribute defines whether you want to allow user-interaction with the map.
In this case, we set it "true" so that the user can navigate.</p>
<p>Setting <code>clickable</code> is important. Otherwise, the map does not allow any user interaction.</p>
<p>The <code>apiKey</code> attribute holds the Google Maps API Key that proves your application and signer
certificate has been registered with the Google Maps service. Because MapView uses Google Maps data, this key is required
in order to receive the map data, even while you are developing. Registration is free and it only takes a couple
minutes to register your certificate and receive a Maps API Key. For instructions on getting a key, read
<a href="{@docRoot}guide/topics/location/geo/mapkey.html">Obtaining a Maps API Key</a>.
(For the purpose of this tutorial, you should register with the fingerprint of the SDK debug certificate.)
Once you've acquired the Maps API Key, insert it for the <code>apiKey</code> value.</p></li>
<p>The <code>android:apiKey</code> must contain an authentic Android Maps API key.
The API key is generated using the MD5 fingerprint of your application certificate. For the purposes of
this exercise, you should use the fingerprint of your debug certificate (which cannot be used to release
your application for Android devices, but will work while developing). See how to
<a href="{@docRoot}guide/topics/location/geo/mapkey.html#getdebugfingerprint">generate a fingerprint from your
debug certificate</a>, then <a href="http://code.google.com/android/maps-api-signup.html">register the
certificate</a> to retieve an API key.
Insert the API key as the value of the <code>apiKey</code> attribute. If you do not insert a valid
Maps API key, the application will still run, but no map tiles will load.</p></li>
<li>Now open the HelloMapView.java file. For this Activity, we're going to extend the special sub-class of
Activity called MapActivity, so change the class declaration to extend

75
docs/html/sdk/1.0_r1/index.jd
View File

@@ -22,44 +22,43 @@ sdk.linux_checksum=2660b4029039b7d714e59827e9a9a11d
<h2>Included in this SDK</h2>
<h4>Development tools</h4>
<p>The SDK includes a variety of tools for developing and debugging application code and designing
an application UI. You can read about the tools in the documentation included with the SDK.
You can access the tools in the <code>&lt;sdk&gt;/tools/</code> directory.</p>
<h4 id="system_images">System Images</h4>
<p>The Android system images listed below are included in this SDK.</p>
<table style="margin-right:1em;" width="80%">
<tr>
<th><nobr>System Image</nobr></th><th><nobr>API Level</nobr></th><th>Notes</th><th>Description</th>
</tr>
<tr>
<td width="5%"><nobr>Android 1.0</nobr></td>
<td width="5%">1</td>
<td width="5%"><nobr>N/A</nobr></td>
<td>Includes the {@code com.google.android.maps} external library and a set of standard development
applications. </td>
</tr>
</table>
<h4>Sample Code and Applications</h4>
<p>You can look at a variety of tutorials and samples in the
documentation included with the SDK and access the sample code itself
in the <code>&lt;sdk&gt;/samples/</code> directory of the SDK package.</p>
<h4>Documentation</h4>
<p>The SDK package provides a full set of local documentation, including installation and upgrade
instructions. To view it, open the <code>&lt;sdk&gt;/documentation.html</code> file in a web browser.
If you are developing in an IDE such as Eclipse, you can also view the reference documentation
directly in the IDE. </p>
<p>This SDK includes some awesome stuff.</p>
<h2>System and Software Requirements</h2>
<p>The following systems and development environments are supported by this SDK.</p>
<h4>Supported Operating Systems:</h4>
<ul>
<li>Windows XP or Vista</li>
<li>Mac OS X 10.4.8 or later (x86 only)</li>
<li>Linux (tested on Linux Ubuntu Dapper Drake)</li>
</ul>
<h4>Supported Development Environments:</h4>
<ul>
<li>Eclipse IDE
<ul>
<li><a href="http://www.eclipse.org/downloads/">Eclipse</a> 3.3 (Europa), 3.4 (Ganymede)
<ul>
<li>Eclipse <a href="http://www.eclipse.org/jdt">JDT</a> plugin (included in most Eclipse IDE packages) </li>
<li><a href="http://www.eclipse.org/webtools">WST</a> (optional, but needed for the Android Editors feature; included in <a href="http://www.eclipse.org/downloads/moreinfo/compare.php">most Eclipse IDE packages</a>)</li>
</ul>
</li>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="installing.html#installingplugin">Android Development Tools plugin</a> (optional)</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
<li>Other development environments or IDEs
<ul>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="http://ant.apache.org/">Apache Ant</a> 1.6.5 or later for Linux and Mac, 1.7 or later for Windows</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
</ul>
<p class="note"><strong>Note:</strong> If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In
particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development. </p>

171
docs/html/sdk/1.0_r1/installing.jd
View File

@@ -1,27 +1,29 @@
page.title=Installing the SDK
sdk.version=1.0_r1
@jd:body
<p>For the current SDK release, see the links under <strong>Current SDK Release</strong> in the side navigation.</p>
<p>This page describes how to install the Android 1.0 SDK, Release 1, and set up your development environment.
If you haven't downloaded the SDK yet, you can so from the <a href="{@docRoot}sdk/1.0_r1/index.html">Download</a> page.</p>
<p>This page describes how to install the Android SDK and set up your development environment. If you haven't
downloaded the SDK yet, follow the link below.</p>
<p>Before you begin, be sure that your development environment meets the SDK
<a href="{@docRoot}sdk/1.0_r1/requirements.html">System Requirements</a>. If you encounter any problems during installation,
see the <a href="#installnotes">Installation Notes</a> at the bottom of this page.</p>
<div class="linkbox"><a href="http://developer.android.com/sdk/">Download the SDK</a></div>
<p>Before you begin, be sure that you're development environment meets the SDK
<a href="requirements.html">System and Software Requirements</a>.</p>
<div class="special">
<h4 style="margin-top">Upgrading?</h4>
<p>If you have already developed applications using an earlier version of the
SDK, please skip this page and read the
<a href="{@docRoot}sdk/1.0_r1/upgrading.html"><strong>Upgrading the SDK</strong></a></b> document instead.
<b><a href="upgrading.html">Upgrading the SDK</a></b> document.
</p>
</div>
<a name="installingsdk"></a>
<a name="setup"></a>
<h2>Installing the SDK</h2>
<p>After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named <code>android_sdk_<em>&lt;platform</em>&gt;_<em>&lt;release&gt;</em>_<em>&lt;build&gt;</em></code>. The directory contains a link to a local copy of the documentation and the subdirectories <code>tools/</code>, <code>samples/</code>, and others. </p>
<p>After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named <code>android_sdk_<em>&lt;platform</em>&gt;_<em>&lt;release&gt;</em>_<em>&lt;build&gt;</em></code>. The directory contains the subdirectories <code>tools/</code>, <code>samples/</code>, and others. </p>
<p>Make a note of the name and location of the unpacked SDK directory on your system &mdash; you will need to refer to the SDK directory later, when setting up the Android plugin or using SDK tools. </p>
@@ -45,86 +47,10 @@ SDK, please skip this page and read the
<p>Adding <code>tools</code> to your path lets you run Android Debug Bridge (adb) and the other command line <a href="{@docRoot}guide/developing/tools/index.html">tools</a> without needing to supply the full path to the tools directory. Note that, if you update your SDK, you should remember to update your PATH settings to point to the new location, if different.</p>
<p>If you will be using the Eclipse IDE as your environment for developing Android applications, continue reading the next
section in order to install the Android Development Tools plugin and setup Eclipse. If you choose not to use Eclipse, you can
develop Android applications using other tools &mdash; read the guide to developing
<a href="{@docRoot}guide/developing/other-ide.html">In other IDEs</a>.</p>
<h2>Setting up Eclipse</h2>
<p>First, you should install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.</p>
<p>To download and install the ADT plugin, follow the steps below for your respective Eclipse version. </p>
<table style="font-size:100%">
<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr>
<tr>
<td width="45%">
<ol>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find
and Install...</strong>. </li>
<li>In the dialog that appears, select <strong>Search for new features to install</strong> and click <strong>Next</strong>. </li>
<li>Click <strong>New Remote Site</strong>. </li>
<li>In the resulting dialog box, enter a name for the remote site (e.g. Android Plugin) and enter this as its URL:
<pre>https://dl-ssl.google.com/android/eclipse/</pre>
<p>Alternatively, you can use http in the Location URL, if you are having
trouble with https (https is preferred for security reasons).</p>
<pre>http://dl-ssl.google.com/android/eclipse/</pre>
<p>Click <strong>OK</strong>.</p> </li>
<li>You should now see the new site added to the search list (and checked).
Click <strong>Finish</strong>. </li>
<li>In the subsequent Search Results dialog box, select the checkbox for
<strong>Android Plugin</strong> &gt; <strong>Developer Tools</strong>.
This will check both features: "Android Developer Tools", and "Android
Editors". The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>. </li>
<li>Read the license agreement and then select <strong>Accept terms of the license agreement</strong>.
Click <strong>Next</strong>. </li>
<li>Click <strong>Finish</strong>. </li>
<li>The ADT plugin is not signed; you can accept the installation anyway
by clicking <strong>Install All</strong>. </li>
<li>Restart Eclipse. </li>
</ol>
</td>
<td>
<ol>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates...</strong>.
</li>
<li>In the dialog that appears, click the <strong>Available Software</strong> tab.
</li>
<li>Click <strong>Add Site...</strong>
</li>
<li>Enter this as the Location:
<pre>https://dl-ssl.google.com/android/eclipse/</pre>
<p>Alternatively, you can use http in the Location URL, if you are having
trouble with https (https is preferred for security reasons).</p>
<pre>http://dl-ssl.google.com/android/eclipse/</pre>
<p>Click <strong>OK</strong>.</p></li>
<li>Back in the Available Software view, you should see the plugin. Select the checkbox next to
<em>Developer Tools</em> and click <strong>Install...</strong>
</li>
<li>On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked.
The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>.
</li>
<li>Accept the license agreement and click <strong>Finish</strong>.</li>
<li>Restart Eclipse. </li>
</ol>
</td>
</tr>
</table>
<p>Now, you just need to modify your Eclipse preferences to point to the Android SDK directory:</p>
<h3>Setting up Eclipse</h3>
<p>If you'll be developing with the Eclipse IDE, follow the following procedure to setup the IDE
to use the Android SDK.</p>
<p>Basically, you just need to update your Eclipse preferences to point to the Android SDK directory:</p>
<ol>
<li>Select <strong>Window</strong> &gt; <strong>Preferences...</strong> to open the Preferences
panel. (Mac OS X: <strong>Eclipse</strong> &gt; <strong>Preferences</strong>) </li>
@@ -132,55 +58,16 @@ develop Android applications using other tools &mdash; read the guide to develop
<li>For the SDK Location in the main panel, click <strong>Browse...</strong> and locate the SDK directory. </li>
<li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li>
</ol>
<p>Done! We now recommend that you install the ADT Eclipse plugin, which will provide some much-appreciated assistance in developing Android apps with Eclipse...</p>
<p>Done! If you haven't encountered any problems, then you're ready to begin developing Android applications.
We recommend you begin with the <a href="{@docRoot}guide/tutorials/hello-world.html">Hello World</a> tutorial,
which will teach you some basics about Android applications and how to create projects using Eclipse.</p>
<a name="installingplugin"></a>
<h2>Installing the Eclipse Plugin (ADT)</h2>
<p>If you will be using the Eclipse IDE as your environment for developing Android applications, you can install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. This plugin is highly recommended for Eclipse users.</p>
<h3 id="troubleshooting">Troubleshooting ADT Installation</h3>
<p>
If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions: </p>
<p>If you <em>will not</em> be using the Eclipse IDE, you do not need to download or install the ADT plugin.</p>
<ul>
<li>If Eclipse can not find the remote update site containing the ADT plugin, try changing the remote site URL to use http, rather than https. That is, set the Location for the remote site to:
<pre>http://dl-ssl.google.com/android/eclipse/</pre></li>
<li>If you are behind a firewall (such as a corporate firewall), make
sure that you have properly configured your proxy settings in Eclipse.
In Eclipse 3.3/3.4, you can configure proxy information from the main
Eclipse menu in <strong>Window</strong> (on Mac, <strong>Eclipse</strong>) &gt; <strong>Preferences</strong> &gt; <strong>General</strong> &gt; <strong>Network Connections</strong>.</li>
</ul>
<p>
If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you can download the ADT files to your local machine using a browser and the install the files in Eclipse from there:
</p>
<ol>
<li><a href="{@docRoot}sdk/adt_download.html">Download the ADT zip file</a> (do not unpack it).
<li>Follow steps 1 and 2 in the default install instructions (above).
<li>In Eclipse 3.3, click <strong>New Archive Site...</strong>. <br/>
In Eclipse 3.4, click <strong>Add Site...</strong>, then <strong>Archive...</strong>
<li>Browse and select the downloaded the zip file.
<li>Follow the remaining procedures, above, starting from steps 5.
</ol>
<p>
Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.</p>
<p>Note that the "Android Editors" feature of ADT requires several optional
Eclipse components (for example, WST). If you encounter an error when
installing ADT, your Eclipse installion might not include those components.
For information about how to quickly add the necessary components to your
Eclipse installation, see the troubleshooting topic
<a href="{@docRoot}guide/appendix/faq/troubleshooting.html#installeclipsecomponents">ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui"</a>.</p>
<h4>For Linux users</h4>
<p>If you encounter this error when installing the ADT Plugin for Eclipse:
<pre>
An error occurred during provisioning.
Cannot connect to keystore.
JKS</pre>
<p>
...then your development machine lacks a suitable Java VM. Installing Sun
Java 6 will resolve this issue and you can then reinstall the ADT
Plugin.</p>
<p><strong>Follow this guide to install the ADT Plugin</strong></p>
<a name="installnotes"></a>
<h2>Installation Notes</h2>
@@ -219,3 +106,19 @@ at the top of this page. In particular, note that some Linux
distributions may include JDK 1.4 or Gnu Compiler for Java, both of
which are not supported for Android development.</li>
</ul>
<a name="developingwitheclipse"></a>
<a name="existingcode"></a>
<a name="creatingaproject" id="creatingaproject"></a>
<a name="launchconfig" id="launchconfig"></a>
<a name="installingrunningdebugging" id="installingrunningdebugging"></a>
<a name="otherides" id="otherides"></a>
<a name="buildingwithant"></a>
<a name="debugging" id="debugging"></a>
<a name="additionaldebugging" id="additionaldebugging"></a>
<a name="toptips" id="toptips"></a>
<a name="debughelpers"></a>
<a name="uninstalling" id="uninstalling"></a>
<a name="tips" id="tips"></a>
<a name="eclipse" id="eclipse"></a>
<a name="building"></a>

103
docs/html/sdk/1.0_r1/upgrading.jd
View File

@@ -1,12 +1,37 @@
page.title=Upgrading the SDK
sdk.version=1.0_r1
@jd:body
<p>For the current SDK release, see the links under <strong>Current SDK Release</strong> in the side navigation.</p>
<div class="sidebox-wrapper">
<div class="sidebox-inner">
<h2>Useful Links</h2>
<ul class="noindent">
<li><a href="migrating/0.9-1.0/changes-overview.html">Overview of Changes</a>
<p>A high-level look at what's changed in Android, with
discussion of how the changes may affect your apps.</p></li>
<li><a href="migrating/0.9-1.0/changes.html">API Diff Report</a>
<p>A detailed report that lists all the specific changes in the latest SDK.</p></li>
<li><a href="RELEASENOTES.html">Release Notes</a>
<p>Version details, known issues, and resolved issues. </p></li>
<li><a href="http://groups.google.com/group/android-developers">Android Developers Group</a>
<p>A forum where you can discuss migration issues and learn from other Android developers. </p></li>
<li><a href="http://code.google.com/p/android/issues/list">Android Issue Tracker</a>
<p>If you think you may have found a bug, use the issue tracker to report it.</p></li>
</ul>
</div>
</div><!-- class-sidebox -->
<p>This guide will help you migrate your development environment and applications
to <strong>version 1.0, release 1</strong>, of the Android SDK. Use this guide if you've been developing applications
on a different version of the Android SDK.</p>
to the latest version of the SDK. Use this guide if you've been developing applications
on a previous version of the Android SDK.
</p>
<p>To ensure that your applications are compliant with the Android 1.0 system available
on mobile devices, you need to install the new SDK and port your existing Android
@@ -14,7 +39,9 @@ applications to the updated API. The sections below guide you through the proces
<h2 id="install-new">Install the new SDK</h2>
<p>After unpacking the SDK, you should:</p>
<p><a href="{@docRoot}download.html">Download the SDK</a> and unpack it into a safe location.</p>
<p>After unpacking the new SDK, you should:</p>
<ul>
<li>Wipe your emulator data. <p>Some data formats have changed since the last
@@ -33,58 +60,27 @@ applications to the updated API. The sections below guide you through the proces
<h2 id="update-plugin">Update your ADT Eclipse Plugin</h2>
<p>If you develop on Eclipse and are using the ADT plugin, follow these steps to install the
plugin that's required for this version of the SDK.</p>
<p>If you develop on Eclipse and are using the ADT plugin, follow these steps to install the new plugin that accompanies the latest SDK.</p>
<table style="font-size:100%">
<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr>
<tr>
<td width="45%">
<td width="50%">
<ol>
<li><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">Download the ADT v0.8.0 zip
file</a> (do not unpack it).</li>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find
and Install...</strong>. </li>
<li>In the dialog that appears, select <strong>Search for new features to install</strong> and click
<strong>Next</strong>. </li>
<li>Click <strong>New Archive Site...</strong></li>
<li>Browse and select the downloaded the zip file.</li>
<li>You should now see the new site added to the search list (and checked).
Click <strong>Finish</strong>. </li>
<li>In the subsequent Search Results dialog box, select the checkbox for
<strong>Android Plugin</strong> &gt; <strong>Developer Tools</strong>.
This will check both features: "Android Developer Tools", and "Android
Editors". The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>. </li>
<li>Read the license agreement and then select <strong>Accept terms of the license agreement</strong>.
Click <strong>Next</strong>. </li>
<li>Click <strong>Finish</strong>. </li>
<li>The ADT plugin is not signed; you can accept the installation anyway
by clicking <strong>Install All</strong>. </li>
<li>Restart Eclipse. </li>
<li> Select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find and Install...</strong>. </li>
<li> Select <strong>Search for updates of the currently installed features</strong> and click <strong>Finish</strong>. </li>
<li> If any update for ADT is available, select and install. </li>
<li> Restart Eclipse.</li>
</ol>
</td>
<td>
<ol>
<li><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">Download the ADT v0.8.0 zip
file</a> (do not unpack it).</li>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates...</strong>.</li>
<li>In the dialog that appears, click the <strong>Available Software</strong> tab.</li>
<li>Click <strong>Add Site...</strong>, then <strong>Archive...</strong>.</li>
<li>Browse and select the downloaded the zip file.</li>
<li>Back in the Available Software view, you should see the plugin. Select the checkbox next to
<em>Developer Tools</em> and click <strong>Install...</strong></li>
<li>On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked.
The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>.</li>
<li>Accept the license agreement and click <strong>Finish</strong>.</li>
<li>Restart Eclipse. </li>
<li>Select <strong>Help</strong> &gt; <strong>Software Updates...</strong></li>
<li>Select the <strong>Installed Software</strong> tab.</li>
<li>Click <strong>Update...</strong></li>
<li>If an update for ADT is available, select it and click <strong>Finish</strong>.</li>
<li>Restart Eclipse.</li>
</ol>
</td>
</tr>
</table>
@@ -103,7 +99,7 @@ plugin that's required for this version of the SDK.</p>
the ADT plugin and the Ant-based build tools support this requirement by signing compiled
.apk files with a debug key. To do so, the build tools use the Keytool utility included
in the JDK to to create a keystore and a key with a known alias and password. For more
information, see "Signing and Publishing Your App" in the documentation included with the SDK.
information, see <a href="{@docRoot}guide/publishing/app-signing.html">Signing Your Applications</a>.
<p>To support signing, you should first make sure that Keytool is available to the SDK build
tools. In most cases, you can tell the SDK build tools how to find Keytool by making sure that
@@ -137,7 +133,10 @@ to place 3rd jar files, which are now automatically handled by the Ant script.</
framework and API changes. You'll need to update your code to match changes in the Android APIs.</p>
<p>One way to start is to open your project in Eclipse and see where the ADT
identifies errors in your application.</p>
identifies errors in your application. From there, you can lookup
respective changes in the
<a href="migrating/changes-overview.html">Overview of Changes</a>
and <a href="migrating/changes.html">API Diffs Report</a>.</p>
<p>If you have additional trouble updating your code, visit the
<a href="http://groups.google.com/group/android-developers">Android Developers Group</a>
@@ -145,4 +144,8 @@ to seek help from other Android developers.</p>
<p>If you have modified one of the ApiDemos applications and would like to migrate it
to the new SDK, note that you will need to uninstall the version of ApiDemos that comes
preinstalled in the emulator.</p>
preinstalled in the emulator. For more information, or if you encounter an "reinstallation"
error when running or installing ApiDemos, see the troubleshooting topic
<a href="{@docRoot}guide/appendix/faq/troubleshooting.html#apidemosreinstall">I can't install ApiDemos
apps in my IDE because of a signing error</a> for information about how to solve the problem.</p>

75
docs/html/sdk/1.0_r2/index.jd
View File

@@ -22,44 +22,43 @@ sdk.linux_checksum=a1f3b6d854596f850f5008856d0f380e
<h2>Included in this SDK</h2>
<h4>Development tools</h4>
<p>The SDK includes a variety of tools for developing and debugging application code and designing
an application UI. You can read about the tools in the documentation included with the SDK.
You can access the tools in the <code>&lt;sdk&gt;/tools/</code> directory.</p>
<h4 id="system_images">System Images</h4>
<p>The Android system images listed below are included in this SDK.</p>
<table style="margin-right:1em;" width="80%">
<tr>
<th><nobr>System Image</nobr></th><th><nobr>API Level</nobr></th><th>Notes</th><th>Description</th>
</tr>
<tr>
<td width="5%"><nobr>Android 1.0</nobr></td>
<td width="5%">1</td>
<td width="5%"><nobr>N/A</nobr></td>
<td>Includes the {@code com.google.android.maps} external library and a set of standard development
applications. </td>
</tr>
</table>
<h4>Sample Code and Applications</h4>
<p>You can look at a variety of tutorials and samples in the
documentation included with the SDK and access the sample code itself
in the <code>&lt;sdk&gt;/samples/</code> directory of the SDK package.</p>
<h4>Documentation</h4>
<p>The SDK package provides a full set of local documentation, including installation and upgrade
instructions. To view it, open the <code>&lt;sdk&gt;/documentation.html</code> file in a web browser.
If you are developing in an IDE such as Eclipse, you can also view the reference documentation
directly in the IDE. </p>
<p>This SDK includes some awesome stuff.</p>
<h2>System and Software Requirements</h2>
<p>The following systems and development environments are supported by this SDK.</p>
<h4>Supported Operating Systems:</h4>
<ul>
<li>Windows XP or Vista</li>
<li>Mac OS X 10.4.8 or later (x86 only)</li>
<li>Linux (tested on Linux Ubuntu Dapper Drake)</li>
</ul>
<h4>Supported Development Environments:</h4>
<ul>
<li>Eclipse IDE
<ul>
<li><a href="http://www.eclipse.org/downloads/">Eclipse</a> 3.3 (Europa), 3.4 (Ganymede)
<ul>
<li>Eclipse <a href="http://www.eclipse.org/jdt">JDT</a> plugin (included in most Eclipse IDE packages) </li>
<li><a href="http://www.eclipse.org/webtools">WST</a> (optional, but needed for the Android Editors feature; included in <a href="http://www.eclipse.org/downloads/moreinfo/compare.php">most Eclipse IDE packages</a>)</li>
</ul>
</li>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="installing.html#installingplugin">Android Development Tools plugin</a> (optional)</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
<li>Other development environments or IDEs
<ul>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="http://ant.apache.org/">Apache Ant</a> 1.6.5 or later for Linux and Mac, 1.7 or later for Windows</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
</ul>
<p class="note"><strong>Note:</strong> If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In
particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development. </p>

171
docs/html/sdk/1.0_r2/installing.jd
View File

@@ -1,27 +1,29 @@
page.title=Installing the SDK
sdk.version=1.0_r2
@jd:body
<p>For the current SDK release, see the links under <strong>Current SDK Release</strong> in the side navigation.</p>
<p>This page describes how to install the Android 1.0 SDK, Release 2, and set up your development environment.
If you haven't downloaded the SDK yet, you can so from the <a href="{@docRoot}sdk/1.0_r2/index.html">Download</a> page.</p>
<p>This page describes how to install the Android SDK and set up your development environment. If you haven't
downloaded the SDK yet, follow the link below.</p>
<p>Before you begin, be sure that your development environment meets the SDK
<a href="{@docRoot}sdk/1.0_r2/requirements.html">System Requirements</a>. If you encounter any problems during installation,
see the <a href="#installnotes">Installation Notes</a> at the bottom of this page.</p>
<div class="linkbox"><a href="http://developer.android.com/sdk/">Download the SDK</a></div>
<p>Before you begin, be sure that you're development environment meets the SDK
<a href="requirements.html">System and Software Requirements</a>.</p>
<div class="special">
<h4 style="margin-top">Upgrading?</h4>
<p>If you have already developed applications using an earlier version of the
SDK, please skip this page and read the
<a href="{@docRoot}sdk/1.0_r2/upgrading.html"><strong>Upgrading the SDK</strong></a></b> document instead.
<b><a href="upgrading.html">Upgrading the SDK</a></b> document.
</p>
</div>
<a name="installingsdk"></a>
<a name="setup"></a>
<h2>Installing the SDK</h2>
<p>After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named <code>android_sdk_<em>&lt;platform</em>&gt;_<em>&lt;release&gt;</em>_<em>&lt;build&gt;</em></code>. The directory contains a link to a local copy of the documentation and the subdirectories <code>tools/</code>, <code>samples/</code>, and others. </p>
<p>After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named <code>android_sdk_<em>&lt;platform</em>&gt;_<em>&lt;release&gt;</em>_<em>&lt;build&gt;</em></code>. The directory contains the subdirectories <code>tools/</code>, <code>samples/</code>, and others. </p>
<p>Make a note of the name and location of the unpacked SDK directory on your system &mdash; you will need to refer to the SDK directory later, when setting up the Android plugin or using SDK tools. </p>
@@ -45,86 +47,10 @@ SDK, please skip this page and read the
<p>Adding <code>tools</code> to your path lets you run Android Debug Bridge (adb) and the other command line <a href="{@docRoot}guide/developing/tools/index.html">tools</a> without needing to supply the full path to the tools directory. Note that, if you update your SDK, you should remember to update your PATH settings to point to the new location, if different.</p>
<p>If you will be using the Eclipse IDE as your environment for developing Android applications, continue reading the next
section in order to install the Android Development Tools plugin and setup Eclipse. If you choose not to use Eclipse, you can
develop Android applications using other tools &mdash; read the guide to developing
<a href="{@docRoot}guide/developing/other-ide.html">In other IDEs</a>.</p>
<h2>Setting up Eclipse</h2>
<p>First, you should install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.</p>
<p>To download and install the ADT plugin, follow the steps below for your respective Eclipse version. </p>
<table style="font-size:100%">
<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr>
<tr>
<td width="45%">
<ol>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find
and Install...</strong>. </li>
<li>In the dialog that appears, select <strong>Search for new features to install</strong> and click <strong>Next</strong>. </li>
<li>Click <strong>New Remote Site</strong>. </li>
<li>In the resulting dialog box, enter a name for the remote site (e.g. Android Plugin) and enter this as its URL:
<pre>https://dl-ssl.google.com/android/eclipse/</pre>
<p>Alternatively, you can use http in the Location URL, if you are having
trouble with https (https is preferred for security reasons).</p>
<pre>http://dl-ssl.google.com/android/eclipse/</pre>
<p>Click <strong>OK</strong>.</p> </li>
<li>You should now see the new site added to the search list (and checked).
Click <strong>Finish</strong>. </li>
<li>In the subsequent Search Results dialog box, select the checkbox for
<strong>Android Plugin</strong> &gt; <strong>Developer Tools</strong>.
This will check both features: "Android Developer Tools", and "Android
Editors". The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>. </li>
<li>Read the license agreement and then select <strong>Accept terms of the license agreement</strong>.
Click <strong>Next</strong>. </li>
<li>Click <strong>Finish</strong>. </li>
<li>The ADT plugin is not signed; you can accept the installation anyway
by clicking <strong>Install All</strong>. </li>
<li>Restart Eclipse. </li>
</ol>
</td>
<td>
<ol>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates...</strong>.
</li>
<li>In the dialog that appears, click the <strong>Available Software</strong> tab.
</li>
<li>Click <strong>Add Site...</strong>
</li>
<li>Enter this as the Location:
<pre>https://dl-ssl.google.com/android/eclipse/</pre>
<p>Alternatively, you can use http in the Location URL, if you are having
trouble with https (https is preferred for security reasons).</p>
<pre>http://dl-ssl.google.com/android/eclipse/</pre>
<p>Click <strong>OK</strong>.</p></li>
<li>Back in the Available Software view, you should see the plugin. Select the checkbox next to
<em>Developer Tools</em> and click <strong>Install...</strong>
</li>
<li>On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked.
The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>.
</li>
<li>Accept the license agreement and click <strong>Finish</strong>.</li>
<li>Restart Eclipse. </li>
</ol>
</td>
</tr>
</table>
<p>Now, you just need to modify your Eclipse preferences to point to the Android SDK directory:</p>
<h3>Setting up Eclipse</h3>
<p>If you'll be developing with the Eclipse IDE, follow the following procedure to setup the IDE
to use the Android SDK.</p>
<p>Basically, you just need to update your Eclipse preferences to point to the Android SDK directory:</p>
<ol>
<li>Select <strong>Window</strong> &gt; <strong>Preferences...</strong> to open the Preferences
panel. (Mac OS X: <strong>Eclipse</strong> &gt; <strong>Preferences</strong>) </li>
@@ -132,55 +58,16 @@ develop Android applications using other tools &mdash; read the guide to develop
<li>For the SDK Location in the main panel, click <strong>Browse...</strong> and locate the SDK directory. </li>
<li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li>
</ol>
<p>Done! We now recommend that you install the ADT Eclipse plugin, which will provide some much-appreciated assistance in developing Android apps with Eclipse...</p>
<p>Done! If you haven't encountered any problems, then you're ready to begin developing Android applications.
We recommend you begin with the <a href="{@docRoot}guide/tutorials/hello-world.html">Hello World</a> tutorial,
which will teach you some basics about Android applications and how to create projects using Eclipse.</p>
<a name="installingplugin"></a>
<h2>Installing the Eclipse Plugin (ADT)</h2>
<p>If you will be using the Eclipse IDE as your environment for developing Android applications, you can install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. This plugin is highly recommended for Eclipse users.</p>
<h3 id="troubleshooting">Troubleshooting ADT Installation</h3>
<p>
If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions: </p>
<p>If you <em>will not</em> be using the Eclipse IDE, you do not need to download or install the ADT plugin.</p>
<ul>
<li>If Eclipse can not find the remote update site containing the ADT plugin, try changing the remote site URL to use http, rather than https. That is, set the Location for the remote site to:
<pre>http://dl-ssl.google.com/android/eclipse/</pre></li>
<li>If you are behind a firewall (such as a corporate firewall), make
sure that you have properly configured your proxy settings in Eclipse.
In Eclipse 3.3/3.4, you can configure proxy information from the main
Eclipse menu in <strong>Window</strong> (on Mac, <strong>Eclipse</strong>) &gt; <strong>Preferences</strong> &gt; <strong>General</strong> &gt; <strong>Network Connections</strong>.</li>
</ul>
<p>
If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you can download the ADT files to your local machine using a browser and the install the files in Eclipse from there:
</p>
<ol>
<li><a href="{@docRoot}sdk/adt_download.html">Download the ADT zip file</a> (do not unpack it).
<li>Follow steps 1 and 2 in the default install instructions (above).
<li>In Eclipse 3.3, click <strong>New Archive Site...</strong>. <br/>
In Eclipse 3.4, click <strong>Add Site...</strong>, then <strong>Archive...</strong>
<li>Browse and select the downloaded the zip file.
<li>Follow the remaining procedures, above, starting from steps 5.
</ol>
<p>
Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.</p>
<p>Note that the "Android Editors" feature of ADT requires several optional
Eclipse components (for example, WST). If you encounter an error when
installing ADT, your Eclipse installion might not include those components.
For information about how to quickly add the necessary components to your
Eclipse installation, see the troubleshooting topic
<a href="{@docRoot}guide/appendix/faq/troubleshooting.html#installeclipsecomponents">ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui"</a>.</p>
<h4>For Linux users</h4>
<p>If you encounter this error when installing the ADT Plugin for Eclipse:
<pre>
An error occurred during provisioning.
Cannot connect to keystore.
JKS</pre>
<p>
...then your development machine lacks a suitable Java VM. Installing Sun
Java 6 will resolve this issue and you can then reinstall the ADT
Plugin.</p>
<p><strong>Follow this guide to install the ADT Plugin</strong></p>
<a name="installnotes"></a>
<h2>Installation Notes</h2>
@@ -219,3 +106,19 @@ at the top of this page. In particular, note that some Linux
distributions may include JDK 1.4 or Gnu Compiler for Java, both of
which are not supported for Android development.</li>
</ul>
<a name="developingwitheclipse"></a>
<a name="existingcode"></a>
<a name="creatingaproject" id="creatingaproject"></a>
<a name="launchconfig" id="launchconfig"></a>
<a name="installingrunningdebugging" id="installingrunningdebugging"></a>
<a name="otherides" id="otherides"></a>
<a name="buildingwithant"></a>
<a name="debugging" id="debugging"></a>
<a name="additionaldebugging" id="additionaldebugging"></a>
<a name="toptips" id="toptips"></a>
<a name="debughelpers"></a>
<a name="uninstalling" id="uninstalling"></a>
<a name="tips" id="tips"></a>
<a name="eclipse" id="eclipse"></a>
<a name="building"></a>

44
docs/html/sdk/1.0_r2/requirements.jd
View File

@@ -1,44 +0,0 @@
page.title=System Requirements
sdk.version=1.0_r2
@jd:body
<p>The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android 1.0 SDK, Release 2. </p>
<h2>System and Software Requirements</h2>
<p>The following systems and development environments are supported by this SDK.</p>
<h4>Supported Operating Systems:</h4>
<ul>
<li>Windows XP or Vista</li>
<li>Mac OS X 10.4.8 or later (x86 only)</li>
<li>Linux (tested on Linux Ubuntu Dapper Drake)</li>
</ul>
<h4>Supported Development Environments:</h4>
<ul>
<li>Eclipse IDE
<ul>
<li><a href="http://www.eclipse.org/downloads/">Eclipse</a> 3.3 (Europa), 3.4 (Ganymede)
<ul>
<li>Eclipse <a href="http://www.eclipse.org/jdt">JDT</a> plugin (included in most Eclipse IDE packages) </li>
<li><a href="http://www.eclipse.org/webtools">WST</a> (optional, but needed for the Android Editors feature; included in <a href="http://www.eclipse.org/downloads/moreinfo/compare.php">most Eclipse IDE packages</a>)</li>
</ul>
</li>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="installing.html#installingplugin">Android Development Tools plugin</a> (optional)</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
<li>Other development environments or IDEs
<ul>
<li><a href="http://java.sun.com/javase/downloads/index.jsp">JDK 5 or JDK 6</a> (JRE alone is not sufficient)</li>
<li><a href="http://ant.apache.org/">Apache Ant</a> 1.6.5 or later for Linux and Mac, 1.7 or later for Windows</li>
<li><strong>Not</strong> compatible with Gnu Compiler for Java (gcj)</li>
</ul>
</li>
</ul>
<p class="note"><strong>Note:</strong> If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In
particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development. </p>

103
docs/html/sdk/1.0_r2/upgrading.jd
View File

@@ -1,12 +1,37 @@
page.title=Upgrading the SDK
sdk.version=1.0_r2
@jd:body
<p>For the current SDK release, see the links under <strong>Current SDK Release</strong> in the side navigation.</p>
<div class="sidebox-wrapper">
<div class="sidebox-inner">
<h2>Useful Links</h2>
<ul class="noindent">
<li><a href="migrating/0.9-1.0/changes-overview.html">Overview of Changes</a>
<p>A high-level look at what's changed in Android, with
discussion of how the changes may affect your apps.</p></li>
<li><a href="migrating/0.9-1.0/changes.html">API Diff Report</a>
<p>A detailed report that lists all the specific changes in the latest SDK.</p></li>
<li><a href="RELEASENOTES.html">Release Notes</a>
<p>Version details, known issues, and resolved issues. </p></li>
<li><a href="http://groups.google.com/group/android-developers">Android Developers Group</a>
<p>A forum where you can discuss migration issues and learn from other Android developers. </p></li>
<li><a href="http://code.google.com/p/android/issues/list">Android Issue Tracker</a>
<p>If you think you may have found a bug, use the issue tracker to report it.</p></li>
</ul>
</div>
</div><!-- class-sidebox -->
<p>This guide will help you migrate your development environment and applications
to <strong>version 1.0, release 2</strong>, of the Android SDK. Use this guide if you've been developing applications
on a different version of the Android SDK.</p>
to the latest version of the SDK. Use this guide if you've been developing applications
on a previous version of the Android SDK.
</p>
<p>To ensure that your applications are compliant with the Android 1.0 system available
on mobile devices, you need to install the new SDK and port your existing Android
@@ -14,7 +39,9 @@ applications to the updated API. The sections below guide you through the proces
<h2 id="install-new">Install the new SDK</h2>
<p>After unpacking the SDK, you should:</p>
<p><a href="{@docRoot}download.html">Download the SDK</a> and unpack it into a safe location.</p>
<p>After unpacking the new SDK, you should:</p>
<ul>
<li>Wipe your emulator data. <p>Some data formats have changed since the last
@@ -33,58 +60,27 @@ applications to the updated API. The sections below guide you through the proces
<h2 id="update-plugin">Update your ADT Eclipse Plugin</h2>
<p>If you develop on Eclipse and are using the ADT plugin, follow these steps to install the
plugin that's required for this version of the SDK.</p>
<p>If you develop on Eclipse and are using the ADT plugin, follow these steps to install the new plugin that accompanies the latest SDK.</p>
<table style="font-size:100%">
<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr>
<tr>
<td width="45%">
<td width="50%">
<ol>
<li><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">Download the ADT v0.8.0 zip
file</a> (do not unpack it).</li>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find
and Install...</strong>. </li>
<li>In the dialog that appears, select <strong>Search for new features to install</strong> and click
<strong>Next</strong>. </li>
<li>Click <strong>New Archive Site...</strong></li>
<li>Browse and select the downloaded the zip file.</li>
<li>You should now see the new site added to the search list (and checked).
Click <strong>Finish</strong>. </li>
<li>In the subsequent Search Results dialog box, select the checkbox for
<strong>Android Plugin</strong> &gt; <strong>Developer Tools</strong>.
This will check both features: "Android Developer Tools", and "Android
Editors". The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>. </li>
<li>Read the license agreement and then select <strong>Accept terms of the license agreement</strong>.
Click <strong>Next</strong>. </li>
<li>Click <strong>Finish</strong>. </li>
<li>The ADT plugin is not signed; you can accept the installation anyway
by clicking <strong>Install All</strong>. </li>
<li>Restart Eclipse. </li>
<li> Select <strong>Help</strong> &gt; <strong>Software Updates</strong> &gt; <strong>Find and Install...</strong>. </li>
<li> Select <strong>Search for updates of the currently installed features</strong> and click <strong>Finish</strong>. </li>
<li> If any update for ADT is available, select and install. </li>
<li> Restart Eclipse.</li>
</ol>
</td>
<td>
<ol>
<li><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">Download the ADT v0.8.0 zip
file</a> (do not unpack it).</li>
<li>Start Eclipse, then select <strong>Help</strong> &gt; <strong>Software Updates...</strong>.</li>
<li>In the dialog that appears, click the <strong>Available Software</strong> tab.</li>
<li>Click <strong>Add Site...</strong>, then <strong>Archive...</strong>.</li>
<li>Browse and select the downloaded the zip file.</li>
<li>Back in the Available Software view, you should see the plugin. Select the checkbox next to
<em>Developer Tools</em> and click <strong>Install...</strong></li>
<li>On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked.
The Android Editors feature is optional, but recommended. If
you choose to install it, you need the WST plugin mentioned earlier in this
page. Click <strong>Next</strong>.</li>
<li>Accept the license agreement and click <strong>Finish</strong>.</li>
<li>Restart Eclipse. </li>
<li>Select <strong>Help</strong> &gt; <strong>Software Updates...</strong></li>
<li>Select the <strong>Installed Software</strong> tab.</li>
<li>Click <strong>Update...</strong></li>
<li>If an update for ADT is available, select it and click <strong>Finish</strong>.</li>
<li>Restart Eclipse.</li>
</ol>
</td>
</tr>
</table>
@@ -103,7 +99,7 @@ plugin that's required for this version of the SDK.</p>
the ADT plugin and the Ant-based build tools support this requirement by signing compiled
.apk files with a debug key. To do so, the build tools use the Keytool utility included
in the JDK to to create a keystore and a key with a known alias and password. For more
information, see "Signing and Publishing Your App" in the documentation included with the SDK.
information, see <a href="{@docRoot}guide/publishing/app-signing.html">Signing Your Applications</a>.
<p>To support signing, you should first make sure that Keytool is available to the SDK build
tools. In most cases, you can tell the SDK build tools how to find Keytool by making sure that
@@ -137,7 +133,10 @@ to place 3rd jar files, which are now automatically handled by the Ant script.</
framework and API changes. You'll need to update your code to match changes in the Android APIs.</p>
<p>One way to start is to open your project in Eclipse and see where the ADT
identifies errors in your application.</p>
identifies errors in your application. From there, you can lookup
respective changes in the
<a href="migrating/changes-overview.html">Overview of Changes</a>
and <a href="migrating/changes.html">API Diffs Report</a>.</p>
<p>If you have additional trouble updating your code, visit the
<a href="http://groups.google.com/group/android-developers">Android Developers Group</a>
@@ -145,4 +144,8 @@ to seek help from other Android developers.</p>
<p>If you have modified one of the ApiDemos applications and would like to migrate it
to the new SDK, note that you will need to uninstall the version of ApiDemos that comes
preinstalled in the emulator.</p>
preinstalled in the emulator. For more information, or if you encounter an "reinstallation"
error when running or installing ApiDemos, see the troubleshooting topic
<a href="{@docRoot}guide/appendix/faq/troubleshooting.html#apidemosreinstall">I can't install ApiDemos
apps in my IDE because of a signing error</a> for information about how to solve the problem.</p>

12
docs/html/sdk/1.1_r1/index.jd
View File

@@ -4,16 +4,16 @@ sdk.version=1.1_r1
sdk.date=February 2009
sdk.win_download=android-sdk-windows-1.1_r1.zip
sdk.win_bytes=86038515
sdk.win_checksum=8c4b9080b430025370689e03d20842f3
sdk.win_bytes=84533935
sdk.win_checksum=4cec82e3d2c1658d73182e543d130a06
sdk.mac_download=android-sdk-mac_x86-1.1_r1.zip
sdk.mac_bytes=79046151
sdk.mac_checksum=becf0f1763d61eedce15d2a903d6c1dd
sdk.mac_bytes=78918508
sdk.mac_checksum=d67fb5f0eaf4f5a83dc985f5790940c6
sdk.linux_download=android-sdk-linux_x86-1.1_r1.zip
sdk.linux_bytes=79345522
sdk.linux_checksum=ebcb16b0cd4aef198b4dd9a1418efbf1
sdk.linux_bytes=79219171
sdk.linux_checksum=df88091c9f0ef6cc56cd92afcdad8d56
@jd:body

139
docs/html/sdk/1.1_r1/installing.jd
View File

@@ -4,43 +4,22 @@ sdk.version=1.1_r1
@jd:body
<p>This page describes how to install the Android SDK and set up your
development environment. If you haven't downloaded the SDK, you can
do so from the
<a href="{@docRoot}sdk/1.1_r1/index.html">Download</a> page.</p>
<p>This page describes how to install the Android 1.1 SDK, Release 1, and set up your development environment.
If you haven't downloaded the SDK yet, you can so from the <a href="{@docRoot}sdk/1.1_r1/index.html">Download</a> page.</p>
<p>If you encounter any problems during installation, see the
<a href="#installnotes">Installation Notes</a> at the bottom of
this page.</p>
<p>Before you begin, be sure that your development environment meets the SDK
<a href="{@docRoot}sdk/1.1_r1/requirements.html">System Requirements</a>. If you encounter any problems during installation,
see the <a href="#installnotes">Installation Notes</a> at the bottom of this page.</p>
<h4 style="margin-top">Upgrading?</h4>
<p>If you have already developed applications using an earlier version
of the SDK, please skip this page and read the
<a href="{@docRoot}sdk/1.1_r1/upgrading.html"><strong>Upgrading the
SDK</strong></a></b> document instead.
<p>If you have already developed applications using an earlier version of the
SDK, please skip this page and read the
<a href="{@docRoot}sdk/1.1_r1/upgrading.html"><strong>Upgrading the SDK</strong></a></b> document instead.
</p>
<h2 id="setup">Preparing for Installation</h2>
<p>Before you get started with the Android SDK, take a moment to confirm
that your development machine meets the <a
href="{@docRoot}sdk/1.1_r1/requirements.html">system requirements</a>.
</p>
<p>If you will be developing on Eclipse with the Android Development
Tools (ADT) Plugin &mdash; the recommended path if you are new to
Android &mdash; make sure that you have a suitable version of Eclipse
installed on your computer. If you need to install Eclipse, you can
download it from this location: </p>
<p style="margin-left:2em;"><a href=
"http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a
></p>
<p>A Java or RCP version of Eclipse is recommended. </p>
<h2 id="installingsdk">Installing the SDK</h2>
<a name="installingsdk"></a>
<a name="setup"></a>
<h2>Installing the SDK</h2>
<p>After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named <code>android_sdk_<em>&lt;platform</em>&gt;_<em>&lt;release&gt;</em>_<em>&lt;build&gt;</em></code>. The directory contains a link to a local copy of the documentation and the subdirectories <code>tools/</code>, <code>samples/</code>, and others. </p>
@@ -68,34 +47,16 @@ download it from this location: </p>
<p>If you will be using the Eclipse IDE as your environment for developing Android applications, continue reading the next
section in order to install the Android Development Tools plugin and set up Eclipse. If you choose not to use Eclipse, you can
section in order to install the Android Development Tools plugin and setup Eclipse. If you choose not to use Eclipse, you can
develop Android applications using other tools &mdash; read the guide to developing
<a href="{@docRoot}guide/developing/other-ide.html">in other IDEs</a>.</p>
<a href="{@docRoot}guide/developing/other-ide.html">In other IDEs</a>.</p>
<h2 id="installingplugin">Installing the ADT Plugin for Eclipse</h2>
<h2>Setting up Eclipse</h2>
<p>Android offers a custom plugin for the Eclipse IDE, called Android
Development Tools (ADT), that is designed to give you a powerful,
integrated environment in which to build Android applications. It
extends the capabilites of Eclipse to let you quickly set up new Android
projects, create an application UI, add components based on the Android
Framework API, and debug using the Android SDK tools.</p>
<p>First, you should install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.</p>
<p>If you are new to Android or want to develop using the Eclipse IDE,
the ADT plugin will be an essential part of your development
environment. In general, using Eclipse with ADT is a highly recommended
approach and is the fastest way to get started. This section describes
how to install ADT into your Eclipse environment.
<p>If you prefer to work in a development environment other than Eclipse,
you do not need to install Eclipse or the ADT Plugin. Instead, you can
access the SDK tools directly to build and debug your application. </p>
<p>Once you have Eclipse installed, as described in <a href="#setup">
Preparing for Installation</a>, follow the steps below to
download the ADT plugin and install it in your respective Eclipse
environment. </p>
<p>To download and install the ADT plugin, follow the steps below for your respective Eclipse version. </p>
<table style="font-size:100%">
<tr><th>Eclipse 3.3 (Europa)</th><th>Eclipse 3.4 (Ganymede)</th></tr>
@@ -162,6 +123,7 @@ environment. </p>
</tr>
</table>
<p>Now, you just need to modify your Eclipse preferences to point to the Android SDK directory:</p>
<ol>
<li>Select <strong>Window</strong> &gt; <strong>Preferences...</strong> to open the Preferences
@@ -171,9 +133,9 @@ environment. </p>
<li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li>
</ol>
<p>Done! If you haven't encountered any problems, then you're ready to
begin developing Android applications. See the <a href="#next">After
Installation: Next Steps</a> section for suggestions on how to start. </p>
<p>Done! If you haven't encountered any problems, then you're ready to begin developing Android applications.
We recommend you begin with the <a href="{@docRoot}guide/tutorials/hello-world.html">Hello World</a> tutorial,
which will teach you some basics about Android applications and how to create projects using Eclipse.</p>
<h3 id="troubleshooting">Troubleshooting ADT Installation</h3>
@@ -220,59 +182,8 @@ JKS</pre>
Java 6 will resolve this issue and you can then reinstall the ADT
Plugin.</p>
<h2 id="next">After Installation: Next Steps</h2>
<p>Once you have installed the SDK and the ADT Plugin, you are ready to
begin developing applications. Here are a few ways you can get started: </p>
<p><strong>Learn about Android</strong></p>
<ul>
<li>Take a look at the <a href="{@docRoot}guide/index.html">Dev
Guide</a> and the types of information it provides</li>
<li>Read an introduction to Android as a platform in <a
href="{@docRoot}guide/basics/what-is-android.html">What is
Android?</a></li>
<li>Learn about the Android framework and how applications run on it in
<a href="{@docRoot}guide/topics/fundamentals.html">Application
Fundamentals</a></li>
<li>Take a look at the Android framework API specification in the <a
href="{@docRoot}reference/index.html">Reference</a> tab</li>
</ul>
<p><strong>Explore the SDK</strong></p>
<ul>
<li>Get an overview of the <a
href="{@docRoot}guide/development/tools/index.html">development
tools</a> that are available to you</li>
<li>Read the overviews of how to develop <a
href="{@docRoot}guide/developing/eclipse-adt.html">in Eclipse/ADT</a> or
<a href="{@docRoot}guide/developing/other-ide.html">in other IDEs</a>
</li>
</ul>
<p><strong>Explore some code</strong></p>
<ul>
<li>Set up a <a href="{@docRoot}guide/tutorials/hello-world.html">Hello
World application</a></li>
<li>Follow the <a href="{@docRoot}guide/tutorials/notepad/index.html">
Notepad Tutorial</a> to build a full Android application </li>
<li>Create a new project for one of the other sample applications
included in <code>&lt;sdk&gt;/samples</code>, then compile and run it in
your development environment</li>
</ul>
<p><strong>Visit the Android developer groups</strong></p>
<ul>
<li>Take a look at the <a
href="{@docRoot}community/index.html">Community</a> tab to see a list of
Android developers groups. In particular, you might want to look at the
<a href="http://groups.google.com/group/android-developers">Android
Developers</a> group to get a sense for what the Android developer
community is like.</li>
</ul>
<h2 id="installnotes">Installation Notes</h2>
<a name="installnotes"></a>
<h2>Installation Notes</h2>
<h4>Ubuntu Linux Notes</h4>
<ul>
<li>If you need help installing and configuring Java on your
@@ -304,9 +215,9 @@ and the ADT plugin. </li>
<ul>
<li>If JDK is already installed on your development computer, please
take a moment to make sure that it meets the version requirements listed
in the <a href="{@docRoot}sdk/1.1_r1/requirements.html">System Requirements</a>.
In particular, note that some Linux distributions may include JDK 1.4 or Gnu
Compiler for Java, both of which are not supported for Android development.</li>
at the top of this page. In particular, note that some Linux
distributions may include JDK 1.4 or Gnu Compiler for Java, both of
which are not supported for Android development.</li>
</ul>

44
docs/html/sdk/sdk_toc.cs
View File

@@ -1,42 +1,26 @@
<ul>
<li><?cs
if:android.whichdoc != "online" ?>
<h2>Android 1.1 SDK, r1</h2><?cs
else ?>
<h2>Current SDK Release</h2><?cs
/if ?>
<ul><?cs
if:android.whichdoc == "online" ?>
<li><a href="<?cs var:toroot ?>sdk/1.1_r1/index.html">Download</a></li><?cs
/if ?>
<li>
<?cs if:android.whichdoc != "online" ?><h2>Android 1.1 SDK, r1</h2>
<?cs else ?><h2>Latest SDK Release</h2><?cs /if ?>
<ul>
<?cs if:android.whichdoc == "online" ?>
<li><a href="<?cs var:toroot ?>sdk/1.1_r1/index.html">Download</a></li>
<?cs /if ?>
<li><a href="<?cs var:toroot ?>sdk/1.1_r1/installing.html">Installing</a></li>
<li><a href="<?cs var:toroot ?>sdk/1.1_r1/upgrading.html">Upgrading</a></li>
<li><a href="<?cs var:toroot ?>sdk/1.1_r1/requirements.html">System Requirements</a></li>
</ul>
<ul>
<li><a href="<?cs var:toroot ?>sdk/terms.html">SDK Terms and Conditions</a></li>
<li><a href="<?cs var:toroot ?>sdk/RELEASENOTES.html">SDK Release Notes</a></li>
</ul><?cs
if:android.whichdoc == "online" ?>
<li>
<h2>Android System Images</h2>
</ul>
<ul>
<li><a href="<?cs var:toroot ?>sdk/android-1.1.html">Android 1.1 Version Notes</a></li>
</ul>
</li>
<li>
<h2>Previous SDK Releases</h2>
<ul>
<li><a href="<?cs var:toroot ?>sdk/1.0_r2/index.html">Android 1.0 SDK, release 2</a></li>
<li><a href="<?cs var:toroot ?>sdk/1.0_r1/index.html">Android 1.0 SDK, release 1</a></li>
</ul>
</li><?cs
/if ?>
</ul>
<ul>
<li><a href="<?cs var:toroot ?>sdk/terms.html">SDK Terms and Conditions</a></li>
<?cs if:android.whichdoc == "online" ?>
<li><a href="http://code.google.com/android/download_list.html">Previous SDK Releases</a></li>
<?cs /if ?>
</ul>
<script type="text/javascript">
<!--
buildToggleLists();
//-->
</script>

68
docs/html/search.jd
View File

@@ -1,8 +1,8 @@
page.title=Search Results
@jd:body
<script src="http://www.google.com/jsapi" type="text/javascript"></script>
<script src="/assets/jquery-history.js" type="text/javascript"></script>
<script type="text/javascript">
google.load('search', '1');
@@ -20,80 +20,36 @@ page.title=Search Results
// configure search result options
searchOptions = new google.search.SearcherOptions();
searchOptions.setExpandMode(GSearchControl.EXPAND_MODE_OPEN);
searchOptions.setRoot(document.getElementById("leftSearchControl"));
// configure each of the searchers, for each tab
devSiteSearcher = new google.search.WebSearch();
devSiteSearcher.setUserDefinedLabel("All Developers Site");
devSiteSearcher.setSiteRestriction("http://developer.android.com/");
devGuideSearcher = new google.search.WebSearch();
devGuideSearcher.setUserDefinedLabel("Dev Guide");
devGuideSearcher.setSiteRestriction("http://developer.android.com/guide/");
referenceSearcher = new google.search.WebSearch();
referenceSearcher.setUserDefinedLabel("Reference");
referenceSearcher.setSiteRestriction("http://developer.android.com/reference/");
blogSearcher = new google.search.WebSearch();
blogSearcher.setUserDefinedLabel("Blog");
blogSearcher.setSiteRestriction("http://android-developers.blogspot.com");
groupsSearcher = new google.search.WebSearch();
groupsSearcher.setUserDefinedLabel("Developer Groups");
groupsSearcher.setSiteRestriction("001283715400630100512:ggqrtvkztwm");
sourceSiteSearcher = new google.search.WebSearch();
sourceSiteSearcher.setUserDefinedLabel("Android Source");
sourceSiteSearcher.setSiteRestriction("http://source.android.com");
homeSiteSearcher = new google.search.WebSearch();
homeSiteSearcher.setUserDefinedLabel("Android Home");
homeSiteSearcher.setSiteRestriction("http://www.android.com");
// configure searcher options
searcher = new google.search.WebSearch();
searcher.setUserDefinedLabel("Android Developers");
searcher.setSiteRestriction("001283715400630100512:ggqrtvkztwm");
// add each searcher to the search control
searchControl.addSearcher(devSiteSearcher, searchOptions);
searchControl.addSearcher(devGuideSearcher, searchOptions);
searchControl.addSearcher(referenceSearcher, searchOptions);
searchControl.addSearcher(groupsSearcher, searchOptions);
searchControl.addSearcher(sourceSiteSearcher, searchOptions);
searchControl.addSearcher(blogSearcher, searchOptions);
// configure result options
searchControl.addSearcher(searcher, searchOptions);
searchControl.setResultSetSize(google.search.Search.LARGE_RESULTSET);
searchControl.setLinkTarget(google.search.Search.LINK_TARGET_SELF);
searchControl.setTimeoutInterval(google.search.SearchControl.TIMEOUT_LONG);
searchControl.setNoResultsString(google.search.SearchControl.NO_RESULTS_DEFAULT_STRING);
// upon ajax search, refresh the url and search title
searchControl.setSearchStartingCallback(this, function(control, searcher, query) {
$("#searchTitle").html("search results for <em>" + query + "</em>");
$.history.add('q=' + query); // add the current query to the browser history
temp = location.href.split('#');
url = temp ? temp[0] : location.href;
location.href = url + '#q=' + query;
document.getElementById("searchTitle").innerHTML = "search results for <em>" + query + "</em>"
});
// draw the search results box
searchControl.draw(document.getElementById("leftSearchControl"), drawOptions);
searchControl.draw(null, drawOptions);
// execute a search upon page load, from url hash query
if (location.href.indexOf("#q=") != -1) {
url = location.href.split("#q=");
searchControl.execute(decodeURI(url[1]));
}
document.getElementById("search_autocomplete").focus();
}
google.setOnLoadCallback(OnLoad, true);
// when an event on the browser history occurs (back, forward, load) perform a search
$(window).history(function(e, hash) {
hashParts = hash.split('=');
searchControl.execute(decodeURI(hashParts[1]));
$("#searchTitle").html("search results for <em>" + decodeURI(hashParts[1]) + "</em>");
});
// forcefully regain key-up event control (previously jacked by search api)
$("#search_autocomplete").keyup(function(event) {
return search_changed(event, false, '/');
});
</script>
<div id="mainBodyFixed" style="width:auto; margin:20px">

5444
docs/html/sitemap.txt
View File

File diff suppressed because it is too large Load Diff