Given Safari will soon be supporting WebP, I suspect a shift away from the use of animated GIF images towards the use of animated WebP images, which are significantly more efficient, is coming.
Operations like extract and rotate on individual pages/frames might be rather complex, but a possible new resizePages operation to resize all pages/frames in an image to a given width _or_ height (these would have to be mutually exclusive, plus an optional kernel), would be relatively straightforward.
馃憞 PROPOSED API - NOT YET AVAILABLE
.resizePages({ width, kernel })
.resizePages({ height, kernel })
馃憜 PROPOSED API - NOT YET AVAILABLE
Why not load all pages by default, though? Is BC the only concern? I guess it can break "convert first frame of gif/tiff to jpeg" scenario.
Why not simply apply all operations on all frames? I would need compositing functionality for animated gifs. Duplicating every method to apply for all frames would be a rather complex task.
It would be easier applying all operations on all frames and the ability to extract single frames or sequences and construct new animated images based on frames/sequences. So compositing images on a subset on frames can be implemented based on these primitives.
Any news on this?
+1, waiting for the resizePages API
Most helpful comment
+1, waiting for the resizePages API