[cairo] The past, present and future of RGB16_565
keithp at keithp.com
Tue Jun 16 02:18:27 PDT 2009
On Tue, 2009-06-16 at 10:03 +0100, Chris Wilson wrote:
> So... Is this scheme too ugly for words?
I'd say you're almost there -- just create a function that takes your
opaque type instead of attempting to coerce it to the existing type
cairo_image_surface_create_for_wacky_format (wacky_format, width,
or am I just missing something?
also, I'd suggest (and perhaps be wrong) that a static structure could
be used for this wacky format data, and if we need something different
in the future, a new type and creation function could be added.
Future-proofing an API fails at least as often as it succeeds.
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.cairographics.org/archives/cairo/attachments/20090616/babae2c6/attachment.pgp
More information about the cairo