On 11/24/05 3:47 AM, Peter Weilbacher wrote:
No, from what I have heard it's not in CVS because there were some
changes necessary to the cairo codebase to get it to compile on OS/2
with different compilers that the cairo team didn't like. And I guess
Mozilla syncs with cairo CVS so it's not there, either. (Hmm, can we
check in the working OS/2 files to Mozilla CVS at all under these
circumstances?)
The only changes we have in mozilla's copy of cairo is stuff to
integrate with our build system and vital fixes that have been merged
upstream. The place for a new backend is in cairo's cvs.
If you want you can take a look at the OS/2 cairo files in
ftp://ftp.netlabs.org/pub/cairo/cairo-1.0.2-2005.11.01/cairo-1.0.2-os2-s
rc.zip
Both functions you quote are implemented and get called when I display
SVG content in my SeaMonkey build. But should the actual compositing be
implemented in the backend (I notice a function
_cairo_win32_surface_composite) or how else is cairo told that it should
do the compositing?
While that does have a _cairo_os2_surface_acquire_dest_image, it's just
a stub and isn't reading back from the target surface as it should.
If your platform's native graphics API supports compositing, then the
backend should implement a composite function and put it in the backend
structure. Otherwise, a null entry in the structure for composite is
what tells cairo that it needs to composite internally through the
aquire_source_image, libpixman composite, release_dest_image fallback.
-tor
_______________________________________________
mozilla-layout mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-layout
