A while ago I wrote Android-BitmapMemoryCache, a cache based off of LruCache
which would cache Android Bitmap objects in memory in a clever way. You can get
the full details from this earlier post
[http://www.senab.co.uk/2012/07/01/android-bitmap-caching-revisited/], but the
bottom line is that it knew when a Bitmap was no longer being used, and so would
recycle it.
I left it like that the past 5 months and I knew it worked. I was aware though,
that developers were looking for something a littlAs you may or not know, I released a small library as part of the work I did for
photup (it was actually created before that) which contained an ImageView which
could be scaled, dragged and double-tapped. Even though I released it onto
GitHub about 2 months ago, I haven’t really maintained it since. Until now. I’ve
spent a good few days improving it, making it better and easier to use, and I
think I’ve achieved both in today’s release: v1.1.
Sample Application
I’ve uploaded the sample app to GoFollowing on from yesterday’s post
[http://www.senab.co.uk/2012/05/23/pull-to-refresh-indicator-concept/] about
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’