diff options
Diffstat (limited to 'docs/html/sdk')
| -rw-r--r-- | docs/html/sdk/1.1_r1/index.jd | 16 | ||||
| -rw-r--r-- | docs/html/sdk/1.1_r1/installing.jd | 43 | ||||
| -rw-r--r-- | docs/html/sdk/1.1_r1/upgrading.jd | 51 | ||||
| -rw-r--r-- | docs/html/sdk/RELEASENOTES.jd | 199 | ||||
| -rw-r--r-- | docs/html/sdk/android-1.1.jd | 13 | ||||
| -rw-r--r-- | docs/html/sdk/download.jd | 48 | ||||
| -rw-r--r-- | docs/html/sdk/sdk_toc.cs | 12 | ||||
| -rw-r--r-- | docs/html/sdk/terms.jd | 2 |
8 files changed, 280 insertions, 104 deletions
diff --git a/docs/html/sdk/1.1_r1/index.jd b/docs/html/sdk/1.1_r1/index.jd index b516acb..7e70b6b 100644 --- a/docs/html/sdk/1.1_r1/index.jd +++ b/docs/html/sdk/1.1_r1/index.jd @@ -1,19 +1,19 @@ -page.title=Download Android 1.1 SDK, Release 1 +page.title=Android 1.1 SDK, Release 1 sdk.version=1.1_r1 sdk.date=February 2009 sdk.win_download=android-sdk-windows-1.1_r1.zip -sdk.win_bytes=unknown -sdk.win_checksum=unknown +sdk.win_bytes=84533935 +sdk.win_checksum=4cec82e3d2c1658d73182e543d130a06 sdk.mac_download=android-sdk-mac_x86-1.1_r1.zip -sdk.mac_bytes=unknown -sdk.mac_checksum=unknown +sdk.mac_bytes=78918508 +sdk.mac_checksum=d67fb5f0eaf4f5a83dc985f5790940c6 sdk.linux_download=android-sdk-linux_x86-1.1_r1.zip -sdk.linux_bytes=unknown -sdk.linux_checksum=unknown +sdk.linux_bytes=79219171 +sdk.linux_checksum=df88091c9f0ef6cc56cd92afcdad8d56 @jd:body @@ -57,6 +57,6 @@ in the <code><sdk>/samples/</code> directory of the SDK package.</p> <p>The most current documentation is always available on the Android Developers site:</p> -<p style="margin-left:2em;"><a href="ttp://developer.android.com/index.html">http://developer.android.com/</a></p> +<p style="margin-left:2em;"><a href="http://developer.android.com/index.html">http://developer.android.com/</a></p> diff --git a/docs/html/sdk/1.1_r1/installing.jd b/docs/html/sdk/1.1_r1/installing.jd index 1319237..b198800 100644 --- a/docs/html/sdk/1.1_r1/installing.jd +++ b/docs/html/sdk/1.1_r1/installing.jd @@ -5,10 +5,11 @@ sdk.version=1.1_r1 <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 so from the <a href="{@docRoot}sdk/1.1_r1/index.html">Download</a> page.</p> +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>Before you begin, be sure that your development environment meets the SDK -<a href="{@docRoot}sdk/1.1_r1/requirements.html">System Requirements</a>.</p> +<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 @@ -20,7 +21,7 @@ SDK, please skip this page and read the <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><platform</em>>_<em><release></em>_<em><build></em></code>. The directory contains 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><platform</em>>_<em><release></em>_<em><build></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>Make a note of the name and location of the unpacked SDK directory on your system — you will need to refer to the SDK directory later, when setting up the Android plugin or using SDK tools. </p> @@ -44,25 +45,16 @@ 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> -<h2>Setting up Eclipse</h2> -<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> > <strong>Preferences...</strong> to open the Preferences - panel. (Mac OS X: <strong>Eclipse</strong> > <strong>Preferences</strong>) </li> - <li>Select <strong>Android</strong> from the left panel. </li> - <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>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 — read the guide to developing +<a href="{@docRoot}guide/developing/other-ide.html">In other IDEs</a>.</p> -<h2 id="installingplugin">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. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.</p> +<h2>Setting up Eclipse</h2> -<p>If you <em>will not</em> be using the Eclipse IDE, you do not need to download or install the ADT plugin. You can still develop Android applications using other 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>To download and install the ADT plugin, follow the steps below for your respective Eclipse version. </p> @@ -131,6 +123,21 @@ to use the Android SDK.</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> > <strong>Preferences...</strong> to open the Preferences + panel. (Mac OS X: <strong>Eclipse</strong> > <strong>Preferences</strong>) </li> + <li>Select <strong>Android</strong> from the left panel. </li> + <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! 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> <p> If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions: </p> diff --git a/docs/html/sdk/1.1_r1/upgrading.jd b/docs/html/sdk/1.1_r1/upgrading.jd index aa7c3a5..2ad6757 100644 --- a/docs/html/sdk/1.1_r1/upgrading.jd +++ b/docs/html/sdk/1.1_r1/upgrading.jd @@ -30,7 +30,7 @@ sdk.version=1.1_r1 </div> --> -<p>This document describes how to move your devlopment environment and existing +<p>This document describes how to move your development environment and existing Android applications from an Android 1.0 SDK to the Android 1.1, Release 1 SDK. If you are migrating applications from an earlier SDK, please read the upgrading document available in the Android 1.0 SDK package. @@ -38,18 +38,18 @@ document available in the Android 1.0 SDK package. <p>To ensure that your applications are compliant with the Android 1.1 system available on mobile devices, you need to install the Android 1.1 SDK and port your existing Android -applications to it. The sections below guide you through the process.</p> +applications to it. The sections below will guide you through the process.</p> <h2 id="install-new">Installing the Latest SDK</h2> <p><a href="{@docRoot}sdk/1.1_r1/index.html">Download the SDK</a> and unpack it into a safe location.</p> -<p>After unpacking the new SDK, you should:</p> +<p>After unpacking the new SDK and saving it an appropriate location, you should:</p> <ul> <li>Wipe your emulator data. <p>Some data formats have changed since the last SDK release, so any previously saved data in your emulator must be removed. Open a console/terminal - and navigate to the <code>/tools</code> directory of your SDK. Launch the + and navigate to the <code>/tools</code> directory of your new SDK. Launch the emulator with the <code>-wipe-data</code> option. <p>Windows: <code>emulator -wipe-data</code><br/> Mac/Linux: <code>./emulator -wipe-data</code></p> @@ -71,7 +71,7 @@ applications to it. The sections below guide you through the process.</p> <h2 id="update-plugin">Update your ADT Eclipse Plugin</h2> <p>If you develop on Eclipse and are migrating from an Android 1.0 -SDK, no update of the ADT plugin is needed. </p> +SDK, no update of the ADT plugin is needed — skip to <a href="#updateEclipsePrefs">Update your Eclipse SDK Preferences</a>. </p> <p>If you are migrating from an earlier version of the SDK, you will need to update the ADT plugin. <p>You may also want to upgrade your @@ -111,7 +111,9 @@ version available. </p> </tr> </table> -<p>After restart, update your Eclipse preferences to point to the SDK directory:</p> +<h2 id="updateEclipsePrefs">Update your Eclipse SDK Preferences</h2> + +<p>The last step is to update your Eclipse preferences to point to the new SDK directory:</p> <ol> <li>Select <strong>Window</strong> > <strong>Preferences...</strong> to open the Preferences panel. (Mac OSX: <strong>Eclipse</strong> > <strong>Preferences</strong>)</li> <li>Select <strong>Android</strong> from the left panel.</li> @@ -119,43 +121,6 @@ version available. </p> <li>Click <strong>Apply</strong>, then <strong>OK</strong>.</li> </ol> - -<!-- -<h2 id="sign">Set Up Application Signing</h2> - -<p>All applications must now be signed before you can install them on the emulator. Both -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 <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 -your JAVA_HOME environment variable is set and that it references a suitable JDK. Alternatively, -you can add the JDK version of Keytool to your PATH variable.</p> - -<p>If you are developing on a version of Linux that originally came with Gnu Compiler for Java, -make sure that the system is using the JDK version of Keytool, rather than the gcj version. -If keytool is already in your PATH, it might be pointing to a symlink at /usr/bin/keytool. -In this case, check the symlink target to make sure that it points to the keytool in the JDK.</p> - -<p>If (and only if) you use Ant to build your .apk files (rather than ADT for Eclipse), you must regenerate -your build.xml file. To do that, follow these steps:</p> -<ol> - <li>In your Android application project directory, locate and delete the current build.xml file.</li> - <li>Run activitycreator, directing output to the folder containing your application project. - -<pre>- exec activitycreator --out <project folder> your.activity.YourActivity</pre> - - </li> -</ol> - -<p>Run in this way, activitycreator will not erase or create new Java files (or manifest files), -provided the activity and package already exists. It is important that the package and the activity -are real. The tool creates a new build.xml file, as well as a new directory called "libs" in which -to place 3rd jar files, which are now automatically handled by the Ant script.</p> ---> - <h2 id="migrate">Migrate Your Applications, if Necessary</h2> <p>If (and only if) you have written apps in an SDK released previous to diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd index 6e0716c..bad71a2 100644 --- a/docs/html/sdk/RELEASENOTES.jd +++ b/docs/html/sdk/RELEASENOTES.jd @@ -1,10 +1,9 @@ page.title=SDK Release Notes -sdk.version=1.1_r1 @jd:body <p>This document provides version-specific information about Android SDK releases. For the latest known issues, please ensure that you're viewing this page at: <a href="http://developer.android.com/sdk/RELEASENOTES.html">http://developer.android.com/sdk/RELEASENOTES.html</a>.</p> -<h2>Android 1.1 SDK, Release 1</h2> +<h2 id="1.1_r1">Android 1.1 SDK, Release 1</h2> <p>This SDK provides the development tools and Android system image you need to create applications for Android-powered devices. Applications developed on this SDK will be compatible with mobile devices running the Android 1.1 platform. </p> @@ -20,14 +19,14 @@ sdk.version=1.1_r1 <pre><code><manifest> ... - <uses-sdk minSdkVersion="2"> + <uses-sdk minSdkVersion="2" /> ... </manifest></code> </pre> <p>By setting <code>android:minSdkVersion</code> in this way, you ensure that users will only be able to install your application if their devices are running the Android 1.1 platform. In turn, this ensures that your application will function properly on their devices, especially if it uses APIs introduced in Android 1.1. </p> -<p>If your application uses APIs introduced in Android 1.1 but does not declare <code><uses-sdk minSdkVersion="2"></code>, then it will run properly on Android 1.1 devices but <em>not</em> on Android 1.0 devices. </p> +<p>If your application uses APIs introduced in Android 1.1 but does not declare <code><uses-sdk minSdkVersion="2" /></code>, then it will run properly on Android 1.1 devices but <em>not</em> on Android 1.0 devices. </p> <p>If your application does not use any new APIs introduced in Android 1.1, you can indicate Android 1.0 compatibility by removing <code>minSdkVersion</code> or setting the attribute to "1". However, before publishing your application, you must make sure to compile your application against the Android 1.0 system image (available in the Android 1.0 SDK), to ensure that it builds and functions properly for Android 1.0 devices. You should test the application against system images corresponding to the API Levels that the application is designed to be compatible with.</p> @@ -115,7 +114,196 @@ in Eclipse</a>.</li> <li>It is not possible to send MMS messages between emulator instances. </li> <li>In some cases, you may encounter problems when using the browser on an emulator started with the command-line option <code>-http-proxy</code>. </li> -<li>We regret to inform developers that Android 1.1 will not include support for +<li>On the OSX platform, if you manually remove the ~/.android directory +using <code>rm -rf ~/.android</code>, then try to run +the emulator, it crashes. This happens because the emulator fails to create +a new .android directory before attempting to create the child SDK1.0 directory. +To work around this issue, manually create a new .android directory using +<code>mkdir ~/.android</code>, then run the emulator. The emulator +creates the SDK1.0 directory and starts normally. </li> +<li>We regret to inform developers that Android 1.1 will not include support +for ARCNet network interfaces.</li> +<li>The final set of Intent patterns honored by Android 1.0 has not yet been +fully documented. Documentation will be provided in future releases.</li> +<li>In ADT Editor, you can add at most ten new resource values at a time, +in a given res/values/*.xml, using the form in the Android Resources pane. +If you add more than ten, the Android Resources pane will not display the +attributes fields for the additional resource entries. To work around this +problem, you can close the file in the editor and open it again, or you +can edit the resource entries in the XML text mode. </li> +<li>The emulator's battery-control commands (<code>power <option></code>) +are not working in this release.</li> +</ul> + + + + + +<h2 id="1.0_r2">Android 1.0 SDK, Release 2</h2> + +<p>This SDK release includes the Android 1.0 platform and application API. +Applications developed on this SDK will be compatible with mobile devices +running the Android 1.0 platform.</p> + +<p>This release includes mainly bug fixes, although some smaller features were +added.</p> + +<h3>ADT Plugin Compatibility</h3> + +<p>For this release of the SDK, the compatible version of the Android +Development Tools (ADT) Plugin for Eclipse is <strong>0.8.0</strong>. If you are +using a previous version of ADT, you should update to the latest version for use +with this SDK. For information about how to update your ADT plugin, see <a +href="/android/intro/upgrading.html">Upgrading the SDK</a>.</p> + +<h3>Installation and Upgrade Notes</h3> + +<p>If you're installing the Android SDK for the first time, please see the +instructions in <a href="/android/intro/installing.html">Installing the +SDK</a>. + +<h3>Other Notes</h3> + +<p><strong>T-Mobile G1 Compatability</strong></p> + +<p>This version of the SDK has been tested for compatability with the first +Android-powered mobile device, the <a href="http://www.t-mobileg1.com">T-Mobile +G1</a>. </p> + +<p><strong>MapView API Key</strong></p> + +<p>MapView is a class that lets you easily integrate Google Maps into your +application. Before you can access the maps data, you will need to register with +the Google Maps service and receive a Maps API Key, which you then add to your +MapView for authentication to the server.</p> + +<p>Developers should note that the registration service for MapView is now +active and Google Maps is actively enforcing the Maps API Key requirement. For +information about how to register for a Maps API Key, see <a +href="http://code.google.com/android/toolbox/apis/mapkey.html">http://code. +google.com/android/toolbox/apis/mapkey.html</a>.</p> + +<p><strong>USB Driver for Windows</strong></p> +<p>If you using Windows and want to develop or test your application on an +Android-powered device (such as the T-Mobile G1), you need an appropriate USB +driver. For your convenience, the Windows version of the Android SDK includes a +USB driver that you can install, to let you develop on the device. The USB +driver files are located in the <code><SDK>/usb_driver</code> directory. + +</p> + +<h3>Resolved Issues, Changes</h3> +<ul> +<li>The android.jar in this SDK release now includes several classes that were +missing from the previous SDK. </li> +<li>The android.R.styleable class and its fields were removed from the public +API, to better ensure forward-compatibility for applications. The constants +declared in android.R.styleable were platform-specific and subject to arbitrary +change across versions, so were not suitable for use by applications. You can +still access the platform's styleable attributes from your resources or code. To +do so, declare a custom resource element using a +<code><declare-styleable></code> in your project's res/values/R.attrs +file, then declare the attribute inside. For examples, see +<sdk>/samples/ApiDemos/res/values/attrs.xml. For more information about +custom resources, see <a +href="/android/reference/available-resources.html#customresources">Custom +Layout Resources</a>. Note that the android.R.styleable documentation is still +provided in the SDK, but only as a reference of the platform's styleable +attributes for the various elements.</li> +<li>The VM now properly ensures that private classes are not +available to applications through reflection. If you were using reflection +to access private classes in a previous release, you will now get a run-time +error. </li> + +<li>The Settings and Email applications are now included in the SDK and +available in the emulator.</li> +<li>We regret to inform developers that SDK 1.0_r2 does not support MFM, RLL, +or Winchester hard disk drives.</li> +<li>In the emulator, the control key for enabling/disabling trackball mode +is changed from Control-T to F6. You can also enter trackball mode temporarily +using the Delete key. While the key is pressed, you can send trackball events.</li> +</ul> + +<p>Unless otherwise noted, Known Issues from the previous SDK release also apply +to this release.</p> + + + + + + +<h2 id="1.0_r1">Android 1.0 SDK, Release 1</h2> + +<p>This SDK release is the first to include the Android 1.0 platform and application API. Applications developed on this SDK will be compatible with mobile devices running the Android 1.0 platform, when such devices are available.</p> + +<p>This release includes mainly bug fixes, although some smaller features were added. The Android 1.0 also includes several API changes from the 0.9 version. For more information on API changes, see the <a href="/android/migrating/0.9-1.0/changes-overview.html">Overview of Changes</a> and the <a href="/android/migrating/0.9-1.0/changes.html">API Differences Report</a>. For those porting from the M5 release, the SDK also includes the legacy changes overview and API Differences Reports. See the current Overview of Changes for more information. </p> + +<h3>ADT Plugin Compatibility</h3> + +<p>For this version of the SDK — Android 1.0 SDK, Release 1 — the compatible version of the Android Development Tools (ADT) Plugin for Eclipse is <strong>0.8.0</strong>. If you are using a previous version of ADT, you should update to the latest version for use with this SDK. For information about how to update your ADT plugin, see <a href="/android/intro/upgrading.html">Upgrading the SDK</a>.</p> + +<h3>Installation and Upgrade Notes</h3> + +<p>If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Please see <a href="/android/intro/upgrading.html">Upgrading the SDK</a> for detailed instructions on how to make the transition to this release. Be sure to wipe application user data (emulator option <code>-wipe-data</code>) when running your application on the Android 1.0 SDK emulator.</p> + +<p>If you're installing the Android SDK for the first time, please see the instructions in <a href="/android/intro/installing.html">Installing the SDK</a>. + +<h3>Other Notes</h3> + +<p><strong>MapView API Key</strong></p> + +<p><a href="/android/reference/com/google/android/maps/MapView.html">MapView</a> is a class that lets you easily integrate Google Maps into your application. Before you can access the maps data, you will need to register with the Google Maps service and receive a Maps API Key, which you then add to your MapView for authentication to the server.</p> + +<p>Currently, the registration service for MapView is not yet active and Google Maps is not yet enforcing the Maps API Key requirement. However, note that the registration service will be activated soon, so that MapViews in any application deployed to a mobile device will require registration and a valid Maps API Key. </p> + +<p>As soon as the registration service becomes available, we will update the page at <a href="http://code.google.com/android/toolbox/apis/mapkey.html">http://code.google.com/android/toolbox/apis/mapkey.html</a> with details about how and where to register. Please check that page periodically for registration information, if you are using a MapView.</p> + + +<h3>Resolved Issues, Changes</h3> + +<p><strong>Emulator</strong></p> +<ul> +<li>Emulator now saves the user image in <android>/SDK1.0/</code></li> +<li>Fixed EsounD-related freezes on Linux.</li> +<li>Fixed the documentation in -help-audio. '-audio list' doesn't work, one + needs to call -help-audio-out and -help-audio-in to get the list of valid + audio backends.</li> +<li>Fixed scrollwheel Dpad emulation in rotated mode. before that, using the + scroll-wheel would always generated Dpad Up/Down events, even when in + landscape mode.</li> + +<li>Several Obsolete command options were removed.</li> +<li>Setting the network speed through the console or the -netspeed option will + properly modify the connectivity icon on the device.</li> +<li>Setting the GSM voice registration state to 'roaming' in the console will + properly modify the voice icon on the device</li> +</ul> + +<p><strong>SQLite</strong></p> +<ul> +<li>SQLite is now included in the SDK package on all platforms. </li> +</ul> + +<h3>Known Issues</h3> + +<p><strong>JUnit and Eclipse/ADT</strong></p> +<ul> +<li>If you are developing in Eclipse/ADT and want to add JUnit test +classes, you can do so. However, you need to set up a custom JUnit configuration +before your tests will run properly. For detailed information about how to set +up the JUnit configuration, see the troubleshooting topic <a +href="/android/kb/troubleshooting.html#addjunit">Running a Junit test class +in Eclipse</a>.</li> +</ul> + +<p><strong>Other</strong></p> + +<ul> +<li>It is not possible to send MMS messages between emulator instances. </li> +<li>In some cases, you may encounter problems when using the browser on an +emulator started with the command-line option <code>-http-proxy</code>. </li> + +<li>We regret to inform developers that Android 1.0 will not include support for dot-matrix printers.</li> <li>On the OSX platform, if you manually remove the ~/.android directory using <code>rm -rf ~/.android</code>, then try to run @@ -134,5 +322,6 @@ problem, you can close the file in the editor and open it again, or you can edit the resource entries in the XML text mode. </li> <li>The emulator's battery-control commands (<code>power <option></code>) are not working in this release.</li> + </ul> diff --git a/docs/html/sdk/android-1.1.jd b/docs/html/sdk/android-1.1.jd index 8e63ba3..f70ad26 100644 --- a/docs/html/sdk/android-1.1.jd +++ b/docs/html/sdk/android-1.1.jd @@ -59,7 +59,7 @@ attribute looks like this: </p> <pre><code><manifest> ... - <uses-sdk minSdkVersion="2"> + <uses-sdk minSdkVersion="2" /> ... </manifest></code> </pre> @@ -71,7 +71,7 @@ your application will function properly on their devices, especially if it uses <a href="#apichange">APIs introduced in Android 1.1</a>. </p> <p>If your application uses APIs introduced in Android 1.1 but does not -declare <code><uses-sdk minSdkVersion="2"></code>, then it will +declare <code><uses-sdk minSdkVersion="2" /></code>, then it will run properly on Android 1.1 devices but <em>not</em> on Android 1.0 devices. In the latter case, the application will crash at runtime when it tries to use the Android 1.1 APIs.</p> @@ -175,14 +175,13 @@ AM/PM).</li> <li>Improves recovery from POP3 connection failures.</li> <li>POP3 parser rules loosened, so the application can work with non-compliant email servers.</li> -<li>Removes green CALL button as a shortcut for "add a new call".</li> </ul> <h2 id="features">New Features</h2> <ul> <li>Maps: Adds details and reviews when a user does a search on Maps and -clicks on a business to view it's details.</li> +clicks on a business to view its details.</li> <li>Dialer: In-call screen timeout default is now longer when using the speakerphone.</li> <li>Dialer: Adds a "Show dialpad" / "Hide dialpad" item to the in-call @@ -216,9 +215,9 @@ SDK-bound system images. </li> <th>Module or Feature</th><th>Change Description</th> </tr> <tr><td rowspan="4">Annotations for test systems</td></tr> - <tr><td>Added class {@link android.test.suitebuilder.annotation.LargeTest LargeTest} to package {@link android.test.suitebuilder.annotation}</td></tr> - <tr><td>Added class {@link android.test.suitebuilder.annotation.MediumTest MediumTest} to package {@link android.test.suitebuilder.annotation}</td></tr> - <tr><td>Added class {@link android.test.suitebuilder.annotation.SmallTest SmallTest} to package {@link android.test.suitebuilder.annotation}</td></tr> + <tr><td>Added {@link android.test.suitebuilder.annotation.LargeTest LargeTest} annotation.</td></tr> + <tr><td>Added {@link android.test.suitebuilder.annotation.MediumTest MediumTest} annotation.</td></tr> + <tr><td>Added {@link android.test.suitebuilder.annotation.SmallTest SmallTest} annotation.</td></tr> <tr><td rowspan="2">Allow a process to easily know its UID.</td></tr> <tr><td>Added public method {@link android.os.Process#myUid} to class {@link android.os.Process android.os.Process}</td></tr> diff --git a/docs/html/sdk/download.jd b/docs/html/sdk/download.jd index d64b781..3c4f06b 100644 --- a/docs/html/sdk/download.jd +++ b/docs/html/sdk/download.jd @@ -1,15 +1,11 @@ page.title=Download the Android SDK -@jd:body - -<p>Please carefully review the Android SDK License Agreement before downloading the SDK. -The License Agreement constitutes a contract between you and Google with respect to your use of the SDK.</p> +hide_license_footer=true -<iframe style="border:1px solid #888;margin:0 0 1em;height:400px;width:95%;" src="terms_body.html"> -</iframe> +@jd:body <script language="javascript"> function verify() { - document.getElementById('download_button').disabled = !document.getElementById('checkbox').checked; + document.getElementById('download-button').disabled = !document.getElementById('checkbox').checked; } function submit() { var location = window.location.href; @@ -18,20 +14,30 @@ The License Agreement constitutes a contract between you and Google with respect if (document.getElementById('checkbox').checked) { document.location = "http://dl.google.com/android/" + filename; } - document.getElementById('click_download').setAttribute("href", "http://dl.google.com/android/" + filename); - document.getElementById('next_steps').style.display = "block"; + document.getElementById('click-download').setAttribute("href", "http://dl.google.com/android/" + filename); + $("#terms-form").hide(500); + $("#next-steps").show(500); + document.getElementById('checkbox').disabled=true; + document.getElementById('download-button').disabled=true; } else { alert("You have not selected an SDK version. Please return to the Download page"); } } </script> +<div id="terms-form"> + <p>Please carefully review the Android SDK License Agreement before downloading the SDK. +The License Agreement constitutes a contract between you and Google with respect to your use of the SDK.</p> + + <iframe id="terms" style="border:1px solid #888;margin:0 0 1em;height:400px;width:95%;" src="terms_body.html"> + </iframe> + <p> <input type="checkbox" id="checkbox" onclick="verify()" /> <label for="checkbox">I agree to the terms of the Android SDK License Agreement.</label> </p> <p> - <input type="submit" value="Download" id="download_button" disabled="disabled" onclick="submit()" /> + <input type="submit" value="Download" id="download-button" disabled="disabled" onclick="submit()" /> </p> <p> <script language="javascript"> @@ -42,20 +48,24 @@ The License Agreement constitutes a contract between you and Google with respect } </script> </p> +</div><!-- end terms-form --> <noscript> <p><strong>Please enable Javascript in your browser in order to agree to the terms and download the SDK.</strong></p> </noscript> -<div class="special" id="next_steps" style="display:none"> - <p>Your download should be underway. If not, <a id="click_download">click here to download</a>.</p> - <p>Continue your setup with one the following documents:</p> - <ul style="margin-top:.5em"> - <li><a href="installing.html" class="addVersionPath">Installing</a> - If you are - installing the Android SDK for the first time.</li> - <li><a href="upgrading.html" class="addVersionPath">Upgrading</a> - If you are - upgrading from a previously installed version of the Android SDK.</li> - </ul> +<div class="special" id="next-steps" style="display:none"> + <h2>Thank you for downloading the Android SDK!</h2> + <p>Your download should be underway. If not, <a id="click-download">click here to start the download</a>.</p> + <p>If you are upgrading from a previously installed version of the Android SDK, see + <a href="upgrading.html" class="addVersionPath">Upgrading the SDK</a>.</p> + <p>If you are installing for the first time, read + <a href="installing.html" class="addVersionPath">Installing the Android SDK</a> to get your environment set up. + Once you have completed your installation, visit the <em>Dev Guide</em> tab and begin with the + <a href="/guide/tutorials/hello-world.html">Hello World</a> tutorial to create your first + Android application. From there, learn more about Android with the + <a href="/guide/topics/fundamentals.html">Application Fundamentals</a> documentation.</p> + <p>If you want to re-read the license agreement, it's available to you in the <em>SDK</em> tab.</p> </div> <script language="javascript"> diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index f617302..688929f 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -1,8 +1,12 @@ <ul> - <li><h2>Latest SDK Release</h2> + <li> + <?cs if:android.whichdoc != "online" ?><h2>Android 1.1 SDK, r1</h2> + <?cs else ?><h2>Latest SDK Release</h2><?cs /if ?> <ul> - <li><a href="<?cs var:toroot ?>sdk/1.1_r1/index.html">Download</a></li> + <?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> @@ -15,6 +19,8 @@ </ul> <ul> <li><a href="<?cs var:toroot ?>sdk/terms.html">SDK Terms and Conditions</a></li> - <li><a href="http://code.google.com/android/download_list.html">Previous SDK Releases</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> diff --git a/docs/html/sdk/terms.jd b/docs/html/sdk/terms.jd index 72e5bd0..4638850 100644 --- a/docs/html/sdk/terms.jd +++ b/docs/html/sdk/terms.jd @@ -1,5 +1,5 @@ page.title=Terms and Conditions -sdk.version=1.1_r1 +hide_license_footer=true @jd:body <p>This is the Android Software Development Kit License Agreement.</p> |