Many web site designs demands consistency of images based on their use within components. For example, a panoramic spotlight may demand the image be 960 x 400, and bio picture must be 100 x 100 and greyscale.
Some times we have some images on which we can not use image renditions generated by out of the box because of their cropped size. In that case we have to use our different types of dimensions for different types of component.
The ACS AEM Commons Named Transform Image Servlet allows specific image transforms to be defined centrally via OSGI configurations. These image transforms can be easily invoked via parameterized HTTP GET requests to image resources in AEM.
So let see about ACS AEM Commons provided Image Transformers and how to use these transformers and what will the effect of these on images.
Supported “image-y” resources
Almost any “image-like” resource can be requested using the named transform URI parameterization, and the underlying image will be derived and rendered using the transformation parameters.
Pages (cq:Page):
HTTP GET /content/acme/article.transform/feature/image.png
Image component resources:
HTTP GET /content/acme/article/_jcr_content/image.transform/feature/image.png
DAM Assets (dam:Asset):
HTTP GET /content/dam/images/dog.jpg.transform/feature/image.jpg
DAM Asset Renditions”
HTTP GET /content/dam/images/dog.jpg/jcr:content/renditions/thumbnail.jpg.transform/feature/image.jpg
“Raw” Binary Images (nt:file or nt:resource):
HTTP GET /etc/designs/acme/images/cat.png.transform/feature/image.jpg
1. Resize:
Resizes the image to the specified width and/or height.
Name
Resizes the image to the specified width and/or height.
Name
- Resize
- width=[width in px]
- height=[height in px]Example
- resize:width=200
- resize:height=300
- resize:width=400&height=400
How to use:
Define any number of sling:OsgiConfig’s, each representing a differently named transform
/apps/mysite/config/com.adobe.acs.commons.images.impl.NamedImageTransformerImpl-myTransformName.xml
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="sling:OsgiConfig" name="my-transform" transforms="[resize:width=400&height=400]"/>
Get the URI to a supported resource (see above) to transform
add the .transform extension (append this even if the resource is named with an extension; like a DAM asset)
Add an initial suffix segment that matches your transform name (Ex. /my-transform)
Add a final suffix segment of /image.<image-format-extension> OR /img.<image-format-extension>
Resulting in
<img src=”/content/mysite/article/_jcr_content/image.transform/my-transform/image.png”/>
or
<img src=”/content/dam/images/dog.jpg.transform/my-transform/img.png”/>
The below DAM Asset image has been resizes as defined by the custom defined my-transform transform rule set.
bc http://localhost:4502/content/dam/we-retail/en/activities/hiking/hiking_5.jpg.transform/my-transform/image.jpg
Resized Image
Define any number of sling:OsgiConfig’s, each representing a differently named transform
/apps/mysite/config/com.adobe.acs.commons.images.impl.NamedImageTransformerImpl-myTransformName.xml
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="sling:OsgiConfig" name="my-transform" transforms="[resize:width=400&height=400]"/>
Get the URI to a supported resource (see above) to transform
add the .transform extension (append this even if the resource is named with an extension; like a DAM asset)
Add an initial suffix segment that matches your transform name (Ex. /my-transform)
Add a final suffix segment of /image.<image-format-extension> OR /img.<image-format-extension>
Resulting in
<img src=”/content/mysite/article/_jcr_content/image.transform/my-transform/image.png”/>
or
<img src=”/content/dam/images/dog.jpg.transform/my-transform/img.png”/>
The below DAM Asset image has been resizes as defined by the custom defined my-transform transform rule set.
bc http://localhost:4502/content/dam/we-retail/en/activities/hiking/hiking_5.jpg.transform/my-transform/image.jpg
Resized Image
Original Image
2. Bounded Resize (v1.8.0+)
Resizes the image but will not resize past maximum dimension constraints. Accepts two Integer params: height and width. Either width or height will scale to the parameterized limit. The other dimension scale automatically to maintain the original aspect ratio. If the original image is smaller than the configured dimensions the image won’t be resized. Upscale param can be set to true to allow upscaling smaller images.
Name
- bounded-resize
- width=[width in px]
- height=[height in px]
- upscale=true/false
- bounded-resize:width=200
- bounded-resize:height=300
- bounded-resize:width=400&height=400&upscale=true
The below DAM Asset image has been resizing as defined by the custom-defined my-transform-bounded transform rule set.
bc. http://localhost:4502/content/dam/we-retail/en/activities/hiking/hiking_5.jpg.transform/my-transform-bounded/image.jpg
Bounded-resize
3. Crop
Crops the image to the specified bounds.
Name
- crop
- bounds=[x,y,width,height]
- smart=[boolean] Defaults to true. Smart bounding will attempt to shift the specified crop-zone to fit within the image dimensions if the crop-zone falls outside the images dimensions.
- crop:bounds=0,10,300,350
- crop:bounds=0,10,300,350&smart=false
- crop:bounds=25%,0,50%,100%
- Relative cropping available since v2.8.0/3.4.0
The below DAM Asset image has been cropped as defined by the custom defined my-transform-crop transform rule set.
http://localhost:4502/content/dam/we-retail/en/activities/hiking/hiking_5.jpg.transform/my-transform-crop/image.jpg
4. Greyscale
Converts the image to greyscale.
Name
.greyscale
Params
.None
Example
.greyscale
If we want to use all configs in single transform rule than we can use it. config will be like this:
The below DAM Asset image has been resizes, cropped and greyscaled as defined by the custom defined my-transform-all transform rule set.
Note: Order matters when defining your image transformation rules. For example, a resize then crop can yield significantly different results than a crop then resize.
Converts the image to greyscale.
Name
.greyscale
Params
.None
Example
.greyscale
If we want to use all configs in single transform rule than we can use it. config will be like this:
The below DAM Asset image has been resizes, cropped and greyscaled as defined by the custom defined my-transform-all transform rule set.
Note: Order matters when defining your image transformation rules. For example, a resize then crop can yield significantly different results than a crop then resize.
Source: https://lhotsetechnologies.com/blog/named-transform-image-servlet-image-renditions-on-the-fly/
No comments:
Post a Comment
If you have any doubts or questions, please let us know.