[Webkit-unassigned] [Bug 26379] Reconsider image decoding architecture/APIs

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=26379





------- Comment #48 from eric at webkit.org  2009-06-15 13:43 PDT -------
So the debate boils down to if it's OK to add a image abstraction around the
Vector<unsigned>.  Correct?  RGBA32Buffer used to be a thin layer you could
grab through.  Now Peter's changed it to be an image abstraction, like
ImageBuffer.

I don't see why this breaks ports?  Can't we have a default ImageBuffer which
uses Vector<unsigned> under the covers?  Although it seems that would only be
needed by platforms which don't provide an Image type to decode into, or?

For what it's worth, CoreGraphics (what I tend to use as my reference for
graphics APIs), decodes into an opaque image type:
http://developer.apple.com/documentation/graphicsimaging/reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreate

I feel much more informed after all this, and am looking forward to peter's
next round of patches to share more platform/graphics code between all ports.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.