Quoting Daniel Rogers <daniel@xxxxxxxxxxxxxxxxx>: > Ok . .. Great! Have you done JAI programming. I am taking some > inspiration from that particular library. I've read about JAI and considered using it on a project but ended up deciding against it because of the non-open nature of the license and because it was a bit overkill for the small tasks we needed it for. So I have a little understanding of JAI's way of doing things. ... I've spent some time since I first started looking at GEGL trying to understand the GObject system, since I've never used it before, and have come to the sad conclusion that it is N.A.S.T.Y. It's neat how they implemented such a featureful and flexible object system in straight C, but after using C++ and particularly Java, ease of creating and using classes becomes a basic expectation. GObject makes it painful and hairy. Oh, and don't even think of renaming a class. You'll be fixing calls to macros all day. :-P But maybe once you gain experience with GObject it becomes easier and more natural? Anyway, that's kind of a roadblock keeping me from jumping into the code right away, since objects are used so extensively in GEGL. Nothing against GEGL itself, I suppose all GTK2 apps (and of course the GIMP) have to use GObject? Myself never having written a GTK application before. I'd still love to help but I'm kind of stuck right now. Maybe later I will be more useful. I'll be lurking and poking around the code once in a while, but too much GObject makes my head hurt. :-) Colin
