On 6/19/06, Steve Bennett stevage@gmail.com wrote:
In that case, it sounds like the relevant parameter should also be stored on the image, rather than on the call to the image. It seems unlikely to me that one would want to downscale using one method on one page, and using a different method on another page. In extreme cases (like, wanting to demonstrate pixelation), people can use the current fallback method.
The amount of sharpening is size dependant.. I suppose you could attach a sharpening list to the image, which provides a list of thumb reduction ratios (rather than thumb sizes, so that it does the same WRT cropping) well with and the correct sharpening for each. This is a good idea because it would prevent the bloat of maintaining multiple versions. I like this... okay, so my point 2 is dead. Thanks for pointing this out. :) This also would allow the users to fully specify the sharpening parameters, which would be much better than the few fixed settings I'd envisioned.
Cropping still applies, however.