diff options
author | Dirk Dougherty <ddougherty@google.com> | 2009-09-10 10:45:41 -0700 |
---|---|---|
committer | Dirk Dougherty <ddougherty@google.com> | 2009-09-10 18:23:12 -0700 |
commit | 4c8a16a43905e92dd24ee0d9860d20d270d77977 (patch) | |
tree | 7a3caf2db8e1ed6fff71889d8e642520f6b00df5 /docs/html/sdk | |
parent | dac0d75ad7fbd10981477b1fcc35c955185a41fd (diff) | |
download | frameworks_base-4c8a16a43905e92dd24ee0d9860d20d270d77977.zip frameworks_base-4c8a16a43905e92dd24ee0d9860d20d270d77977.tar.gz frameworks_base-4c8a16a43905e92dd24ee0d9860d20d270d77977.tar.bz2 |
Minor changes to api levels doc and upgrading doc. Change Linux "tested on" to Hardy Heron.
Change-Id: I24a0c3cb5c15e3725fecb5c64d8aa6de17c76cbd
Diffstat (limited to 'docs/html/sdk')
-rw-r--r-- | docs/html/sdk/1.6_r1/requirements.jd | 2 | ||||
-rw-r--r-- | docs/html/sdk/1.6_r1/upgrading.jd | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/html/sdk/1.6_r1/requirements.jd b/docs/html/sdk/1.6_r1/requirements.jd index 781ee32..8e698fa 100644 --- a/docs/html/sdk/1.6_r1/requirements.jd +++ b/docs/html/sdk/1.6_r1/requirements.jd @@ -11,7 +11,7 @@ Android applications using the Android SDK tools included in Android <ul> <li>Windows XP (32-bit) or Vista (32- or 64-bit)</li> <li>Mac OS X 10.4.8 or later (x86 only)</li> - <li>Linux (tested on Linux Ubuntu Dapper Drake)</li> + <li>Linux (tested on Linux Ubuntu Hardy Heron)</li> </ul> <h3>Supported Development Environments</h3> diff --git a/docs/html/sdk/1.6_r1/upgrading.jd b/docs/html/sdk/1.6_r1/upgrading.jd index 2f9cc73..ebe6a95 100644 --- a/docs/html/sdk/1.6_r1/upgrading.jd +++ b/docs/html/sdk/1.6_r1/upgrading.jd @@ -219,7 +219,7 @@ hardware capabilities. If you find dependencies, you can design around them by building in alternate support or graceful degradation, or you can specify them as hardware requirements in a <a href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code><uses-configuration></code>.</a> -element in the application's manifest file. Also see the <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code> +element in the application's manifest file. Also see the <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a> manifest element, which lets your application declare a requirement for specific features, such as an OpenGL ES version or a camera that has autofocus capability. @@ -258,7 +258,7 @@ AVDs that emulate different screen resolutions and densities. Also note that, starting with Android 1.6, the platform provides a Compatibility Mode that automatically scales the UI of applications if they do not explicitly indicate support for the current screen in the -<a href="{@docRoot}guide/topics/manifest/supports-screen-element.html"><code><supports-screen></code> +<a href="{@docRoot}guide/topics/manifest/supports-screen-element.html"><code><supports-screen></code></a> element in their manifest files. As part of testing, you should evaluate how your application is displayed in Compatibility Mode on different screens. </p> </li> |