[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cairo
Subject:    [Cairo] Exposing cairo_path_t publicly?
From:       Carl Worth <cworth () east ! isi ! edu>
Date:       2003-12-03 15:10:04
Message-ID: 16333.64716.311259.766129 () scream ! east ! isi ! edu
[Download RAW message or body]

On Nov 29, Duncan Mak wrote:
 > Do you think it is adequate to expose the private cairo_path_t API and
 > use it to implement the GDI+ GraphicsPath? Or do you think a fresh
 > implementation (not related to cairo_path_t) is needed?

I think that you'll want your own implementation.

I did expose cairo_path_t at one point a few months ago. That lasted
less than a day. Keith's cool reception of this new feature convinced
me to remove it:

http://cairographics.org/pipermail/cairo/2003-September/000540.html

And even then, I didn't feel comfortable exposing any way to get at
the path data, so it wouldn't have helped you anyway.

Basically, cairo should be seen as just an immediate mode drawing
library. Data storage for paths, objects, and their attributes should
live in a layer above cairo.

-Carl


[prev in list] [next in list] [prev in thread] [next in thread]