Adaptive Resize - and IMv7 CLI development.
Posted: 2011-09-27T18:44:15-07:00
Adaptive-resize is actually just a resize using a hardcorded Mesh Interpolation (in IMv6), which is not available as a filter. and is ment for use with very very small image size changes.
However the IMv7 (alpha) version now have it using the current -interpolate setting, without even a fallback to Mesh if interpolate is not defined. As such it now defaults to bilinear interpolating instead of mesh when interpolate is not set by the user.
The operator was originally created in a fast response to a user request, but without discussion. It is was it would probably have been more like what is now in IMv7. As such in my view it is a miss-named operator. As I am currently working on IMv7 CLI interface, I need to decide whether to fix this (back to using Mesh), OR rename the operator to something like -interpolated-resize, which correctly described what the operator is now doing.
My preference is for the later, and rename the operator more appropriately (including the library function), perhaps with the change and a depreciation warning for the old operator migrated back to IMv6 (but without library API change)
What do other developers think?
However the IMv7 (alpha) version now have it using the current -interpolate setting, without even a fallback to Mesh if interpolate is not defined. As such it now defaults to bilinear interpolating instead of mesh when interpolate is not set by the user.
The operator was originally created in a fast response to a user request, but without discussion. It is was it would probably have been more like what is now in IMv7. As such in my view it is a miss-named operator. As I am currently working on IMv7 CLI interface, I need to decide whether to fix this (back to using Mesh), OR rename the operator to something like -interpolated-resize, which correctly described what the operator is now doing.
My preference is for the later, and rename the operator more appropriately (including the library function), perhaps with the change and a depreciation warning for the old operator migrated back to IMv6 (but without library API change)
What do other developers think?