来自android开发者(创建列表和卡片):
RecyclerView小部件是一个更高级和灵活的版本 列表视图。
好吧,这听起来很酷,但当我看到这张示例图片时,我真的很困惑这两者之间的区别。
上面的图片可以通过ListView使用自定义适配器轻松创建。
那么,在什么情况下应该使用RecyclerView呢?
来自android开发者(创建列表和卡片):
RecyclerView小部件是一个更高级和灵活的版本 列表视图。
好吧,这听起来很酷,但当我看到这张示例图片时,我真的很困惑这两者之间的区别。
上面的图片可以通过ListView使用自定义适配器轻松创建。
那么,在什么情况下应该使用RecyclerView呢?
当前回答
RecyclerView相对于listview的优点:
默认包含ViewHolder。 简单的动画。 支持水平,网格和交错布局
listView相对于recyclerView的优点:
易于添加分隔线。 可以使用内置的arrayAdapter简单的普通列表 支持页眉和页脚。 支持OnItemClickListner。
其他回答
I think the main and biggest difference they have is that ListView looks for the position of the item while creating or putting it, on the other hand RecyclerView looks for the type of the item. if there is another item created with the same type RecyclerView does not create it again. It asks first adapter and then asks to recycledpool, if recycled pool says "yeah I've created a type similar to it", then RecyclerView doesn't try to create same type. ListView doesn't have a this kind of pooling mechanism.
RecyclerView相对于listview的优点:
默认包含ViewHolder。 简单的动画。 支持水平,网格和交错布局
listView相对于recyclerView的优点:
易于添加分隔线。 可以使用内置的arrayAdapter简单的普通列表 支持页眉和页脚。 支持OnItemClickListner。
ListView和RecyclerView之间有很多区别,但你应该特别注意以下几点:
ViewHolder模式在ListView中是完全可选的,但它被烘焙到RecyclerView中。 ListView只支持垂直滚动,但RecyclerView并不局限于垂直滚动列表。
ListView是RecyclerView的祖先。有很多事情ListView没有做,或者做得不好。如果您要收集ListView的缺点,并通过将问题抽象到不同的域来解决问题,那么您最终会得到类似于回收器视图的东西。下面是ListViews的主要问题点:
Didn't enforce View Reuse for same item types (look at one of the adapters that are used in a ListView, if you study the getView method you will see that nothing prevents a programmer from creating a new view for every row even if one is passed in via the convertView variable) Didn't prevent costly findViewById uses(Even if you were recycling views as noted above it was possible for devs to be calling findViewById to update the displayed contents of child views. The main purpose of the ViewHolder pattern in ListViews was to cache the findViewById calls. However this was only available if you knew about it as it wasn't part of the platform at all) Only supported Vertical Scrolling with Row displayed Views (Recycler view doesn't care about where views are placed and how they are moved, it's abstracted into a LayoutManager. A Recycler can therefore support the traditional ListView as shown above, as well as things like the GridView, but it isn't limited to that, it can do more, but you have to do the programming foot work to make it happen). Animations to added/removed was not a use case that was considered. It was completely up to you to figure out how go about this (compare the RecyclerView. Adapter classes notify* method offerings v. ListViews to get an idea).
简而言之,RecyclerView是一个更灵活的ListView,尽管你可能需要做更多的编码工作。
除了以上差异之外,还有以下几个:
RV separates view creation and binding of data to view. In LV, you need to check if convertView is null or not for creating view, before binding data to it. So, in case of RV, view will be created only when it is needed but in case of LV, one can miss the check for convertview and will create view everytime. Switching between Grid and List is more easy now with LayoutManager. No need to notify and update all items, even if only single item is changed. One had to implement view caching in case of LV. It is provided in RV by default. (There is difference between view caching n recycling.) Very easy item animations in case of RV.