一.ViewPager+Fragment 预加载
ViewPager的预加载,是指ViewPager的内部加载数据机制,它会默认至少预加载一个相邻的ViewPager内的Fragment页数据。
如果设置 viewpager.setOffscreenPageLimit(0); 会发现没有效果。
可以查看ViewPager.java源码我们知道,ViewPager默认必须预加载一个相邻页面的数据。
public class ViewPager extends ViewGroup { ... private static final int DEFAULT_OFFSCREEN_PAGES = 1; ... /** * Set the number of pages that should be retained to either side of the * current page in the view hierarchy in an idle state. Pages beyond this * limit will be recreated from the adapter when needed. * * <p>This is offered as an optimization. If you know in advance the number * of pages you will need to support or have lazy-loading mechanisms in place * on your pages, tweaking this setting can have benefits in perceived smoothness * of paging animations and interaction. If you have a small number of pages (3-4) * that you can keep active all at once, less time will be spent in layout for * newly created view subtrees as the user pages back and forth.</p> * * <p>You should keep this limit low, especially if your pages have complex layouts. * This setting defaults to 1.</p> * * @param limit How many pages will be kept offscreen in an idle state. */ public void setOffscreenPageLimit(int limit) { if (limit < DEFAULT_OFFSCREEN_PAGES) { Log.w(TAG, "Requested offscreen page limit " + limit + " too small; defaulting to " + DEFAULT_OFFSCREEN_PAGES); limit = DEFAULT_OFFSCREEN_PAGES; } if (limit != mOffscreenPageLimit) { mOffscreenPageLimit = limit; populate(); } } ... }
如果确实有时候非要相邻的Fragment页面需要实时显示的时候就要刷新数据,我们可以使用Fragment里的一个方法。
重写 public void setUserVisibleHint(boolean isVisibleToUser) {...} 来处理请求刷新数据。
重写 public void setUserVisibleHint(boolean isVisibleToUser) {...} 来处理请求刷新数据。
当然也有很多其他方法来解决页面立即刷新问题,比如:利用EventBus监听事件刷新,或者FragmentManager来控制Fragment响应事件的触发更新等等。
二.FragmentStatePagerAdapter 和 FragmentPagerAdapter
ViewPager 经常和 Fragment 一起使用,并且提供了专门的 FragmentPagerAdapter 和 FragmentStatePagerAdapter 类供 Fragment 中的 ViewPager 使用。
1.FragmentStatePagerAdapter
Implementation of PagerAdapter that uses a Fragment to manage each page. This class also handles saving and restoring of fragment's state.This version of the pager is more useful when there are a large number of pages, working more like a list view.
When pages are not visible to the user, their entire fragment may be destroyed, only keeping the saved state of that fragment.
This allows the pager to hold on to much less memory associated with each visited page as compared to FragmentPagerAdapter at the cost of potentially more overhead when switching between pages.
When using FragmentPagerAdapter the host ViewPager must have a valid ID set.
Subclasses only need to implement getItem(int) and getCount() to have a working adapter.
从FragmentStatePagerAdapter的Api可知。当ViewPager管理的页面有大量数据时候,也就是如果viewpager管理的页面是一个ListView时候,推荐使用FragmentStatePagerAdapter。这是因为FragmentStatePagerAdapter在页面不可见的时候,会销毁这个Fragment。所以FragmentStatePagerAdapter比FragmentPagerAdapter占用内存更小。
This version of the pager is best for use when there are a handful of typically more static fragments to be paged through, such as a set of tabs. The fragment of each page the user visits will be kept in memory,
though its view hierarchy may be destroyed when not visible. This can result in using a significant amount of memory since fragment instances can hold on to an arbitrary amount of state.
For larger sets of pages, consider FragmentStatePagerAdapter.
When using FragmentPagerAdapter the host ViewPager must have a valid ID set.
Subclasses only need to implement getItem(int) and getCount() to have a working adapter.
从FragmentPagerAdapter的Api也同样了解到,当页面有大量数据加载的时候推荐使用FragmentStatePagerAdapter,FragmentPagerAdapter 创建的 fragment 永远不会被销毁,一般用于只有少量固定的 fragment 时,可以选择 FragmentPagerAdapter。
最后说一点,在内存优化上,RecyclerView要比ViewPager优秀些。推荐大家优先考虑使用RecyclerView 实现。
2.FragmentPagerAdapter
Implementation of PagerAdapter that represents each page as a Fragment that is persistently kept in the fragment manager as long as the user can return to the page.This version of the pager is best for use when there are a handful of typically more static fragments to be paged through, such as a set of tabs. The fragment of each page the user visits will be kept in memory,
though its view hierarchy may be destroyed when not visible. This can result in using a significant amount of memory since fragment instances can hold on to an arbitrary amount of state.
For larger sets of pages, consider FragmentStatePagerAdapter.
When using FragmentPagerAdapter the host ViewPager must have a valid ID set.
Subclasses only need to implement getItem(int) and getCount() to have a working adapter.
从FragmentPagerAdapter的Api也同样了解到,当页面有大量数据加载的时候推荐使用FragmentStatePagerAdapter,FragmentPagerAdapter 创建的 fragment 永远不会被销毁,一般用于只有少量固定的 fragment 时,可以选择 FragmentPagerAdapter。
最后说一点,在内存优化上,RecyclerView要比ViewPager优秀些。推荐大家优先考虑使用RecyclerView 实现。