Add support for using Volley to load remote images instead of UIL
1. Gives us Caching
2. Load images at full resolution, rather than hardcode them. This is done by trying to fetch an image at highest width possible for the particular view. If it 500s, we assume that the image is smaller than the requested width and just request the full size image
3. Created a MediaWikiImageView, to which you can pass a Media object and it will display it. Takes care of sizing, etc. Optionally you can also specify a view to use as the 'loading' view.
TODO:
Loading from content:// URIs still use UIL. Need to write a Volley HTTP Stack that can fake responses for content:// URIs.
GitHub: https://github.com/wikimedia/apps-android-commons/pull/1
Change-Id: Ia21a7b19fefa552d5a0b013085d0f5f1f80dc5ff
We can't use formatted strings directly because it breaks with
our localization tools. Grab an HTML string and turn it into
a formatted string.
Localized versions will have to be updated still, but that should
happen automatically at TWN.
Where we don't specifically need action-bar or fragment-related stuff,
it's cleaner to use regular getActivity(). If/when the action bar shows
up in the general support libraries that'll be easier to update.
Saves original file into the SD card "Downloads" directory via
Android's DownloadManager service.
On Gingerbread the notification vanishes after downloda, but we
force the gallery to reindex the downloads area so you can still
manually bump over to Gallery.
On ICS/JB the notification hangs around and can be used to open
the saved file directly.
Note that on Gingerbread we have to download over HTTP because
DownloadManager didn't support HTTPS.
Included copy of stock 'upload' icon, flipped it for 'download'.
Follows sequence 'Foo.jpeg', 'Foo 2.jpeg', 'Foo 3.jpeg' etc until one is
found that doesn't exist, then we send up the upload. This avoids most
typical conflicts scenarios.
Still can produce a conflict if you start uploads near-simultaneously,
but this is better than none.
Strangely, the \}\} regex seems to match the | character. Weird,
confusing and scary. This *might* be an ICU Regex vs Java native
Regex thing, or it might be something more subtle / obvious that
I am missing.
However since we're simply doing character matches, doing a simple
equals should suffice for this.
Goddamn wikitext.
Bug: 47380
