On Tue, 2008-12-09 at 12:19 +0000, Neil Roberts wrote: > On Tue, 2008-12-09 at 11:56 +0000, Emmanuele Bassi wrote: > > > I'll have to add specific, pyclutter-only boxed types for the various > > CoglHandle types. that should give me enough leverage to use pygobject's > > own API. otherwise I'll just create some PyObject wrappers and see what > > happens. > > BTW, there is already a boxed type in Clutter for the CoglTexture type > (CLUTTER_TYPE_TEXTURE_HANDLE) which the Ruby bindings make use of. I'm > not sure if pygobject works the same but in Ruby if I use that type then > I get the accessors for the 'cogl-texture' property of ClutterTexture > for free.
I still need to implement most of the machinery (ref+unref) anyway for the other CoglHandle types - and I prefer using COGL_TYPE_HANDLE (or PYCOGL_TYPE_HANDLE in this case) than a fictitious CLUTTER_TYPE_TEXTURE_HANDLE. in any case, I've committed the beginnings of the COGL texture API; there's still some missing stuff - mostly the texture constructors - but it should reasonably work. > The other types don't have boxed types though because Clutter doesn't > use them directly. yup. I was wondering if Clutter should define those types inside clutter-types.h so that people using cogl/cogl.h will not have a GType dependency, but people using Clutter will have the COGL GTypes as well. not that it would make any difference: there is no separate COGL shared object anyway - it's more a psychological thing. :-) ciao, Emmanuele. -- Emmanuele Bassi, Intel Open Source Technology Center -- To unsubscribe send a mail to [EMAIL PROTECTED]
