On Wed, Feb 11, 2015 at 11:51 AM, <
moshen...@gmail.com> wrote:
> While most of the changes are minor, extracting and exposing frame disposal
> to know how to handle frame data in the context of an animation, I did add
> an "Explode" method to GIF.
I'm OK with adding the fields to the GIF struct, since that's part of
the file format, but I'm hesitant to add a GIF.Explode method to the
standard library. Once GIF gains the Disposal and other fields, it
seems like Explode can exist in your own code for now, that *uses*
package gif, instead of being *in* package gif. Even if it eventually
belongs in the stdlib, I'd like some bigger-picture thinking done
first about Go APIs for video and animation in general, not just for
GIFs, and I'd rather not commit to any particular
we-won't-break-back-compat API in the stdlib until we've done that
thinking (and some proof of concept implementations for some common
video formats).
BTW your fillIn function could be a single draw.Draw call. See
"Filling a Rectangle" in
http://blog.golang.org/go-imagedraw-package