Skip to content

Commit 44108b5

Browse files
ddoughertyddougherty
committed
Doc change: Move framework api change info higher in platform notes documents.
Small adjustment to compatibility doc. Change-Id: I2af896292b00323d7f4eb2c828c8dea36b9e94ad
1 parent 68728cb commit 44108b5

File tree

6 files changed

+554
-543
lines changed

6 files changed

+554
-543
lines changed

‎docs/html/guide/practices/compatibility.jd‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,15 +36,16 @@ exchange, however, it also means that your apps will have to cope with that same
3636
variety of hardware.</p>
3737

3838
<p>Fortunately, Android has built-in tools and support that make it easy for
39-
your apps to do that, while at the same time maintaining control of what types
40-
of devices your app is available to. If you do your work properly, users
39+
your apps to do that, while at the same time letting you maintain control of
40+
what types of devices your app is available to. With a bit of forethought and
41+
some minor changes in your app's manifest file, you can ensure that users
4142
whose devices can’t run your app will never see it in the Android Market, and
4243
will not get in trouble by downloading it. This page explains how you can
4344
control which devices have access to your apps, and how to prepare your apps to
4445
make sure they reach the right audience.</p>
4546

4647

47-
<h3 id="defined">What does “Compatibility” mean?</h3>
48+
<h3 id="defined">What does “compatibility” mean?</h3>
4849

4950
<p>A device is “Android compatible” if it can correctly run apps written for the
5051
<em>Android execution environment</em>. The exact details of the Android execution

‎docs/html/guide/practices/screens_support.jd‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,9 @@ device screen, and adapts them to the actual pixel map of the screen.</p>
171171

172172
<p>The table below lists some of the more common screens supported
173173
by Android and illustrates how the platform maps them to generalized screen
174-
configurations.</p>
174+
configurations. Some devices use screens that are not specifically listed
175+
in the table &mdash; the platform maps those to the same set generalized
176+
screen configurations. </p>
175177

176178
<p class="table-caption" id="screens-table"><strong>Table 1.</strong> Examples of
177179
device screens supported by Android.</p>

‎docs/html/sdk/android-1.5.jd‎

Lines changed: 127 additions & 118 deletions
Original file line numberDiff line numberDiff line change
@@ -10,25 +10,31 @@ sdk.platform.deployableDate=May 2009
1010
<div id="qv-wrapper">
1111
<div id="qv">
1212

13-
<h2>In this document</h2>
14-
<ol>
15-
<li><a href="#features">Platform Highlights</a></li>
16-
<li><a href="#relnotes">Revisions</a></li>
17-
<li><a href="#apps">Built-in Applications</a></li>
18-
<li><a href="#locs">Locales</a></li>
19-
<li><a href="#skins">Emulator Skins</a></li>
20-
<li><a href="#api">Framework API</a>
21-
<ol>
22-
<li><a href="#api-level">API level</a></li>
23-
<li><a href="#api-changes">API changes summary</a></li>
24-
<li><a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API differences report &raquo;</a> </li>
25-
</ol></li>
26-
</ol>
27-
28-
<h2>See Also</h2>
29-
<ol>
30-
<li><a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a></li>
31-
</ol>
13+
<h2>In this document</h2>
14+
<ol>
15+
<li><a href="#features">Platform Highlights</a></li>
16+
<li><a href="#relnotes">Revisions</a></li>
17+
<li><a href="#api-level">API Level</a></li>
18+
<li><a href="#api">Framework API Changes</a>
19+
<li><a href="#apps">Built-in Applications</a></li>
20+
<li><a href="#locs">Locales</a></li>
21+
<li><a href="#skins">Emulator Skins</a></li>
22+
23+
</ol>
24+
</li>
25+
</ol>
26+
27+
<h2>Reference</h2>
28+
<ol>
29+
<li><a
30+
href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API
31+
Differences Report &raquo;</a> </li>
32+
</ol>
33+
34+
<h2>See Also</h2>
35+
<ol>
36+
<li><a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a></li>
37+
</ol>
3238

3339
</div>
3440
</div>
@@ -87,7 +93,8 @@ function toggleDiv(link) {
8793
</script>
8894
<style>
8995
.toggleable {
90-
padding: .25em 1em;
96+
padding: .25em 1em 0em 1em;
97+
margin-bottom: 0;
9198
}
9299
.toggleme {
93100
padding: 1em 1em 0 2em;
@@ -162,6 +169,106 @@ padding: .25em 1em;
162169
</div>
163170
</div>
164171

172+
173+
<h2 id="api-level">API Level</h2>
174+
175+
<p>The Android {@sdkPlatformVersion} platform delivers an updated version of
176+
the framework API. The Android {@sdkPlatformVersion} API
177+
is assigned an integer identifier &mdash;
178+
<strong>{@sdkPlatformApiLevel}</strong> &mdash; that is
179+
stored in the system itself. This identifier, called the "API Level", allows the
180+
system to correctly determine whether an application is compatible with
181+
the system, prior to installing the application. </p>
182+
183+
<p>To use APIs introduced in Android {@sdkPlatformVersion} in your
184+
application, you need to set the proper value, "{@sdkPlatformApiLevel}", in the
185+
<code>android:minSdkVersion</code> attributes of the <code>&lt;uses-sdk&gt;</code>
186+
element in your application's manifest. </p>
187+
188+
<p>For more information about how to use API Level, see the <a
189+
href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p>
190+
191+
192+
<h2 id="api">Framework API Changes</h2>
193+
194+
<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>
195+
196+
<h3>UI framework</h3>
197+
<ul>
198+
<li>Framework for easier background/UI thread interaction</li>
199+
<li>New {@link android.widget.SlidingDrawer SlidingDrawer} widget</li>
200+
<li>New {@link android.widget.HorizontalScrollView HorizontalScrollview} widget</li>
201+
</ul>
202+
203+
<h3>AppWidget framework</h3>
204+
<ul>
205+
<li>APIs for creating secure home screen {@link android.appwidget
206+
AppWidgets}. For information about how to use AppWidgets, see the Developer's
207+
Guide <a href="{@docRoot}guide/topics/appwidgets/index.html">AppWidgets</a>
208+
documentation. Also see <a
209+
href="http://android-developers.blogspot.com/2009/04/introducing-home-screen-widgets-and.html">
210+
Introducing home screen widgets and the AppWidget
211+
framework</a> on the Android Developer's Blog.</li>
212+
<li>APIs for populating {@link android.provider.LiveFolders Live Folders}
213+
with custom content.</li>
214+
</ul>
215+
216+
<h3>Media framework</h3>
217+
<ul>
218+
<li>Raw audio recording and playback APIs</li>
219+
<li>Interactive MIDI playback engine</li>
220+
<li>Video recording APIs for developers (3GP format)</li>
221+
<li>Video and photo sharing Intents</li>
222+
<li>Media search Intent</li>
223+
</ul>
224+
225+
<h3>Input Method framework </h3>
226+
<ul>
227+
<li>{@link android.inputmethodservice.InputMethodService Input Method
228+
Service} framework</li>
229+
<li>Text-prediction engine</li>
230+
<li>Ability to provide downloadable IMEs to users</li>
231+
</ul>
232+
233+
<h3>Application-defined hardware requirements</h3>
234+
235+
<p>Applications can now use a new element in their manifest files, <a
236+
href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code>&lt;uses-configuration&gt;</code></a>
237+
to indicate to the Android system what hardware features
238+
they require in order to function properly. For example, an application might
239+
use the element to specify that it requires a physical keyboard or a particular
240+
navigation device, such as a trackball. Prior to installing the application, the
241+
Android system checks the attributes defined for the
242+
<code>&lt;uses-configuration&gt;</code> element and allows the installation to
243+
continue only if the required hardware is present.</p>
244+
245+
<h3>Speech recognition framework</h3>
246+
<ul>
247+
<li>Support for using speech recognition libraries via Intent. See {@link
248+
android.speech.RecognizerIntent RecognizerIntent}.</li>
249+
</ul>
250+
251+
<h3>Miscellaneous API additions</h3>
252+
<ul>
253+
<li>LocationManager - Applications can get location change updates via
254+
Intent</li>
255+
<li>WebView - Touch start/end/move/cancel DOM event support</li>
256+
<li>Redesigned {@link android.hardware.SensorManager Sensor Manager
257+
APIs}</li>
258+
<li>GLSurfaceView - convenience framework for creating OpenGL
259+
applications</li>
260+
<li>Broadcast Intent for app update install succeeded - for smoother app
261+
upgrade experience</li>
262+
</ul>
263+
264+
265+
<h3 id="api-diff">API differences report</h3>
266+
267+
<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
268+
the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API
269+
Differences Report</a>.</p>
270+
271+
165272
<h2 id="apps">Built-in Applications</h2>
166273

167274
<p>The system image included in the downloadable platform provides these
@@ -268,101 +375,3 @@ through Settings.</p>
268375
</ul>
269376

270377
<p>For more information about how to develop an application that displays and functions properly on all Android-powered devices, see <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>.</p>
271-
272-
273-
<h2 id="api">Framework API</h2>
274-
275-
<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>
276-
277-
278-
<h3 id="api-level">API level</h3>
279-
280-
<p>The Android {@sdkPlatformVersion} platform delivers an updated version of the framework
281-
API. As with previous versions, the Android {@sdkPlatformVersion} API
282-
is assigned an integer identifier &mdash; <strong>{@sdkPlatformApiLevel}</strong> &mdash; that is
283-
stored in the system itself. This identifier, called the "API Level", allows the
284-
system to correctly determine whether an application is compatible with
285-
the system, prior to installing the application. </p>
286-
287-
<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
288-
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>&lt;uses-sdk&gt;</code>
289-
element in your application's manifest. </p>
290-
291-
<p>For more information about how to use API Level, see the <a
292-
href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p>
293-
294-
<h3 id="api-changes">API changes summary</h3>
295-
296-
<h4>UI framework</h4>
297-
<ul>
298-
<li>Framework for easier background/UI thread interaction</li>
299-
<li>New {@link android.widget.SlidingDrawer SlidingDrawer} widget</li>
300-
<li>New {@link android.widget.HorizontalScrollView HorizontalScrollview} widget</li>
301-
</ul>
302-
303-
<h4>AppWidget framework</h4>
304-
<ul>
305-
<li>APIs for creating secure home screen {@link android.appwidget
306-
AppWidgets}. For information about how to use AppWidgets, see the Developer's
307-
Guide <a href="{@docRoot}guide/topics/appwidgets/index.html">AppWidgets</a>
308-
documentation. Also see <a
309-
href="http://android-developers.blogspot.com/2009/04/introducing-home-screen-widgets-and.html">
310-
Introducing home screen widgets and the AppWidget
311-
framework</a> on the Android Developer's Blog.</li>
312-
<li>APIs for populating {@link android.provider.LiveFolders Live Folders}
313-
with custom content.</li>
314-
</ul>
315-
316-
<h4>Media framework</h4>
317-
<ul>
318-
<li>Raw audio recording and playback APIs</li>
319-
<li>Interactive MIDI playback engine</li>
320-
<li>Video recording APIs for developers (3GP format)</li>
321-
<li>Video and photo sharing Intents</li>
322-
<li>Media search Intent</li>
323-
</ul>
324-
325-
<h4>Input Method framework </h4>
326-
<ul>
327-
<li>{@link android.inputmethodservice.InputMethodService Input Method
328-
Service} framework</li>
329-
<li>Text-prediction engine</li>
330-
<li>Ability to provide downloadable IMEs to users</li>
331-
</ul>
332-
333-
<h4>Application-defined hardware requirements</h4>
334-
<p>Applications can now use a new element in their manifest files, <a
335-
href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code>&lt;uses-configuration&gt;</code></a>
336-
to indicate to the Android system what hardware features
337-
they require in order to function properly. For example, an application might
338-
use the element to specify that it requires a physical keyboard or a particular
339-
navigation device, such as a trackball. Prior to installing the application, the
340-
Android system checks the attributes defined for the
341-
<code>&lt;uses-configuration&gt;</code> element and allows the installation to
342-
continue only if the required hardware is present.</p>
343-
344-
<h4>Speech recognition framework</h4>
345-
<ul>
346-
<li>Support for using speech recognition libraries via Intent. See {@link
347-
android.speech.RecognizerIntent RecognizerIntent}.</li>
348-
</ul>
349-
350-
<h4>Miscellaneous API additions</h4>
351-
<ul>
352-
<li>LocationManager - Applications can get location change updates via
353-
Intent</li>
354-
<li>WebView - Touch start/end/move/cancel DOM event support</li>
355-
<li>Redesigned {@link android.hardware.SensorManager Sensor Manager
356-
APIs}</li>
357-
<li>GLSurfaceView - convenience framework for creating OpenGL
358-
applications</li>
359-
<li>Broadcast Intent for app update install succeeded - for smoother app
360-
upgrade experience</li>
361-
</ul>
362-
363-
364-
<h3 id="api-diff">API differences report</h3>
365-
366-
<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to
367-
the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API
368-
Differences Report</a>.</p>

0 commit comments

Comments
 (0)