Imagcache_actions provides a similar but different approach to the same task.
The imagecache approach sets its preferences in imagecache UI, and actually generates a different image based on source image dimensions, saving only one copy.
This module makes the decision on which preset to use at render time - and presents tohse choices in a visible way through the CCK fields management CCK interface.
Other than that, they both work by defining a set of secondary imagecache presets and trigger them as needed, so a lot of similarity there.
I'll add a cross-reference to imagecache_actions to this one. They don't compete, but offer a choice.
Comments
Comment #1
pcambraThanks dman, I'm adding a reference in the module description.
I think I can close this issue, reopen if you need further discussion.
Comment #2
pcambra