最近偶然在eoe论坛上看到了一Viewholder的一种新的写法,感觉还不错,可以省下大量的重复代码,貌似性能上也没什么损耗!收藏的用一下;
我们一贯的写法都是每个listView的写一个Viewholder,然后在里面声明一些需要的View的变量,然后在getView()中操作
ViewHolder holder =
null
;
if
(convertView ==
null
){
convertView = mInflater.inflate(R.layout.xxx
null
);
holder =
new
ViewHolder();
holder.tvXXX = (TextView)findViewById(R.id.xxx);
//...一连串的findViewById
}
else
{
holder = (ViewHolder) convertView.getTag();
}
private
static
class
ViewHolder{
TextView tvXXX;
//很多view的定义
}
这大概是最常规的写法了,一个listview里面写一个,写多了的确烦;看看别人介绍的一种写法
public class ViewHolder {
// I added a generic return type to reduce the casting noise in client code
@SuppressWarnings("unchecked")
public static <T extends View> T get(View view, int id) {
SparseArray<View> viewHolder = (SparseArray<View>) view.getTag();
if (viewHolder == null) {
viewHolder = new SparseArray<View>();
view.setTag(viewHolder);
}
View childView = viewHolder.get(id);
if (childView == null) {
childView = view.findViewById(id);
viewHolder.put(id, childView);
}
return (T) childView;
}
}
一种类,其它地方全部可以用了,在getview()里面用起来也相当简单了,连非空判断,setTag也完处理了;
唯一不同的地方是用SparseArray来存储要用的childView了;SparseArray是HashMap的增加版,性能略有提高;
@Override
public View getView(int position, View convertView, ViewGroup parent) {
if (convertView == null) {
convertView = LayoutInflater.from(context) .inflate(R.layout.banana_phone, parent, false);
}
ImageView bananaView = ViewHolder.get(convertView, R.id.banana);
TextView phoneView = ViewHolder.get(convertView, R.id.phone);
BananaPhone bananaPhone = getItem(position);
phoneView.setText(bananaPhone.getPhone());
bananaView.setImageResource(bananaPhone.getBanana());
return convertView;
}