I've started in on some C++ bindings for goocanvas. I'm having a bit of a
head scratcher of some of the type definitions used.
Specifically things like
GooCairoAntialias or GooCairoFillRule
These types are all listed in goocanvasprivate.h, but also appear as
properties in GooCanvasItemSimple
Are these really supposed to be private types?
They seem to be part of the public api, although, I really can't tell for
On Wed, 2006-09-27 at 05:10 -0500, Paul Davis wrote:
> I've started in on some C++ bindings for goocanvas. I'm having a bit
> of a head scratcher of some of the type definitions used.
> Specifically things like
> GooCairoAntialias or GooCairoFillRule
> These types are all listed in goocanvasprivate.h, but also appear as
> properties in GooCanvasItemSimple
> Are these really supposed to be private types?
> They seem to be part of the public api, although, I really can't tell
> for sure.
They are just wrappers for cairo enums, which are already public.
The type functions like goo_cairo_fill_rule_get_type() aren't really
useful in C so I kept them private. But if bindings need them we can
make them public (we've already made some of the other type stuff public
for the python bindings).
Note that there may be major changes to GooCanvas in the near future, so
you might want to wait until these are done before writing the bindings.
(I'll post a message about the possible changes in a minute.)
On Thu, 2006-09-28 at 05:13 -0500, Paul Davis wrote:
> I'm mostly worried about GooCanvasBounds. Thats pretty much the
> biggest one. So far I've just assumed that anything using it was
> private so not wrapping it was ok.
> Although, I imagine in the future, if someone wants to extend the
> shapes in any great way, having that available would be a necessity.
> (Just guessing, haven't looked at the code)
Yes, GooCanvasBounds is definitely public.