Android glide corner radius

Transformations in Glide take a resource, mutate it, and return the mutated resource. Typically transformations are used to crop, or apply filters to Bitmaps, but they can also be used to transform animated GIFs, or even custom resource types.

Built in types

Glide includes a number of built in transformations, including:

Applying Transformations

Transformations are applied using the RequestOptions class:

Default Transformations

Or with RequestOptions :

For more information on using RequestOptions, see the Options wiki page.

Multiple Transformations.

By default, each subsequent call to transform() or any specific transform method ( fitCenter() , centerCrop() , bitmapTransform() etc) will replace the previous transformation.

To instead apply multiple transformations to a single load, use the MultiTransformation class or the shortcut .transforms() method.

Or with the shortcut method:

The order in which you pass transformations to MultiTransformation ’s constructor determines the order in which the transformations are applied.

Custom transformations.

Although Glide provides a variety of built in Transformation implementations, you may also implement your own custom Transformation s if you need additional functionality.

BitmapTransformation

If you only need to transform Bitmap s, it’s best to start by subclassing BitmapTransformation . BitmapTransformation takes care of a few of the basic things for you, including extracting recycling the original Bitmap if your Transformation returns a new modified Bitmap.

A simple implementation might look something like this:

Although your Transformation will almost certainly do something more sophisticated than our example, it should contain the same basic elements and method overrides.

Required methods

In particular, note that there are three methods that you must implement for any Transformation subclass, including BitmapTransformation in order for disk and memory caching to work correctly:

If your Transformation takes no arguments, it’s often easy to just use a static final String containing the fully qualified package name as an id that can form the basis of hashCode() and can be used to update the MessageDigest passed to updateDiskCacheKey() . If your Transformation does take arguments that affect the way the Bitmap is transformed, they must be included in these three methods as well.

For example, Glide’s RoundedCorners Transformation accepts an int that determines the radius of the rounded corners. Its implementations of equals() , hashCode() and updateDiskCacheKey looks like this:

The original String id remains as well, but the roundingRadius is included in all three methods as well. The updateDiskCacheKey method here also demonstrates how you can use ByteBuffer to including primitive arguments in your updateDiskCacheKey implementation.

Don’t forget equals()/hashCode()!

It’s worth re-iterating one more time that it’s essential that you implement equals() and hashCode() for memory caching to work correctly. Unfortunately BitmapTransformation and Transformation implementations will compile if those methods are not overridden, but that doesn’t mean they work correctly. We’re exploring options for making using the default equals() and hashCode methods a compile time error in future versions of Glide.

Special Behavior in Glide

Re-using Transformations

Transformations are meant to be stateless. As a result, it should always be safe to re-use a Transformation instance for multiple loads. It’s usually good practice to create a Transformation once and then pass it in to multiple loads.

Automatic Transformations for ImageViews

When you start a load into an ImageView in Glide, Glide may automatically apply either FitCenter or CenterCrop, depending on the ScaleType of the view. If the scale type is CENTER_CROP , Glide will automatically apply the CenterCrop transformation. If the scale type is FIT_CENTER or CENTER_INSIDE , Glide will automatically apply the FitCenter transformation.

You can always override the default transformation by applying a RequestOptions with a Transformation set. In addition, you can ensure no Transformation is automatically applied using dontTransform() .

Custom resources

Because Glide 4.0 allows you to specify a super type of the resource you’re going to decode, you may not know exactly what type of transformation to apply. For example, when you use asDrawable() (or just with() since asDrawable() is the default) to ask for a Drawable resource, you may get either the BitmapDrawable subclass, or the GifDrawable subclass.

To ensure any Transformation you add to your RequestOptions is applied, Glide adds your Transformation to a map keyed on the resource class you provide to transform() . When a resource is successfully decoded , Glide uses the map to retrieve a corresponding Transformation .

Glide can apply Bitmap Transformations to BitmapDrawable , GifDrawable , and Bitmap resources, so typically you only need to write and apply Bitmap Transformations . However, if you add additional resource types you may need to consider sub-classing RequestOptions and always applying a Transformation for your custom resource type in addition to the built in Bitmap Transformations .

Источник

Displaying Images with the Glide Library

Glide is an Image Loader Library for Android developed by bumptech and is a library that is recommended by Google. It has been used in many Google open source projects including Google I/O 2014 official application. It provides animated GIF support and handles image loading/caching.

Add to your app/build.gradle file:

Make sure to create a MyAppGlideModule that simply extends from AppGlideModule and has the @GlideModule annotation. For now, the class is empty but later we will show how it can be used to set the default image resolution. If you upgrading from Glide v3, make sure you follow this step too:

Make sure to sync your project to Gradle before continuing, since Glide needs to generate the necessary code to invoke GlideApp.with() in Android Studio.

If you are migrating from Glide v3, make sure to review this guide. Instead of Glide.with() , you will need to use GlideApp.with() :

Resizing images with:

Placeholder and error images:

Cropping images with:

Modify your MyAppGlideModule to override applyOptions:

Ideally, an image’s dimensions would match exactly those of the ImageView in which it is being displayed, but as this is often not the case, care must be taken to resize and/or scale the image appropriately. Android’s native support for this isn’t robust, especially when displaying very large images (such as bitmaps returned from the camera) in smaller image views, which can often lead to errors (see Troubleshooting).

Glide automatically limits the size of the image it holds in memory to the ImageView dimensions. Picasso has the same ability, but requires a call to fit() . With Glide, if you don’t want the image to be automatically fitted to the ImageView , you can call override(horizontalSize, verticalSize) . This will resize the image before displaying it in the ImageView but without respect to the image’s aspect ratio:

Resizing images in this way without respect to the original aspect ratio will often make the image appear skewed or distorted. In most cases, this should be avoided, and Glide offers two standard scaling transformation options to prevent this: centerCrop and fitCenter .

If you only want to resize one dimension, use Target.SIZE_ORIGINAL as a placeholder for the other dimension:

Calling centerCrop() scales the image so that it fills the requested bounds of the ImageView and then crops the extra. The ImageView will be filled completely, but the entire image might not be displayed.

Calling fitCenter() scales the image so that both dimensions are equal to or less than the requested bounds of the ImageView . The image will be displayed completely, but might not fill the entire ImageView .

If an image or set of images aren’t loading, make sure to check the Android monitor log in Android Studio. There’s a good chance you might see an java.lang.OutOfMemoryError «Failed to allocate a [. ] byte allocation with [. ] free bytes» or a Out of memory on a 51121168-byte allocation. . This is quite common and means that you are loading one or more large images that have not been properly resized.

First, you have to find which image(s) being loaded are likely causing this error. For any given Glide . call, we can fix this by one or more of the following approaches:

Add an explicit width or height to the ImageView by setting layout_width=500dp in the layout file.
Call .override(width, height) during the Glide load and explicitly set a width or height for the image such as: GlideApp.with(. ).load(imageUri).override(500, 500).into(. ) .
Try removing android:adjustViewBounds=»true» from your ImageView if present and if you not calling .override()
Open up your static placeholder or error images and make sure their dimensions are relatively small ( AndroidManifest.xml and then add android:largeHeap to your manifest:

Note that this is not generally a good idea, but can be used temporarily to trigger fewer out of memory errors.

If you experience errors loading images, you can create a RequestListener and pass it in via Glide.listener() to intercept errors:

Transformations are supported by an additional third-party library, glide-transformations. First, add the dependencies:

Источник

glide rounded corner transform issue

i use the following code to load an image with rounded corners into imageview using glide:

images get pixelized for some reason. Can somebody tell me where is the problem?

13 Answers 13

I had the same issue, the problem in my case was the image what i’ve tried to load had less size in pixels (320×480), then the ImageView size in pixels. My solution was the following:

My ImageView in the xml file:

P.S. I use 4.2.0 version of Glide

in Glide V4

For Glide v4.9 transformation (java):

For Glide v4.9 the following transformation works fine:

This is what worked for me (generated API, Glide 4.9, Kotlin):

As you can see in my answer here, it can also be achieved using Glide’s Generated API. It takes some initial work but then gives you all the power of Glide with the flexibility to do anything because you write the actual code so I think it’s a good solution for the long run. Plus, the usage is very simple and neat.

First, setup Glide version 4+:

Then create Glide’s app module class to trigger the annotation processing:

Then create the Glide extension which actually does the work. You can customize it to do whatever you want:

After adding these files, build your project.

Источник

How to round an image with Glide library?

So, anybody know how to display an image with rounded corners with Glide? I am loading an image with Glide, but I don’t know how to pass rounded params to this library.

I need display image like following example:

26 Answers 26

Glide V4:

Glide V3:

You can use RoundedBitmapDrawable for circular images with Glide. No custom ImageView is required.

Check this post, glide vs picasso.
Edit: the linked post doesn’t call out an important difference in the libraries. Glide does the recycling automatically. See TWiStErRob’s comment for more.

The easiest way (requires Glide 4.x.x)

all_circle_white_bg.xml

I use this transformation library. ->https://github.com/wasabeef/glide-transformations
Circle stroke width is ImageView’s padding

its very simple i have seen Glide library its very good library and essay base on volley Google’s library

usethis library for rounded image view

//For a simple view:

The other solutions did not work for me. I found they all have significant drawbacks:

Solutions using glide transformations do not work with placeholders
Solutions using rounded image views do not work with animations (i.e. crossfade)
Solutions using a generic method of a parent that clips its children (i.e. the accepted answer here) do not work well with glide

It is really interesting that after fumbling around with this I found the Fresco library page about rounded corners and circles in which they list basically the same limitations and conclude with the statement:

there is no really good solution for rounding corners on Android and one has to choose between the aforementioned trade-offs

Unbelievable that at this time we still dont have a real solution. I have an alternate solution based on the link I put above. The drawback with this approach is that it assumes your background is a solid color (the corners aren’t really transparent). You would use it like this:

Источник

Glide Library – Image Loading Library For Android

Table of Contents

What is Glide Android?

Glide Android is an open source media management and image loading framework for Android.
It supports fetching, decoding, and displaying video stills, images, and animated GIFs.
Glide includes a flexible API that allows developers to plug into almost any network stack.
By default, Glide uses a custom HttpUrlConnection based stack but also includes utility libraries to plug into Google’s Volley project or Square’s OkHttp library instead.

Why is Glide Android?

Glide’s primary focus is on making scrolling any kind of a list of images as smooth and fast as possible, but Glide is also effective for almost any case where you need to fetch, resize, and display a remote image.

Setup Glide in your Android Studio project

Add to your app/build.gradle file:

Basic Usage of Glide

Glide Basic Example

Advanced Usage of Glide

With PlaceHolder

With Placeholder and error placeholder

Resizing image

Cropping image

Center Crop

Circle crop

Fit Center

Resizing with the center crop

Resize and fit center

Adding listener for Glide image loading

Change Glide default Configuration

Extending AppGlideModule you can override the default config on the glide.

In this case, I just change the default image format of the glide.

Glide default Bitmap Format is set to RGB_565 since it
consumed just 50% memory footprint compared to ARGB_8888.

Glide Transformations

Transformations are supported by an additional third-party library, glide-transformations. First, add the dependencies:

Rounded Corners

Circle Crop

Blur Effect

Multiple transforms

Also, you can use multiple transformations at once.

Adjusting Image Size Dynamically

To readjust the ImageView size after the image has been retrieved, first define a SimpleTarget object to intercept the Bitmap once it is loaded:

Next, pass the SimpleTarget to Glide via into().

Источник