On 06/21/02 Rachel Hestilow wrote: > So, it looks like some of the GdkPixbuf methods (::render*) are in Gdk > proper and not gdk-pixbuf. This makes sense from the C programmer's > perspective, because they are the methods that render to gdk drawables, > and apps like sawfish needed their own xlib rendering methods. But given > that we obviously can't have a class scattered across several > assemblies, I see a couple of options here: > > a) Move gdk-pixbuf back into gdk. This would solve the problem at the > cost of requiring Gdk for any GdkPixbuf usage. Did anyone express > interest in using GdkPixbuf on its own? > System.Windows.Forms/System.Drawing guys, I'm looking at you here. > > b) Have the Gdk rendering methods be in a class of their own: either as > static methods in some sort of GdkPixbufRenderer, or a subclass of > Pixbuf for Gdk. I personally like this approach, but it might confuse > people migrating from C, who are at this point our core audience.
I think the pixbuf code should be usable without a display and the Gdk assembly can easily depend on it and import the render methods under Gdk.Drawable. lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
