Over the past few months I've been receiving a ton of emails, tweets, G+
mentions and GitHub issues in connection with my open source libraries. So I
thought I would set out what my plan is for them in the future, and the order in
which I'll be tackling the backlog.
The library which is taking up the majority of my personal dev time at the
moment before it hits v1.0. I've done this library a bit differently that my
previous ones as I've developed it in the open, whereas So this is my first blog post on ActionBar-PullToRefresh. I've been mainly
talking about it on Google+ up until now as it simply was not ready for
production use. Well today I tagged and push v0.4 of the project, which adds the
main missing feature: automatically styling based on your Action Bar style.
First of all here's a video of how it works:
So here's a non-exhaustive list of it's features:
* By default mirrors the Gmail implementation: grow from center progress bar.
* ListVieAndroid-PullToRefresh was started about 18 months ago, as I needed it for a
project (Friendcaster). Since then I’ve kept maintaining the project, pushing it
forward and adding new features.
Well today I’m stopping development. There are two reasons for this, the first
is that it is feature complete. The second reason is that the volume of ‘issues’
I get is taking up too much of my time.
At the end of the day, it’s open source. If you want something added or fixed,
you have the source to do so.Following on from yesterday’s post
making Pull-to-Refresh more discoverable, today I’ve made it a bit more
customisable. As you can see above, instead of the standard Android
indeterminate spinner we have Andy spinning instead. This drawable is completely
customisable by you.
That’s not all as I’ve removed the rotating arrows, and added an effect so that
the drawable (in this case Andy) is rotated based on how far you’Lots of evangelist Android developers dislike the Pull-to-Refresh pattern on
Android. For instance Cyril Mottier wrote a whole blog post
[http://android.cyrilmottier.com/?p=598] detailing his views and it’s well worth
a read. The trouble with his arguments (in my opinion) is that he’s far too
‘pure’ in his views on using patterns from other platforms. For me, getting
something which works well and people can use is more important than keeping to
Google’s Pure Android