Home | History | Annotate | Download | only in backward-compatible-ui

Lines Matching full:actionbar

18   <li><a href="#abstract-actionbar-tab">Abstract ActionBar.Tab</a></li>
19 <li><a href="#abstract-actionbar-methods">Abstract ActionBar Tab Methods</a></li>
24 <li><a href="{@docRoot}guide/topics/ui/actionbar.html">Action Bar</a></li>
25 <li><a href="{@docRoot}guide/topics/ui/actionbar.html#Tabs">Action Bar Tabs</a></li>
39 <p>Suppose you want to use <a href="{@docRoot}guide/topics/ui/actionbar.html#Tabs">action bar tabs</a> as the primary form of top-level navigation in your application. Unfortunately, the {@link android.app.ActionBar} APIs are only available in Android 3.0 or later (API level 11+). Thus, if you want to distribute your application to devices running earlier versions of the platform, you need to provide an implementation that supports the newer API while providing a fallback mechanism that uses older APIs.</p>
63 <p>The key APIs for tabs are in {@link android.app.ActionBar} and {@link android.app.ActionBar.Tab ActionBar.Tab}. These are the APIs to abstract in order to make your tabs version-aware. The requirements for this example project call for compatibility back to Eclair (API level 5) while taking advantage of the new tab features in Honeycomb (API Level 11). A diagram of the class structure to support these two implementations and their abstract base classes (or interfaces) is shown below.</p>
70 <h2 id="abstract-actionbar-tab">Abstract ActionBar.Tab</h2>
72 <p>Get started on building your tab abstraction layer by creating an abstract class representing a tab, that mirrors the {@link android.app.ActionBar.Tab ActionBar.Tab} interface:</p>
93 <h2 id="abstract-actionbar-methods">Abstract ActionBar Tab Methods</h2>
95 <p>Next, define an abstract class that allows you to create and add tabs to an activity, like {@link android.app.ActionBar#newTab ActionBar.newTab()} and {@link android.app.ActionBar#addTab ActionBar.addTab()}:</p>