Re: [PATCH] image: Add public API for the creation of a surface for a pixman_image_t

[email protected] (Søren Sandmann)
Newsgroups gmane.comp.lib.cairo
Message-ID <[email protected]>
Chris Wilson <[email protected]> writes:

> Greater interoperablity with pixman is often requested by users dealing
> with quirky hardware that prefers niche formats. As the goal is to keep
> the number of core, well supported cairo_format_t to a minimum, we need
> an alternative mechanism to support the extensive range of formats
> supported by pixman. In the future we will also have to look to
> supporting pixman colorspaces, but for now we only handled RGBA linear
> compositing and so restrict ourselves to that subset of pixman images.

Just a few comments:

- At some point, pixman will need to break API compatibility. Up until
  now this has as far as I know been possible to do without affecting
  cairo's API. I'm not sure what the implications for this new API would
  be.

- Copying the image passed in means that if and when new pixman features
  such as dithering or damage tracking become available for destination
  images, cairo won't be able to take advantage of them without being
  updated. (And updating cairo to do so, would then be a potential ABI
  break).

If the main reason for this API is to help people with weird hardware,
maybe cairo_format_t could simply be extended to cover all known pixman
formats?

Another possibility might be to add a new "pixman" surface type that was
explicitly documented to be less ABI stable than cairo itself.


Søren
--
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.