[cairo] Cleaning up the PDF API
keithp at keithp.com
Mon May 16 20:13:54 PDT 2005
On Mon, 2005-05-16 at 22:55 -0400, Kristian Høgsberg wrote:
> cairo_pdf_surface_create_for_stream() on the other hand, will use the
> closure for a longer time, specifically, the created pdf surface will
> continue to reference it and use it *after* the function call returns.
There are many operations which the application may want to perform
while cairo is busy with the file. I see the application needing to
output lots of information after each page, and more information at the
end of the file. I think we can make 'cairo_show_page()' and
'cairo_finish()' flush the file without performance problems, but that
leaves the application needing to perform surface-specific operations at
each of these points.
The raw language binding should just expose the raw functionality and
expect that higher level functions manage the surface-specific
manipulations that aren't done within cairo. There should be no
distinction needed between the C binding and any other language in this
regard; C applications will have to do precisely the same work.
-------------- 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.freedesktop.org/archives/cairo/attachments/20050516/16a34879/attachment.pgp
More information about the cairo