Issue Feature Closed

#20497New options noRescale and resoultionFactor for getImgResource()

Stefan Geith 05/24/09, 15:41 updated 04/21/11, 15:18

Description

Sometimes a higher resolution as the display-resolution of an Image is needed.
E.g. if you want to render PDFs from your HTML-Output, you coulld need higher resolutions for images, if you want to print them.
This is not possible in the moment.

New options for the imgResource that would be helpful:
noRescale=1 -> creates image, as ususal, but doenst resize original file
resolutionFactor=n -> creates an image, that has n times higher resoultion than displayed

Imagine an uploaded Image of size 1500×1000 pixel.
If you create an IMAGE-Tag by TS with width=320m, then the Image will be rendered to 480×320 pixels and the width/height-params of the created -tag will be also 480×320.
If you want to zoom-in on the website or you want to create a PDF from the page, then the resolution is to low.

With use of noResize=1an IMAGE-Tag will be rendered with width/height-params 480×320, but the src-param will be the original image (having 1500×100 pixels).

With use of resolutionFactor=2 an IMAGE-Tag will be rendered with the Image scaled to 960×640 pixels and the width/height-params of the created -tag set to 480×320.

(issue imported from #M11177)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.