Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5b18c714 authored by Joe Fernandez's avatar Joe Fernandez Committed by Android (Google) Code Review
Browse files

Merge "docs: Release Notes v2 for Android 4.0.3, ADT 16.0.1, Support lib r5-r6" into ics-mr1

parents 14633f1b 71d5c1db
Loading
Loading
Loading
Loading
+70 −60
Original line number Diff line number Diff line
@@ -35,7 +35,8 @@ worry less about platform versions.</p>

<p class="note"><strong>Note:</strong> The Support Package includes more than one support
library. Each one has a different <em>minimum API level</em>. For example, one library requires API
level 4 or higher, while another requires API level 13 or higher (v13 is a superset of v4 and includes additional
level 4 or higher, while another requires API level 13 or higher (v13 is a superset of v4 and
includes additional
support classes to work with v13 APIs). The minimum version is indicated
by the directory name, such as {@code v4/} and {@code v13/}.</p>

@@ -54,6 +55,8 @@ the Support Package, as denoted by revision number.</p>
  </a></p>

  <div class="toggle-content-toggleme" style="padding-left:2em">
    <p class="note"><strong>Note:</strong> Reference for support library APIs are now available with
    the framework references, for example: {@link android.support.v4.app}.</p>
<dl>
      <dt>Changes for v4 support library:</dt>
      <dd>
@@ -68,10 +71,10 @@ the Support Package, as denoted by revision number.</p>
              <li>Added {@link android.support.v4.view.PagerTitleStrip}, a non-interactive title
                strip, that can be added as a child of ViewPager. Developers can supply text
                appearance and color, as well as layout sizing and gravity information.</li>
              <li>Updated PagerAdapter methods to take ViewGroup objects, rather than View to avoid
                class casting in adapter implementations. For more information, see
                {@link android.support.v4.view.PagerAdapter}.</li>
              <li>Updated ViewPager to use Launcher Workspace-style fling behavior.</li>
              <li>Updated {@link android.support.v4.view.PagerAdapter} methods to take ViewGroup
                objects, rather than View to avoid class casting in adapter implementations.</li>
              <li>Updated {@link android.support.v4.view.ViewPager} to use Launcher-style
                fling behavior.</li>
              <li>Bug fixes for user interface interaction and test automation.</li>
            </ul>
          </li>
@@ -111,34 +114,35 @@ the Support Package, as denoted by revision number.</p>
        <ul>
          <li>Support for Accessiblity APIs:
            <ul>
              <li>Added <code>AccessibilityDelegateCompat</code> to support
              {@link android.view.View.AccessibilityDelegate}.</li>
              <li>Added {@link android.support.v4.view.AccessibilityDelegateCompat}
              to support {@link android.view.View.AccessibilityDelegate}.</li>

              <li>Added <code>AccessibilityEventCompat</code> to support
              {@link android.view.accessibility.AccessibilityEvent}.</li>
              <li>Added {@link android.support.v4.view.accessibility.AccessibilityEventCompat}
              to support {@link android.view.accessibility.AccessibilityEvent}.</li>

              <li>Added <code>AccessibilityManagerCompat</code> to support
              {@link android.view.accessibility.AccessibilityManager}.</li>
              <li>Added {@link android.support.v4.view.accessibility.AccessibilityManagerCompat}
              to support {@link android.view.accessibility.AccessibilityManager}.</li>

              <li>Added <code>AccessibilityNodeInfoCompat</code> to support
              {@link android.view.accessibility.AccessibilityNodeInfo}.</li>
              <li>Added {@link android.support.v4.view.accessibility.AccessibilityNodeInfoCompat}
              to support {@link android.view.accessibility.AccessibilityNodeInfo}.</li>

              <li>Added <code>AccessibilityRecordCompat</code> to support
              {@link android.view.accessibility.AccessibilityRecord}.</li>
              <li>Added {@link android.support.v4.view.accessibility.AccessibilityRecordCompat}
              to support {@link android.view.accessibility.AccessibilityRecord}.</li>

              <li>Added <code>AccessibilityServiceInfoCompat</code> to support
              {@link android.accessibilityservice.AccessibilityServiceInfo}.</li>
              <li>Added {@link
              android.support.v4.accessibilityservice.AccessibilityServiceInfoCompat}
              to support {@link android.accessibilityservice.AccessibilityServiceInfo}.</li>

              <li>Added <code>ViewGroupCompat</code>
              <li>Added {@link android.support.v4.view.ViewGroupCompat}
              to support accessibility features in {@link android.view.ViewGroup}.
              </li>

              <li>Modified <code>ViewCompat</code>
              <li>Modified {@link android.support.v4.view.ViewCompat}
              to support accessibility features in {@link android.view.View}.</li>
            </ul>
          </li>

          <li>Changes to <code>ViewPager</code>:
          <li>Changes to ViewPager:
            <ul>
              <li>Added support for margins between pages.
              An optional {@link android.graphics.drawable.Drawable} can be provided
@@ -339,7 +343,7 @@ provided APIs are available in the {@code android.support} package (for
example, {@code android.support.v4}).</p>

<p class="note"><strong>Tip:</strong> To see the library APIs in action, take a look at the sample
apps in {@code extras/android/support/&lt;version&gt;/samples/}.</p>
apps in {@code &lt;sdk&gt;/extras/android/support/&lt;version&gt;/samples/}.</p>

<p class="warning"><strong>Warning:</strong> Be certain that you not confuse the standard
{@code android} packages with those in {@code android.support} library. Some code completion tools
@@ -377,17 +381,20 @@ differences, however. Most notably:</p>

<ul>
  <li>When creating an activity to use fragments, you must declare your activity to extend the
{@code FragmentActivity} class (instead of the traditional {@link android.app.Activity}
class).</li>
  <li>To manage your fragments and loaders, you must use the methods {@code
FragmentActivity.getSupportFragmentManager()} and {@code
FragmentActivity.getSupportLoaderManager()} (instead of the {@link
android.app.Activity#getFragmentManager()} and {@link android.app.Activity#getLoaderManager()}
methods).</li>
{@link android.support.v4.app.FragmentActivity} class (instead of the traditional
{@link android.app.Activity} class).</li>
  <li>To manage your fragments and loaders, you must use the methods
  {@link android.support.v4.app.FragmentActivity#getSupportFragmentManager
  FragmentActivity.getSupportFragmentManager()} and
  {@link android.support.v4.app.FragmentActivity#getSupportLoaderManager
  FragmentActivity.getSupportLoaderManager()} (instead of the
  {@link android.app.Activity#getFragmentManager()} and
  {@link android.app.Activity#getLoaderManager()} methods).</li>
  <li>The {@link android.app.ActionBar} is <strong>not supported</strong> by the library.
However, when creating your <a href="{@docRoot}guide/topics/ui/menus.html#options-menu">Options
Menu</a>, you can declare which items should be added to the Action Bar when it's available (on
Android 3.0 or later). You can do so with the {@code MenuCompat.setShowAsAction()} method. For
Android 3.0 or later). You can do so with the
{@link android.support.v4.view.MenuCompat#setShowAsAction MenuCompat.setShowAsAction()} method, for
example:
<pre>
public boolean onCreateOptionsMenu(Menu menu) {
@@ -397,12 +404,15 @@ public boolean onCreateOptionsMenu(Menu menu) {
    return true;
}
</pre>
<p>Also see the <a href="{@docRoot}resources/samples/ActionBarCompat/index.html">Action Bar
Compatibility</a> sample for a demonstration of how to use {@link android.app.ActionBar} on Android
3.0+ and also support action bar functionality on older versions.</p>
</li>
</ul>

<div class="note"><p><strong>Tip:</strong> To enable the Holographic theme on devices
running Android 3.0 or higher, declare in your manifest file that your application targets
API level 11. For example:</p>
API level 11, for example:</p>
<pre>
&lt;uses-sdk android:minSdkVersion="4" android:targetSdkVersion="11" /&gt;
</pre>
@@ -417,29 +427,29 @@ Apps for Android 3.0</a>.</p>

<h2 id="Docs">Reference Docs</h2>

<p>The libraries currently do not provide reference documentation for the included APIs. To generate
your own set using the {@code javadoc} tool, perform the following from a command (as appropriate
for the library version you're using). In this example, documentation is generated for the v4
library:</p>
<p>The reference documentation for the Support Packages is included as part of the Android
online developer documentation:</p>

<pre class="no-pretty-print">
cd &lt;sdk&gt;/extras/android/support/v4/
mkdir docs
javadoc -sourcepath src/java/ -subpackages android.support.v4 -d docs
</pre>
<p>Open the {@code docs/index.html} file to begin browsing the generated documentation.</p>
<ul>
  <li><a href="{@docRoot}reference/android/support/v4/app/package-summary.html">Support Package
    API 4 Reference</a></li>
  <li><a href="{@docRoot}reference/android/support/v13/app/package-summary.html">Support Package
    API 13 Reference</a></li>
</ul>


<h2 id="Samples">Samples</h2>

<p>If you want to see some code that uses the support libraries, samples are included with the
Support Package, inside each support library directory. For example, at {@code
extras/android/support/v4/samples/}.</p>
Support Package, inside each support library directory, for example; {@code
&lt;sdk&gt;/extras/android/support/v4/samples/}. You can also view these samples as part of the
Android online developer documentation:</p>

<ul>
  <li><a href="{@docRoot}resources/samples/Support4Demos/index.html">Support API 4 Demos</a></li>
  <li><a href="{@docRoot}resources/samples/Support13Demos/index.html">Support API 13 Demos</a></li>
</ul>

<p>Additionally, the <a href="http://code.google.com/p/iosched/">Google I/O App</a> is a complete
application that uses the v4 support library to provide a single APK for both handsets and tablets
and also demonstrates some of Android's best practices in Android UI design.</p>



+2 −2
Original line number Diff line number Diff line
@@ -94,7 +94,7 @@ padding: .25em 1em;
  <ul>
    <li>Added Lint tools to detect common errors in Android projects. 
      (<a href="http://tools.android.com/recent/lint">more info</a>)</li>
    <a>Added sensor emulation support, which allows the emulator to read sensor data from a
    <li>Added sensor emulation support, which allows the emulator to read sensor data from a
      physical Android device. 
      (<a href="http://tools.android.com/recent/sensoremulation">more info</a>)</li>
    <li>Added support for using a webcam to emulate a camera on Mac OS X.</li>
@@ -201,7 +201,7 @@ padding: .25em 1em;
commands, see the
<a href="{@docRoot}guide/developing/building/building-cmdline.html#AntReference">Ant Command
Reference</a>.</li>
    <li>Changed how library projects are built.</a></li>
    <li>Changed how library projects are built.</li>
    <li>Improved incremental builds, so that resource compilation runs less frequently. Builds no
    longer run when you edit strings or layouts (unless you add a new <code>id</code>) and no longer
    run once for each library project.</li>