本文共 8200 字，大约阅读时间需要 27 分钟。
Lateral navigation is navigation between sibling screens in the application's screen hierarchy (sometimes referred to as a screen map). The most prominent lateral navigation patterns are tabs and horizontal paging (also known as swipe views). This pattern and others are described in . This lesson covers how to implement several of the primary lateral navigation patterns in Android. http://blog.csdn.net/sergeycao
Tabs allow the user to navigate between sibling screens by selecting the appropriate tab indicator available at the top of the display. In Android 3.0 and later, tabs are implemented using the class, and are generally set up in . In some cases, such as when horizontal space is limited and/or the number of tabs is large, an appropriate alternate presentation for tabs is a dropdown list (sometimes implemented using a ).
In previous versions of Android, tabs could be implemented using a and . For details, see the tutorial.
As of Android 3.0, however, you should use either or along with the class.
To create tabs, you can use the following code in your activity's method. Note that the exact presentation of tabs may vary per device and by the current device configuration, to make best use of available screen space. For example, Android may automatically collapse tabs into a dropdown list if tabs don't fit horizontally in the action bar.
@Overridepublic void onCreate(Bundle savedInstanceState) { ... final ActionBar actionBar = getActionBar(); // Specify that tabs should be displayed in the action bar. actionBar.setNavigationMode(ActionBar.NAVIGATION_MODE_TABS); // Create a tab listener that is called when the user changes tabs. ActionBar.TabListener tabListener = new ActionBar.TabListener() { public void onTabSelected(ActionBar.Tab tab, FragmentTransaction ft) { } public void onTabUnselected(ActionBar.Tab tab, FragmentTransaction ft) { } public void onTabReselected(ActionBar.Tab tab, FragmentTransaction ft) { } }; // Add 3 tabs. for (int i = 0; i < 3; i++) { actionBar.addTab( actionBar.newTab() .setText("Tab " + (i + 1)) .setTabListener(tabListener)); } ...} To use a dropdown list instead, use the following code in your activity's method. Dropdown lists are often preferable in cases where more information must be shown per navigation item, such as unread message counts, or where the number of available navigation items is large.
@Overridepublic void onCreate(Bundle savedInstanceState) { ... final ActionBar actionBar = getActionBar(); // Specify that a dropdown list should be displayed in the action bar. actionBar.setNavigationMode(ActionBar.NAVIGATION_MODE_LIST); actionBar.setListNavigationCallbacks( // Specify a SpinnerAdapter to populate the dropdown list. new ArrayAdapter ( actionBar.getThemedContext(), android.R.layout.simple_list_item_1, android.R.id.text1, new String[]{ "Tab 1", "Tab 2", "Tab 3" }), // Provide a listener to be called when an item is selected. new ActionBar.OnNavigationListener() { public boolean onNavigationItemSelected( int position, long id) { // Take action here, e.g. switching to the // corresponding fragment. return true; } }); ...} Horizontal paging, or swipe views, allow users to horizontally on the current screen to navigate to adjacent screens. This pattern can be implemented using the widget, currently available as part of the . For navigating between sibling screens representing a fixed number of sections, it's best to provide the with a . For horizontal paging across collections of objects, it's best to use a , which destroys fragments as the user navigates to other pages, minimizing memory usage.
Below is an example of using a to swipe across a collection of objects.
public class CollectionDemoActivity extends FragmentActivity { // When requested, this adapter returns a DemoObjectFragment, // representing an object in the collection. DemoCollectionPagerAdapter mDemoCollectionPagerAdapter; ViewPager mViewPager; public void onCreate(Bundle savedInstanceState) { // ViewPager and its adapters use support library // fragments, so use getSupportFragmentManager. mDemoCollectionPagerAdapter = new DemoCollectionPagerAdapter( getSupportFragmentManager()); mViewPager = (ViewPager) findViewById(R.id.pager); mViewPager.setAdapter(mDemoCollectionPagerAdapter); }}// Since this is an object collection, use a FragmentStatePagerAdapter,// and NOT a FragmentPagerAdapter.public class DemoCollectionPagerAdapter extends FragmentStatePagerAdapter { public DemoCollectionPagerAdapter(FragmentManager fm) { super(fm); } @Override public Fragment getItem(int i) { Fragment fragment = new DemoObjectFragment(); Bundle args = new Bundle(); // Our object is just an integer :-P args.putInt(DemoObjectFragment.ARG_OBJECT, i + 1); fragment.setArguments(args); return fragment; } @Override public int getCount() { return 100; } @Override public CharSequence getPageTitle(int position) { return "OBJECT " + (position + 1); }}// Instances of this class are fragments representing a single// object in our collection.public static class DemoObjectFragment extends Fragment { public static final String ARG_OBJECT = "object"; @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { // The last two arguments ensure LayoutParams are inflated // properly. View rootView = inflater.inflate( R.layout.fragment_collection_object, container, false); Bundle args = getArguments(); ((TextView) rootView.findViewById(android.R.id.text1)).setText( Integer.toString(args.getInt(ARG_OBJECT))); return rootView; }} You can also add indicators to your horizontal paging UI by adding a . Below is an example layout XML file for an activity whose entire contents are a and a top-aligned inside it. Individual pages (provided by the adapter) occupy the remaining space inside the .
One of the key design recommendations in Android 4.0 for tabs is to between them where appropriate. This behavior enables users to swipe horizontally across the selected tab's contents to navigate to adjacent tabs, without needed to directly interact with the tabs themselves. To implement this, you can use a in conjunction with the tabs API.
Upon observing the current page changing, select the corresponding tab. You can set up this behavior using an in your activity's method:
@Overridepublic void onCreate(Bundle savedInstanceState) { ... mViewPager.setOnPageChangeListener( new ViewPager.SimpleOnPageChangeListener() { @Override public void onPageSelected(int position) { // When swiping between pages, select the // corresponding tab. getActionBar().setSelectedNavigationItem(position); } }); ...} And upon selecting a tab, switch to the corresponding page in the . To do this, add an to your tab when creating it using the method:
actionBar.newTab() ... .setTabListener(new ActionBar.TabListener() { public void onTabSelected(ActionBar.Tab tab, FragmentTransaction ft) { // When the tab is selected, switch to the // corresponding page in the ViewPager. mViewPager.setCurrentItem(tab.getPosition()); } ... }));