Android雜談--ListView之BaseAdapter的使用


      前言      

  話說開發用了各種Adapter之后感覺用的最舒服的還是BaseAdapter,盡管使用起來比其他適配器有些麻煩,但是使用它卻能實現很多自己喜歡的列表布局,比如ListView、GridView、Gallery、Spinner等等。它是直接繼承自接口類Adapter的,使用BaseAdapter時需要重寫很多方法,其中最重要的當屬getView,因為這會涉及到ListView優化等問題,其他的方法可以參考鏈接的文章

BaseAdapter與其他Adapter有些不一樣,其他的Adapter可以直接在其構造方法中進行數據的設置,比如

SimpleAdapter adapter = new SimpleAdapter(this, getData(), R.layout.list_item, new String[]{"img","title","info",new int[]{R.id.img, R.id.title, R.id.info}});

但是在BaseAdapter中需要實現一個繼承自BaseAdapter的類,並且重寫里面的很多方法,例如

class MyAdapter extends BaseAdapter
{
private Context context;
public MyAdapter(Context context)
{
this.context = context;
}
@Override
public int getCount() {
// How many items are in the data set represented by this Adapter.(在此適配器中所代表的數據集中的條目數)
return 0;
}

@Override
public Object getItem(int position) {
// Get the data item associated with the specified position in the data set.(獲取數據集中與指定索引對應的數據項)
return null;
}

@Override
public long getItemId(int position) {
// Get the row id associated with the specified position in the list.(取在列表中與指定索引對應的行id)
return 0;
}

@Override
public View getView(int position, View convertView, ViewGroup parent) {
// Get a View that displays the data at the specified position in the data set.
return null;
}

}

這里面沒什么難度,但是這個getView方法必須好好處理,也是最麻煩的

第一種:沒有任何處理,不建議這樣寫。如果數據量少看將就,但是如果列表項數據量很大的時候,會每次都重新創建View,設置資源,嚴重影響性能,所以從一開始就不要用這種方式

        @Override
public View getView(int position, View convertView, ViewGroup parent) {
View item = mInflater.inflate(R.layout.list_item, null);
ImageView img = (ImageView)item.findViewById(R.id.img)
TextView title = (TextView)item.findViewById(R.id.title);
TextView info = (TextView)item.findViewById(R.id.info);
img.setImageResource(R.drawable.ic_launcher);
title.setText("Hello");
info.setText("world");

return item;
}

第二種ListView優化:通過緩存convertView,這種利用緩存contentView的方式可以判斷如果緩存中不存在View才創建View,如果已經存在可以利用緩存中的View,提升了性能

        public View getView(int position, View convertView, ViewGroup parent) {
if(convertView == null)
{
convertView = mInflater.inflate(R.layout.list_item, null);
}

ImageView img = (ImageView)convertView.findViewById(R.id.img)
TextView title = (TextView)convertView.findViewById(R.id.title);
TextView info = (TextView)ConvertView.findViewById(R.id.info);
img.setImageResource(R.drawable.ic_launcher);
title.setText("Hello");
info.setText("world");

return convertView;
}

第三種ListView優化:通過convertView+ViewHolder來實現,ViewHolder就是一個靜態類,使用 ViewHolder 的關鍵好處是緩存了顯示數據的視圖(View),加快了 UI 的響應速度。

當我們判斷 convertView == null  的時候,如果為空,就會根據設計好的ListItem布局(XML),來為convertView賦值,並生成一個viewHolder來綁定converView里面的各個View控件(XML布局里面的那些控件)。再用convertViewsetTagviewHolder設置到Tag中,以便系統第二次繪制ListView時從Tag中取出。(看下面代碼中)

如果convertView不為空的時候,就會直接用convertViewgetTag(),來獲得一個ViewHolder

    //在外面先定義,ViewHolder靜態類
static class ViewHolder
{
public ImageView img;
public TextView title;
public TextView info;
}
//然后重寫getView
@Override
public View getView(int position, View convertView, ViewGroup parent) {
ViewHolder holder;
if(convertView == null)
{
holder = new ViewHolder();
convertView = mInflater.inflate(R.layout.list_item, null);
holder.img = (ImageView)item.findViewById(R.id.img)
holder.title = (TextView)item.findViewById(R.id.title);
holder.info = (TextView)item.findViewById(R.id.info);
convertView.setTag(holder);
}else
{
holder = (ViewHolder)convertView.getTag();
holder.img.setImageResource(R.drawable.ic_launcher);
holder.title.setText("Hello");
holder.info.setText("World");
}

return convertView;
}

到這里,可能會有人問ViewHolder靜態類結合緩存convertView與直接使用convertView有什么區別嗎,是否重復了

在這里,官方給出了解釋

提升Adapter的兩種方法

To work efficiently the adapter implemented here uses two techniques:
-It reuses the convertView passed to getView() to avoid inflating View when it is not necessary

(譯:重用緩存convertView傳遞給getView()方法來避免填充不必要的視圖)
-It uses the ViewHolder pattern to avoid calling findViewById() when it is not necessary

(譯:使用ViewHolder模式來避免沒有必要的調用findViewById():因為太多的findViewById也會影響性能)
ViewHolder類的作用
-The ViewHolder pattern consists in storing a data structure in the tag of the view
returned by getView().This data structures contains references to the views we want to bind data to,
thus avoiding calling to findViewById() every time getView() is invoked

(譯:ViewHolder模式通過getView()方法返回的視圖的標簽(Tag)中存儲一個數據結構,這個數據結構包含了指向我們

要綁定數據的視圖的引用,從而避免每次調用getView()的時候調用findViewById())

實例一:用BaseAdapter來自定義ListView布局
main.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width
="fill_parent"
android:layout_height
="fill_parent"
android:orientation
="vertical" >

<ListView
android:id="@+id/lv"
android:layout_width
="fill_parent"
android:layout_height
="wrap_content"
android:fastScrollEnabled
="true"
/>

</LinearLayout>

list_item.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width
="match_parent"
android:layout_height
="match_parent"
android:orientation
="horizontal" >

<ImageView
android:id="@+id/img"
android:layout_width
="wrap_content"
android:layout_height
="wrap_content"
/>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height
="wrap_content"
android:orientation
="vertical"
>
<TextView
android:id="@+id/tv"
android:layout_width
="wrap_content"
android:layout_height
="wrap_content"
android:textSize
="20sp"
/>
<TextView
android:id="@+id/info"
android:layout_width
="wrap_content"
android:layout_height
="wrap_content"
android:textSize
="14sp"
/>
</LinearLayout>


</LinearLayout>

Activity

package com.loulijun.demo17;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.BaseAdapter;
import android.widget.ImageView;
import android.widget.ListView;
import android.widget.TextView;

public class Demo17Activity extends Activity {
private ListView lv;
private List<Map<String, Object>> data;
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
lv = (ListView)findViewById(R.id.lv);
//獲取將要綁定的數據設置到data中
data = getData();
MyAdapter adapter = new MyAdapter(this);
lv.setAdapter(adapter);
}

private List<Map<String, Object>> getData()
{
List<Map<String, Object>> list = new ArrayList<Map<String, Object>>();
Map<String, Object> map;
for(int i=0;i<10;i++)
{
map = new HashMap<String, Object>();
map.put("img", R.drawable.ic_launcher);
map.put("title", "跆拳道");
map.put("info", "快樂源於生活...");
list.add(map);
}
return list;
}

//ViewHolder靜態類
static class ViewHolder
{
public ImageView img;
public TextView title;
public TextView info;
}

public class MyAdapter extends BaseAdapter
{
private LayoutInflater mInflater = null;
private MyAdapter(Context context)
{
//根據context上下文加載布局,這里的是Demo17Activity本身,即this
this.mInflater = LayoutInflater.from(context);
}

@Override
public int getCount() {
//How many items are in the data set represented by this Adapter.
//在此適配器中所代表的數據集中的條目數
return data.size();
}

@Override
public Object getItem(int position) {
// Get the data item associated with the specified position in the data set.
//獲取數據集中與指定索引對應的數據項
return position;
}

@Override
public long getItemId(int position) {
//Get the row id associated with the specified position in the list.
//獲取在列表中與指定索引對應的行id
return position;
}

//Get a View that displays the data at the specified position in the data set.
//獲取一個在數據集中指定索引的視圖來顯示數據
@Override
public View getView(int position, View convertView, ViewGroup parent) {
ViewHolder holder = null;
//如果緩存convertView為空,則需要創建View
if(convertView == null)
{
holder = new ViewHolder();
//根據自定義的Item布局加載布局
convertView = mInflater.inflate(R.layout.list_item, null);
holder.img = (ImageView)convertView.findViewById(R.id.img);
holder.title = (TextView)convertView.findViewById(R.id.tv);
holder.info = (TextView)convertView.findViewById(R.id.info);
//將設置好的布局保存到緩存中,並將其設置在Tag里,以便后面方便取出Tag
convertView.setTag(holder);
}else
{
holder = (ViewHolder)convertView.getTag();
}
holder.img.setBackgroundResource((Integer)data.get(position).get("img"));
holder.title.setText((String)data.get(position).get("title"));
holder.info.setText((String)data.get(position).get("info"));

return convertView;
}

}
}

運行結果如下:


實例二:Gallery上應用BaseAdapter

main.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width
="fill_parent"
android:layout_height
="fill_parent"
android:orientation
="vertical" >

<ImageView
android:id="@+id/img"
android:layout_width
="480px"
android:layout_height
="480px"
android:layout_gravity
="center"
/>
<Gallery
android:id="@+id/gallery"
android:layout_width
="fill_parent"
android:layout_height
="wrap_content"
android:spacing
="3dp"
android:layout_gravity
="bottom"
/>

</LinearLayout>

Activity:這部分里的getView沒有優化,調試了很久還沒調通,暫時還是用的最基本的方法。會專門找個時間把Gallery內存泄露的部分寫一下,因為圖片資源很多的時候會引起out of memory的錯誤

package com.loulijun.demo16;

import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.view.View;
import android.view.ViewGroup;
import android.widget.AdapterView;
import android.widget.BaseAdapter;
import android.widget.Gallery;
import android.widget.ImageView;

public class Demo16Activity extends Activity {
private Gallery mGallery;
private ImageView mImg;
//圖片數組
private int[] pics = {
R.drawable.pic1,
R.drawable.pic2,
R.drawable.pic3,
R.drawable.pic4,
R.drawable.pic5,
R.drawable.pic6
};
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
mImg = (ImageView)findViewById(R.id.img);
mGallery = (Gallery)findViewById(R.id.gallery);
MyAdapter adapter = new MyAdapter(this);
mGallery.setAdapter(adapter);
mGallery.setOnItemClickListener(new Gallery.OnItemClickListener()
{

@Override
public void onItemClick(AdapterView<?> adapter, View view, int position,
long arg3) {
mImg.setImageResource(pics[position]);
}

});
}

//內部類
class MyAdapter extends BaseAdapter
{
//用來接收傳遞過來的Context上下文對象
private Context context;

//構造函數
public MyAdapter(Context context)
{
this.context = context;
}
@Override
public int getCount() {
//返回圖片數組大小
return pics.length;
}

@Override
public Object getItem(int position) {
//根據選中項返回索引位置
return position;
}

@Override
public long getItemId(int position) {
//根據選中項id返回索引位置
return position;
}
//未優化的getView,這部分可以使用recycle()釋放內存、或者BitmapFacotry.Options縮小,或者軟引用,或者控制圖片資源大小等等很多方法,找時間專門寫
@Override
public View getView(int position, View convertView, ViewGroup parent) {
ImageView img = new ImageView(context);
img.setAdjustViewBounds(true);
img.setImageResource(pics[position]);
img.setScaleType(ImageView.ScaleType.FIT_XY);
img.setLayoutParams(new Gallery.LayoutParams(120,120));

return img;
}
}
}

運行效果:原理都是一樣,只不過是布局加載的時候會有區別,不過就這個小區別也讓人夠惱火的了



文章精選:

http://www.cnblogs.com/over140/archive/2010/12/03/1895128.html






免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM