- 20 10月, 2017 1 次提交
-
-
由 pkorth 提交于
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=172750122
-
- 19 10月, 2017 3 次提交
- 18 10月, 2017 7 次提交
-
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
We can use the default themes from Activities and/or Context wrappers to obtain placeholder Drawables, which can be more efficient than forcing callers to call getDrawable when building their request and more powerful/neater than having callers pass in a Theme. This change does NOT pass through the Context or Themes to the decoder that loads non-Bitmap drawables on a background thread to avoid memory leaks. Fixes #1267.
-
由 Sam Judd 提交于
useAnimationExecutor can lead to deadlock in scenarios where useUnlimitedSourceExecutor is required. As a result, it’s safer to always prefer useUnlimitedSourceExecutor.
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
These are only used as memory cache options, so we can safely change the keys without invalidating disk cache values.
-
由 Sam Judd 提交于
-
- 17 10月, 2017 1 次提交
-
-
由 Sam Judd 提交于
-
- 16 10月, 2017 1 次提交
-
-
由 Sundin 提交于
-
- 14 10月, 2017 1 次提交
-
-
由 Sam Judd 提交于
Fixes #2396.
-
- 13 10月, 2017 4 次提交
-
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
More progress toward #2270.
-
由 Sam Judd 提交于
Fixes #2462.
-
由 Sam Judd 提交于
Previously we were obtaining the requested image size. The requested image size is ignored in roundedCorners because the transformation doesn’t scale. As a result we were weirdly stretching the image with some combinations of image and requested dimensions. Fixes #2472.
-
- 12 10月, 2017 2 次提交
-
-
由 Sam Judd 提交于
Our normal source executor is often used to load data from networks. Glide’s default networking library runs all networking operations on Glide’s source executor. OkHttp runs the initial connection on its own thread pool, but we still read and write the body of each request to our ache on Glide’s source executor. Even libraries like Volley that buffer the entire request into memory will still require a few hundred milliseconds of Glide’s source executor’s time to write the request to cache. Scrolling through a list of images will enqueue a large number of requests. If each request is relatively time consuming, it’s likely that all of Glide’s source executor threads will end up blocked for significant periods of time, even if the longer requests are lower priority. Using a different executor for GIF frames and other animations lets us avoid junk during playback. Unfortunately there is a CPU and memory hit to using an additional executor. I’ve tried to limit that here by using only one or two threads and a cached thread pool so that few threads are created and are only created when an animation is actually run. Fixes #899
-
由 brettchabot 提交于
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=171739060
-
- 11 10月, 2017 5 次提交
-
-
由 Sam Judd 提交于
It warns when we use Target.SIZE_ORIGINAL which is currently a negative value.
-
由 Sam Judd 提交于
It’s perfectly possible to load a valid image or video frame from raw resources as well as drawables resources.
-
由 Sam Judd 提交于
-
由 judds 提交于
I've basically just added a helper method that calls thumbnail() recursively for you. It seems like it eliminates some of the especially confusing nested thumbnail logic. Unfortunately it requires @SuppressWarnings("unchecked") whever it's used because it uses varags with a parameterized type (RequestBuilder). I can't currently use @SafeVarargs because that requires a final method. I can't make the method final without preventing mocking in tests (minor) and breaking the generated API (major). By splitting out a separate base class for RequestBuilder I actually probably can fix this in the future, but that's a pretty substantial change that I don't want to make right now. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=171694145
-
由 judds 提交于
This should also be a slight accuracy improvement since we're now using a somewhat more efficient density multiplier in some cases, especially when downsampling. Fixes #2459. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=171601510
-
- 10 10月, 2017 6 次提交
- 08 10月, 2017 1 次提交
-
-
由 Sam Judd 提交于
Unless you override the jar task completely, any files you specified are added to the original files, not replaced. To make matters worse, gradle does not fail jar tasks when duplicate classes are added by default. We’ve fixed the immediate issue with compiler’s jar file by excluding classes that do not originate from our repackaged/proguarded jar to avoid duplicate class files.We’ve hopefully also prevented future occurrences by forcing all jar tasks in the project to fail by default if duplicate classes are added. Fixes #2452.
-
- 07 10月, 2017 3 次提交
-
-
由 Sam Judd 提交于
As a fallback for drawables that we either can’t obtain an InputStream for or can’t decode as Bitmaps, Glide will now also call Resources#getDrawable with the given resource id. Fixes #350.
-
由 Sam Judd 提交于
-
由 Sam Judd 提交于
We’re going with .error() to match the behavior of the .error Drawable and resource id methods. fallback() is a somewhat better name, but we unfortunately already use it to handle cases where models are null and expected to be null. Fixes #451.
-
- 06 10月, 2017 3 次提交
-
-
由 Sam Judd 提交于
-
由 judds 提交于
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=171204273
-
由 judds 提交于
More progress towards #738. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=170938515
-
- 05 10月, 2017 2 次提交
-
-
由 Sam Judd 提交于
-
由 Robert Papp 提交于
-