[Webkit-unassigned] [Bug 15654] [GTK] GdkPixbuf support for ImageCairo

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 28 11:37:28 PDT 2008


https://bugs.webkit.org/show_bug.cgi?id=15654


alp at nuanti.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alp at nuanti.com




------- Comment #2 from alp at nuanti.com  2008-10-28 11:37 PDT -------
(In reply to comment #1)
> (In reply to comment #0)
> > We need interoperability between GdkPixbuf and ImageCairo to implement certain
> > features. It may even be the case that we want Image in the GTK+ port to be
> > implemented using GdkPixbuf rather than a Cairo surface.
> 
> What is the benefit of GdkPixbuf? Why should we use GdkPixbuf instead of a
> cairo_surface? Expecially if you read
> http://live.gnome.org/GtkCairoIntegration. It is intented to replace GdkPixbuf
> in Gtk by cairo (at least in parts of it).
> The biggest problem seems to be point 2 in the problems list.
> We'll have to do something like in 'Workarounds & Solutions' on the same link.
> 

I don't think there's any need to switch to GdkPixbuf or stop using
cairo_surface. This bug is just here to add some integration between the image
classes in GTK+ and the WebCore Cairo backend so we can easily take GdkPixbufs
handed to us by GTK+ and render them with Cairo, and vice-versa, generate
GdkPixbufs based on Cairo surfaces if we need to expose them in the WebKit GTK+
API for example. This kind of integration could be helpful for Cursor.h and
custom image cursors and I think the file chooser needed something like this
too. Hope things are a little clearer now.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list