-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'load more' functionality #4
Comments
I will add this eventually. Note that it should be designed in a fashion similar to |
I am working on integrating this into the SVPullToRefresh class, though I only get an hour here and there. I'll have something soon, and I'd love some feedback. Thanks a lot; this is my first contribution to GitHub, so I am still navigating my way around. On May 3, 2012, at 4:22 PM, Sam Vermette wrote:
|
I have it working now so that the user can drag past the last cell and trigger the load. I created a property in the SVPullToRefresh class that allows you to set either the section or row load limit. The SVPullToRefresh and the DragToLoad can be called with a single method This is one implementation style. The other would be to automatically load the next portion of content once you scroll past a certain point in the scrollView/tableView. I can work on that implementation, as well. Perhaps by adding a third addPullToRefresh... method similar to |
I've renamed the perpetual load handler to |
See my latest comment on pull request #10. Will leave this issue open until someone else (or I) come up with a decent implementation of the "load more" functionality. Sorry if I sound rude, I'm just trying to keep SVPullToRefresh a high-quality component. |
I just added support for infinite scrolling. It might require a little more testing but seems to do the job pretty good so far. Will close the issue as the core functionality is there, but feel free to report bugs related to it though. |
Transfer pull request from origin repo
Please, add 'load more' functionality at the bottom of the table.
Thanks !
The text was updated successfully, but these errors were encountered: