Hi Jamey,Thanks for all the information!But I am just wondering whether I need to continue the entirely xcb-based Gtk-XCB backend. If necessary, I would like you to have a glance at my code, and any comments would be appreciated.
In addition, I will try to make gdk_window_queue just to iterate the
On 11/8/06, Havoc Pennington <[EMAIL PROTECTED]> wrote:
It seems pretty clear that gtk-x11 has to continue to be installed -gdkx.h is in the ABI.XCB is a replacement for Xlib, so if we contribute the gtk-xcb backend, it should replace gtk-x11. Accordingly, there is
gdkxcb.h, instead gdkx.h. Howeve
In order to win the performance, I would like to make use of round-trip delays to get work done in gdk-xcb firstly, which is impossible with Xlib in general. Also the small library and transparent thread safety are the reason of xcb-porting. These features have been illuminated a lot.
JianjunOn 11/
I am always working on the xcb port of gtk. So far most common gtk applications can run well atop the gdk-xcb backend. As the dependency of gtk, Pango and Xft are ported as well.
These XCB backends are built on the 1.0 RC3 (0.9.93) release of xcb-proto and libxcb(http://xcb.freedesktop.org/dist/)
