On Sep 24, 2010, at 2:40 AM, Axel Simon wrote: > > Since we just had a discussion on GValue, what were the problems you > encountered? Do we need to expand the GValue API? > > Cheers, > Axel >
I'm not exactly sure. It's been a while so I don't exactly remember the issues I had. I don't really think so, although maybe. I was trying to make it completely invisible and could only get part way there. I think some of the issues were if someone were to try using a custom actor, or something from hypothetical Mx or whatever bindings (as well as maybe a few things in Clutter if I remember correctly), it wasn't good enough to claim it was a general actor. Things in Clutter seemed to more picky about GTypes passed in for actors, flags and pretty much everything. I think ClutterInterval and a few other somewhat minor pieces were particularly problematic. I ended up taking a bunch of Gvalue functions gtk2hs, and ripping them up to use some kind of class for GValues and made some kind of made a mess which I didn't like at all. I'll have to look at it again at some point. I'm pretty sure my solution was pretty terrible and only mostly worked. There were a few other small things about the Gvalue API that I think needed to change internally for bindings, but wouldn't need to be exposed to programs. I think one of the problems was using signed int for unsigned types for colors and a few other didn't make sense, so I just used modified Gtk2hs property functions for those. -Matt ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Gtk2hs-devel mailing list Gtk2hs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk2hs-devel
