themidgard at gmail.com
Wed Sep 21 01:16:15 PDT 2005
The coding style seems similar to the one I was thinking of using. With the
exception of the capitalization in first letter of the methods (but that's
only small details).
By the way, another thing that I tough of was the possibility to have
automatic status checks (after any operation that might fail) and react to
that failure by (optionaly) throwing an exception.
I think this is a good idea, but as I don't have too much experience using
cairo i'm still unsure. It's certainly a better way of checking for error
conditions, but cairo seems to be able to keep going even if certain errors
occurs (say, cairo_create() is called when cairo_status()==
This could eventualy be made in a way it was possible to disable the checks
with a #define or with a simple bool in the wrapper class.
What do you think of this ?
If you need any help, just ask.
On 9/21/05, Evan Martin <martine at danga.com> wrote:
> I've been doing exactly this. I should put this code up somewhere.
> It's currently just a 283-line header file that does the obvious
> wrapping. Here's a snippet of some code that uses it. (I apologize
> for the coding style, but it's trying to match another project.)
> // ... a function that takes a cairo::Context &cr, and then:
> cairo::TextExtents te;
> // center the title.
> cr.GetTextExtents(*title_, &te);
> cr.MoveTo(Point((cairo_width_ - te.width) / 2.0, -20));
> On 9/19/05, Rui Pires <themidgard at gmail.com> wrote:
> > Hi,
> > I'm quite interested in cairoxx, as i'm a C++ fan.
> > It's sad that there are already bindings available for a bunch of other
> > languages and not for C++. It's true that in C++ you can use the C API
> > directly, but it's not the same thing. For me it just doesn't feel right
> > using it that way.
> > Anyway, i've checked the mailing list archives didn't find out if this
> > being actively developed or if it is stopped. Also, at the time i write
> > this, the last CVS checkin seems to have been 16 months ago.
> > If anyone's interested i'm willing to try writing a really thin set of
> > wrapper classes (mostly inline functions, to keep overhead at a
> > Rui Pires.
> > _______________________________________________
> > cairo mailing list
> > cairo at cairographics.org
> > http://cairographics.org/cgi-bin/mailman/listinfo/cairo
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cairo