The current code is sending images as full size images with a calculated width and height. It should be able to reduce bandwidth by resizing images.

Comments

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

I think that I opt for using imagecache way of retrieving images.

By using a node id and a path containing the derived image seems all there is to know.

The current implementation uses the internals of an image node.

So I hope my users tell what to do :-)

Chuck1’s picture

Chuck1 commented

I like this module the image compositions look great and it is very easy to create a composition, BUT the only reason that I can't use this module is that it takes too long to load the webpage with the composition :( .
I will wait and I hope you find a good solution that you must not transfer the full size image.....

It is not possible to render the image with the new size with the GD library before you transfer it?

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented
Version: 5.x-1.0-beta1 » 5.x-1.0-beta6

Using GD is possible but it is not the way i would like to go. It would mean programming image handling into the module. And I want to other things for this module.

So using image-cache for getting to nodes containing images changes the dependency (image.module).

What I can do then is use an admin setting for what the preview url is and what the full image view is. At the moment I'm experimenting with image-cache but coding this will take 8 hours or more.

dman’s picture

dman commented
Issue summary: View changes
Status: Active » Closed (fixed)

Closing old (D5) issues