https://github.com/imbryk/LoopingViewPager

An android ViewPager extension allowing infinite scrolling
https://github.com/imbryk/LoopingViewPager

Last synced: about 6 hours ago
JSON representation

An android ViewPager extension allowing infinite scrolling

• Host: GitHub
• URL: https://github.com/imbryk/LoopingViewPager
• Owner: imbryk
• License: apache-2.0
• Created: 2013-09-15T14:28:58.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2019-04-06T19:37:43.000Z (over 5 years ago)
• Last Synced: 2023-10-25T22:24:26.815Z (about 1 year ago)
• Language: Java
• Size: 521 KB
• Stars: 988
• Watchers: 42
• Forks: 245
• Open Issues: 22
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-android-ui - https://github.com/imbryk/LoopingViewPager

README

        
NO LONGER MAINTAINED

====================

LoopingViewPager

================

An android ViewPager extension allowing infinite scrolling.

You can use it with "standart" `PagerAdapter` (inflating the pager with `Views`),   

but you can also use `FragmentPagerAdapter` which allows you to fill the pager with `Fragments`!   

The ViewPager will actually create 2 additional Views/Fragments to fake the infinite loop.

This ViewPager is fully compatible with [ViewPagerIndicator][1], and [PagerSlidingTabStrip][2]!

Usage

-----

To use it simply change `` to ``

If your `PagerAdapter` is used only to create `Views` (i.e. you don't use `FragmentPagerAdapter` or `FragmentStatePagerAdapter`),

then no more code changes are needed!

If you want to use `LoopViewPager` with `FragmentPagerAdapter` or `FragmentStatePagerAdapter`

additional changes in the adapter must be done.    

The adapter must be prepared to create 2 extra items e.g.:    

* The original adapter creates 4 items: `[0,1,2,3]`   

* The modified adapter will have to create 6 items `[0,1,2,3,4,5]`   

* with mapping `realPosition=(position-1)%count`   

* `[0->3, 1->0, 2->1, 3->2, 4->3, 5->0]`

Sometimes "blinking" can be seen when paginating to first or last view (e.g. when you have a `NetworkImageView` in your layout). 

To remove this effect, simply call setBoundaryCaching( true ) on your `LoopViewPager`,

or change `DEFAULT_BOUNDARY_CASHING` to true, if you want to set boundary caching

on all `LoopViewPager` instances. This will prevent the first and last element from being destroyed,

and every time they need to be displayed the existing instances will be used.

Sample

------

You can see a sample usage on [ViewPagerIndicator fork][3] (by [Jake Wharton][5])   

or on [PagerSlidingTabStrip fork][4] (by [Andreas Stütz][6])   

License

=======

    Copyright 2013 Leszek Mzyk

    Licensed under the Apache License, Version 2.0 (the "License");

    you may not use this file except in compliance with the License.

    You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software

    distributed under the License is distributed on an "AS IS" BASIS,

    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

    See the License for the specific language governing permissions and

    limitations under the License.

    

    

 [1]: https://github.com/JakeWharton/Android-ViewPagerIndicator

 [2]: https://github.com/astuetz/PagerSlidingTabStrip

 [3]: https://github.com/imbryk/Android-ViewPagerIndicator/compare/master...loopingViewPager-demo

 [4]: https://github.com/imbryk/PagerSlidingTabStrip/compare/master...loopingViewPager-demo

 [5]: https://github.com/JakeWharton

 [6]: https://github.com/astuetz