TwinklingRefreshLayout
RefreshLayout that support for OverScroll and better than iOS. 支持下拉刷新和上拉加载的RefreshLayout,自带越界回弹效果,支持RecyclerView,AbsListView,ScrollView,WebView
Top Related Projects
🔥下拉刷新、上拉加载、二级刷新、淘宝二楼、RefreshLayout、OverScroll,Android智能下拉刷新框架,支持越界回弹、越界拖动,具有极强的扩展性,集成了几十种炫酷的Header和 Footer。
Ultra Pull to Refresh for Android. Support all the views.
Phoenix Pull-to-Refresh
A reusable pull-to-refresh and pull-to-loadmore widget
A pull to refresh layout for android, the RecyclerRefreshLayout is based on the SwipeRefreshLayout. support all the views, highly customizable, code simplicity, etc. really a practical RefreshLayout!
Quick Overview
TwinklingRefreshLayout is an Android library that provides a customizable pull-to-refresh layout with various animation effects. It offers a smooth and visually appealing way to implement refresh and load more functionality in Android applications, with support for different header and footer styles.
Pros
- Highly customizable with multiple built-in refresh header and footer styles
- Smooth animations and transitions for a polished user experience
- Supports both pull-to-refresh and load-more functionality
- Easy integration with existing Android projects
Cons
- Limited documentation, especially for advanced customization
- Some reported issues with compatibility on certain Android versions
- May require additional effort to integrate with specific UI frameworks or architectures
- Not actively maintained, with the last update being several years ago
Code Examples
- Basic implementation of TwinklingRefreshLayout:
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout
android:id="@+id/refreshLayout"
android:layout_width="match_parent"
android:layout_height="match_parent">
<ListView
android:id="@+id/listView"
android:layout_width="match_parent"
android:layout_height="match_parent"/>
</com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout>
- Setting up refresh and load more listeners:
TwinklingRefreshLayout refreshLayout = findViewById(R.id.refreshLayout);
refreshLayout.setOnRefreshListener(new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Handle refresh action
refreshLayout.finishRefreshing();
}
@Override
public void onLoadMore(TwinklingRefreshLayout refreshLayout) {
// Handle load more action
refreshLayout.finishLoadmore();
}
});
- Customizing the refresh header:
SinaRefreshView headerView = new SinaRefreshView(this);
headerView.setArrowResource(R.drawable.arrow);
headerView.setTextColor(0xff745D5C);
refreshLayout.setHeaderView(headerView);
Getting Started
- Add the dependency to your app's
build.gradle
file:
dependencies {
implementation 'com.lcodecorex:tkrefreshlayout:1.0.7'
}
- Add TwinklingRefreshLayout to your layout XML:
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout
android:id="@+id/refreshLayout"
android:layout_width="match_parent"
android:layout_height="match_parent">
<!-- Your content view here -->
</com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout>
- Initialize and configure the layout in your Activity or Fragment:
TwinklingRefreshLayout refreshLayout = findViewById(R.id.refreshLayout);
refreshLayout.setOnRefreshListener(new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Handle refresh
}
});
Competitor Comparisons
🔥下拉刷新、上拉加载、二级刷新、淘宝二楼、RefreshLayout、OverScroll,Android智能下拉刷新框架,支持越界回弹、越界拖动,具有极强的扩展性,集成了几十种炫酷的Header和 Footer。
Pros of SmartRefreshLayout
- More comprehensive and feature-rich, offering a wider variety of refresh styles and animations
- Better documentation and examples, making it easier for developers to implement and customize
- Larger community and more frequent updates, ensuring better long-term support and bug fixes
Cons of SmartRefreshLayout
- Slightly more complex to set up and configure due to its extensive feature set
- Potentially higher memory footprint and performance overhead for simpler use cases
Code Comparison
TwinklingRefreshLayout:
RefreshListenerAdapter refreshListener = new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Refresh logic here
}
};
refreshLayout.setOnRefreshListener(refreshListener);
SmartRefreshLayout:
refreshLayout.setOnRefreshListener(new OnRefreshListener() {
@Override
public void onRefresh(RefreshLayout refreshlayout) {
// Refresh logic here
}
});
Both libraries offer similar basic functionality for implementing pull-to-refresh, but SmartRefreshLayout provides more advanced features and customization options. While TwinklingRefreshLayout is simpler and may be sufficient for basic needs, SmartRefreshLayout is better suited for projects requiring more complex refresh behaviors and animations.
Ultra Pull to Refresh for Android. Support all the views.
Pros of android-Ultra-Pull-To-Refresh
- More mature and widely adopted project with a larger community
- Supports a wider range of Android versions (API 8+)
- Highly customizable with various built-in header styles
Cons of android-Ultra-Pull-To-Refresh
- Less active development and maintenance in recent years
- Limited to pull-to-refresh functionality, lacking additional features like load more
Code Comparison
TwinklingRefreshLayout:
RefreshListenerAdapter refreshListener = new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Refresh logic here
}
};
refreshLayout.setOnRefreshListener(refreshListener);
android-Ultra-Pull-To-Refresh:
mPtrFrame.setPtrHandler(new PtrHandler() {
@Override
public void onRefreshBegin(PtrFrameLayout frame) {
// Refresh logic here
}
});
Both libraries offer similar ease of use for implementing basic pull-to-refresh functionality. TwinklingRefreshLayout provides a more modern API with additional features, while android-Ultra-Pull-To-Refresh focuses on core pull-to-refresh functionality with extensive customization options.
TwinklingRefreshLayout is more suitable for projects requiring additional features like load more, while android-Ultra-Pull-To-Refresh is better for projects that need broad device compatibility and extensive customization of the pull-to-refresh behavior.
Phoenix Pull-to-Refresh
Pros of Phoenix
- Visually appealing and customizable animation effects
- Smooth and fluid pull-to-refresh experience
- Well-documented and easy to implement
Cons of Phoenix
- Limited to pull-to-refresh functionality only
- Less flexible compared to TwinklingRefreshLayout's feature set
- May require more setup for complex use cases
Code Comparison
Phoenix:
val refreshLayout = findViewById<PullToRefreshView>(R.id.pull_to_refresh)
refreshLayout.setOnRefreshListener {
// Refresh logic here
refreshLayout.setRefreshing(false)
}
TwinklingRefreshLayout:
RefreshListenerAdapter refreshListener = new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Refresh logic here
refreshLayout.finishRefreshing();
}
};
refreshLayout.setOnRefreshListener(refreshListener);
Summary
Phoenix offers a visually appealing pull-to-refresh experience with smooth animations, while TwinklingRefreshLayout provides a more comprehensive set of features for both refreshing and loading. Phoenix is easier to implement for simple use cases, but TwinklingRefreshLayout offers greater flexibility for complex scenarios. The choice between the two depends on the specific requirements of your project and the desired user experience.
Pros of WaveSwipeRefreshLayout
- Unique wave animation provides a visually appealing and engaging user experience
- Lightweight implementation with minimal dependencies
- Easy to customize wave color and height
Cons of WaveSwipeRefreshLayout
- Limited to pull-to-refresh functionality, lacking additional features like load more
- Less flexible in terms of customization options compared to TwinklingRefreshLayout
- May not be suitable for complex layouts or nested scrolling scenarios
Code Comparison
WaveSwipeRefreshLayout:
WaveSwipeRefreshLayout mWaveSwipeRefreshLayout = (WaveSwipeRefreshLayout) findViewById(R.id.main_swipe);
mWaveSwipeRefreshLayout.setOnRefreshListener(new WaveSwipeRefreshLayout.OnRefreshListener() {
@Override public void onRefresh() {
// Refresh action
}
});
TwinklingRefreshLayout:
TwinklingRefreshLayout refreshLayout = (TwinklingRefreshLayout) findViewById(R.id.refreshLayout);
refreshLayout.setOnRefreshListener(new RefreshListenerAdapter(){
@Override
public void onRefresh(final TwinklingRefreshLayout refreshLayout) {
// Refresh action
}
});
Both libraries offer simple implementation for pull-to-refresh functionality. WaveSwipeRefreshLayout focuses on a unique wave animation, while TwinklingRefreshLayout provides more customization options and additional features like load more. The choice between the two depends on the specific requirements of your project and the desired user experience.
A reusable pull-to-refresh and pull-to-loadmore widget
Pros of SwipeToLoadLayout
- More customizable with support for various view types (ListView, GridView, RecyclerView, etc.)
- Offers both pull-to-refresh and push-to-load-more functionality
- Simpler implementation with fewer dependencies
Cons of SwipeToLoadLayout
- Less visually appealing default animations compared to TwinklingRefreshLayout
- Fewer built-in header and footer styles
- Less active development and community support
Code Comparison
SwipeToLoadLayout:
<com.aspsine.swipetoloadlayout.SwipeToLoadLayout
android:id="@+id/swipeToLoadLayout"
android:layout_width="match_parent"
android:layout_height="match_parent">
<android.support.v7.widget.RecyclerView
android:id="@+id/swipe_target"
android:layout_width="match_parent"
android:layout_height="match_parent" />
</com.aspsine.swipetoloadlayout.SwipeToLoadLayout>
TwinklingRefreshLayout:
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout
android:id="@+id/refreshLayout"
android:layout_width="match_parent"
android:layout_height="match_parent">
<android.support.v7.widget.RecyclerView
android:id="@+id/rv"
android:layout_width="match_parent"
android:layout_height="match_parent" />
</com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout>
Both libraries offer similar XML structure for implementation, with minor differences in naming conventions and attributes.
A pull to refresh layout for android, the RecyclerRefreshLayout is based on the SwipeRefreshLayout. support all the views, highly customizable, code simplicity, etc. really a practical RefreshLayout!
Pros of RecyclerRefreshLayout
- More lightweight and focused specifically on RecyclerView
- Simpler implementation with fewer customization options
- Better performance due to its specialized nature
Cons of RecyclerRefreshLayout
- Less flexible compared to TwinklingRefreshLayout's support for multiple view types
- Fewer animation options and visual customizations
- Limited to RecyclerView, while TwinklingRefreshLayout supports various layouts
Code Comparison
RecyclerRefreshLayout:
RecyclerRefreshLayout refreshLayout = findViewById(R.id.refresh_layout);
refreshLayout.setOnRefreshListener(new RecyclerRefreshLayout.OnRefreshListener() {
@Override
public void onRefresh() {
// Refresh logic here
}
});
TwinklingRefreshLayout:
TwinklingRefreshLayout refreshLayout = findViewById(R.id.refresh_layout);
refreshLayout.setOnRefreshListener(new RefreshListenerAdapter() {
@Override
public void onRefresh(TwinklingRefreshLayout refreshLayout) {
// Refresh logic here
}
});
Both layouts offer similar basic functionality for implementing pull-to-refresh. However, TwinklingRefreshLayout provides more extensive customization options and supports various view types, while RecyclerRefreshLayout is more focused on RecyclerView implementations.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
ãDECREEPTEDã
TwinklingRefreshLayout
TwinklingRefreshLayout extended the thoughts of SwipeRefreshLayout,using a ViewGroup to include a list of Views, to maintain its low coupling and high versatility. Follows are its main features.
- New overscroll animations, running smoothly, much better than iOS.
- Support RecyclerView, ScrollView, AbsListView, WebView and so on.
- Support to load more.
- Default support cross-border rebound.
- You can open a pure bounds rebound mode.
- Lots of methods in the class OnRefreshListener.
- It provides an interface to the callback during the sliding coefficient. Personalized offer good support.
- NestedScroll,CoordinatorLayout
Any View is supported.
Demo
You can download these Videos for more details.
- Music - ListView - FixedHeader
- Food - RecyclerView - PureScrollMode
- Science - GridView - SinaHeader
- Photo - RecyclerView - BezierLayout
- Story - ScrollView - GoogleDotView
- Dribbble - WebView - FloatRefresh
Usage
1.Add a gradle dependency.
compile 'com.lcodecorex:tkrefreshlayout:1.0.7'
2.Add TwinklingRefreshLayout in the layout xml.
<?xml version="1.0" encoding="utf-8"?>
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:id="@+id/refreshLayout"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:tr_wave_height="180dp"
app:tr_head_height="100dp">
<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:overScrollMode="never"
android:background="#fff" />
</com.lcodecore.library.TwinklingRefreshLayout>
To get better effect, you'd better add code android:overScrollMode="never"
to the childView.
3.Coding in the Activity or Fragment.
Change of state need to be manually controlled.
refreshLayout.setOnRefreshListener(new RefreshListenerAdapter(){
@Override
public void onRefresh(final TwinklingRefreshLayout refreshLayout) {
new Handler().postDelayed(new Runnable() {
@Override
public void run() {
refreshLayout.finishRefreshing();
}
},2000);
}
@Override
public void onLoadMore(final TwinklingRefreshLayout refreshLayout) {
new Handler().postDelayed(new Runnable() {
@Override
public void run() {
refreshLayout.finishLoadmore();
}
},2000);
}
});
}
Use finishRefreshing() method to end refresh, finishLoadmore() method to end load more. OnRefreshListener there are other methods, you can choose need to override.
And if you want you refresh automatically, call the method startRefresh().
setWaveHeightãsetHeaderHeightãsetBottomHeightãsetOverScrollHeight
- setMaxHeadHeight is used To set the maximum height of the head can be stretched.
- setHeaderHeight is used to set the standard head height.
- setMaxBottomHeight.
- setBottomHeight is used to set the Bottom height.
- setOverScrollHeight is used to set the max height of overscroll.
And now dp value is supported.
setEnableRefreshãsetEnableLoadmore
Flexible settings for whether to disable the pulling-down mode.
setHeaderView(IHeaderView headerView)ãsetBottomView(IBottomView bottomView)
setEnableOverScroll
Whether to allow overscroll mode, opened by default.
setOverScrollTopShowãsetOverScrollBottomShowãsetOverScrollRefreshShow
Whether to allow the display refresh control on overscrolling, the default is true.
setPureScrollModeOn()
To open the pure overscroll mode so that refreshView would gone permanently.
setAutoLoadMore
if open the loadmore mode after overscrolling bottom automatically.
addFixedExHeader
Allow you to add a view fixed on the top.
startRefreshãstartLoadMoreãfinishRefreshingãfinishLoadmore
setFloatRefresh(boolean)
Make refresh-animation like SwipeRefreshLayout.
setTargetView(View view)
Set the target view that you can scroll.
setDefaultHeaderãsetDefaultFooter
static methods aims to set a default header/footer in a/an Application/Activity.
4.Attributes
- tr_max_head_height - Flexible head height
- tr_head_height - Head height
- tr_max_bottom_height
- tr_bottom_height - Bottom height
- tr_overscroll_height - OverScroll Height
- tr_enable_refresh - default is true
- tr_enable_loadmore - default is true
- tr_pureScrollMode_on - default is false
- tr_overscroll_top_show - default is true
- tr_overscroll_bottom_show - default is true
- tr_enable_overscroll - default is true.
- tr_floatRefresh - open the float-refresh mode.
- tr_autoLoadMore
- tr_enable_keepIView - default is true.
- tr_showRefreshingWhenOverScroll - default is true.
- tr_showLoadingWhenOverScroll - default is true.
Other
1.setOnRefreshListener
- onPullingDown(TwinklingRefreshLayout refreshLayout, float fraction)
- onPullingUp(TwinklingRefreshLayout refreshLayout, float fraction)
- onPullDownReleasing(TwinklingRefreshLayout refreshLayout, float fraction)
- onPullUpReleasing(TwinklingRefreshLayout refreshLayout, float fraction)
- onRefresh(TwinklingRefreshLayout refreshLayout)
- onLoadMore(TwinklingRefreshLayout refreshLayout)
fraction = currentMoveHeight/headHeight OR (fraction = currentMoveHeight/bottomHeight).
3.Header and Footer
BezierLayout(pic 4)
- setWaveColor
- setRippleColor
GoogleDotView(pic 5)
SinaRefreshView(pic 3)
- setArrowResource
- setTextColor
- setPullDownStr
- setReleaseRefreshStr
- setRefreshingStr
ProgressLayout(SwipeRefreshLayout pic 6)
- setProgressBackgroundColorSchemeResource(@ColorRes int colorRes)
- setProgressBackgroundColorSchemeColor(@ColorInt int color)
- setColorSchemeResources(@ColorRes int... colorResIds)
####Footer
BallPulseView(pic 2)
- setNormalColor(@ColorInt int color)
- setAnimatingColor(@ColorInt int color)
LoadingView(pic 3)
Here is more animations.AVLoadingIndicatorViewã
3.Personalize the Header and Footer.
The Header needs to implement IHeaderView interface and Footer in in the same way(IBottomView).
public interface IHeaderView {
View getView();
void onPullingDown(float fraction,float maxHeadHeight,float headHeight);
void onPullReleasing(float fraction,float maxHeadHeight,float headHeight);
void startAnim(float maxHeadHeight,float headHeight);
void reset();
}
getView() method is not allow to return null.
Let's implement a simple refresh dynamic efficiency.
1.Define SinaRefreshHeader extended from FrameLayout and implement IHeaderView interface.
2.Return this in the method getView().
3.Inflate and find Views in the layout xml.
void init() {
if (rootView == null) {
rootView = View.inflate(getContext(), R.layout.view_sinaheader, null);
refreshArrow = (ImageView) rootView.findViewById(R.id.iv_arrow);
refreshTextView = (TextView) rootView.findViewById(R.id.tv);
loadingView = (ImageView) rootView.findViewById(R.id.iv_loading);
addView(rootView);
}
}
4.Override some methods.
@Override
public void onPullingDown(float fraction, float maxHeadHeight, float headHeight) {
if (fraction < 1f) refreshTextView.setText(pullDownStr);
if (fraction > 1f) refreshTextView.setText(releaseRefreshStr);
refreshArrow.setRotation(fraction * headHeight / maxHeadHeight * 180);
}
@Override
public void onPullReleasing(float fraction, float maxHeadHeight, float headHeight) {
if (fraction < 1f) {
refreshTextView.setText(pullDownStr);
refreshArrow.setRotation(fraction * headHeight / maxHeadHeight * 180);
if (refreshArrow.getVisibility() == GONE) {
refreshArrow.setVisibility(VISIBLE);
loadingView.setVisibility(GONE);
}
}
}
@Override
public void startAnim(float maxHeadHeight, float headHeight) {
refreshTextView.setText(refreshingStr);
refreshArrow.setVisibility(GONE);
loadingView.setVisibility(VISIBLE);
}
@Override
public void onFinish(OnAnimEndListener listener) {
listener.onAnimEnd();
}
5.layout xml.
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:orientation="horizontal" android:layout_width="match_parent"
android:layout_height="match_parent"
android:gravity="center">
<ImageView
android:id="@+id/iv_arrow"
android:layout_width="24dp"
android:layout_height="24dp"
android:src="@drawable/ic_arrow"/>
<ImageView
android:id="@+id/iv_loading"
android:visibility="gone"
android:layout_width="34dp"
android:layout_height="34dp"
android:src="@drawable/anim_loading_view"/>
<TextView
android:id="@+id/tv"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="16dp"
android:textSize="16sp"
android:text="pull down to refresh"/>
</LinearLayout>
Pay attention to the using of the parameter fraction
. Such as the code aboverefreshArrow.setRotation(fraction * headHeight / maxHeadHeight * 180)
ï¼fraction * headHeight
is the translationY of the Head and 180 is the angle the arrow would rotateï¼so that we can make the arrow rotate 180 degrees when the translationY is come to the maxHeadHeight.
onPullingDown/onPullingUp onPullReleasing startAnim - be called automatically after the method onRefresh/onLoadMore is called.
Congratulations! Simple to use and simple to Personalise.ï¼To see a more simple example. **TextHeaderView(pic 4)**ï¼ã
NestedScroll
TwinklingRefreshLayout Nested CoordinatorLayout
---layout
<?xml version="1.0" encoding="utf-8"?>
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:id="@+id/refresh"
android:layout_width="match_parent"
android:layout_height="match_parent">
<android.support.design.widget.CoordinatorLayout
android:id="@+id/coord_container"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:addStatesFromChildren="true"
android:fitsSystemWindows="true">
<android.support.design.widget.AppBarLayout
android:id="@+id/appbar_layout"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:clipChildren="false">
<!--...-->
</android.support.design.widget.AppBarLayout>
<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:layout_behavior="@string/appbar_scrolling_view_behavior" />
</android.support.design.widget.CoordinatorLayout>
</com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout>
--- code1
refreshLayout.setTargetView(rv);
Find the RecyclerView/ListView.
--- code2
AppBarLayout appBarLayout = (AppBarLayout) findViewById(R.id.appbar_layout);
appBarLayout.addOnOffsetChangedListener(new AppBarLayout.OnOffsetChangedListener() {
@Override
public void onOffsetChanged(AppBarLayout appBarLayout, int verticalOffset) {
if (verticalOffset >= 0) {
refreshLayout.setEnableRefresh(true);
refreshLayout.setEnableOverScroll(false);
} else {
refreshLayout.setEnableRefresh(false);
refreshLayout.setEnableOverScroll(false);
}
}
});
####CoordinatorLayout nested TwinklingRefreshLayout --- layout
<?xml version="1.0" encoding="utf-8"?>
<android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:id="@+id/coord_container"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:addStatesFromChildren="true"
android:fitsSystemWindows="true">
<com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout
android:id="@+id/refresh"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:layout_behavior="@string/appbar_scrolling_view_behavior">
<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:layout_width="match_parent"
android:layout_height="match_parent" />
</com.lcodecore.tkrefreshlayout.TwinklingRefreshLayout>
</android.support.design.widget.CoordinatorLayout>
Pay attention to layout_behavior="@string/appbar_scrolling_view_behavior"
for TwinklingRefreshLayout.
psï¼Contact me: lcodecore@163.com QQ group: 202640706
If you like this library, you can donate me. Buy me a coffee!
Update Logs
v1.07
- NestedScroll,CoordinateLayout
- Any View
- Keep state when refreshing/loading.
v1.06
- Repair memory leaks of customized Views.
- remove the dependence of AVLoadingIndicatorView.
- Fix bugs of OverScroll when TargetView scrolls at the top/bottom.
- Repair bugs of touching,scroll-event listeners.
- Optimization of interface flicker problems after load-more.
v1.05 Emergency Fix
- Fix the bug of setAutoLoadMore().
- Fix the bug that FixedHeader covered the first item of listview.
- Add onRefreshCanceled()/onLoadmoreCanceled() for RefreshListenerAdapter.
v1.04
- Refactor the code.
- Make animations smoothly.
- Add support to Fixed Header.
- Add support to float refresh mode.
- IHeadView.onFinish(animEndListener) -> Available to run animations before finishRefresh.
v1.03
- more attributes.
- Fix the NullPointerException bug in Fragment.
- Fix the Sliding conflict.
License
Copyright 2016 lcodecorex
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.
Top Related Projects
🔥下拉刷新、上拉加载、二级刷新、淘宝二楼、RefreshLayout、OverScroll,Android智能下拉刷新框架,支持越界回弹、越界拖动,具有极强的扩展性,集成了几十种炫酷的Header和 Footer。
Ultra Pull to Refresh for Android. Support all the views.
Phoenix Pull-to-Refresh
A reusable pull-to-refresh and pull-to-loadmore widget
A pull to refresh layout for android, the RecyclerRefreshLayout is based on the SwipeRefreshLayout. support all the views, highly customizable, code simplicity, etc. really a practical RefreshLayout!
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot