KWIG Qt->Gtk porting layer and merging main loops.

Avery Pennarun apenwarr at
Wed Oct 27 20:23:23 EEST 2004

On Wed, Oct 27, 2004 at 06:57:21PM +0200, nf wrote:

> KWIQ Qt adaptation layer:
> I'm just curious. Don't you think that such a "common main loop" would
> help to avoid lots of code duplication and improve (free)desktop
> interoperability? Maybe a little expert discussion could inspire someone
> to play with this...

Common mainloops are a wonderful thing that we should definitely have.  With
WvStreams and UniConf, we've done a bit of hackery to make this sort of
thing work (make the WvStreams/UniConf stuff all work asynchronously without
threads in your favourite mainloop, be it WvStreams, Qt, glib, or win32). 

If we can manage to agree on a common standard, that would be perfect.  I
think libevent should be that standard.  Just grab it and use it; it's the
basic model that everything else is based on anyway.  I'm pretty sure glib's
mainloop stuff is sufficiently flexible that you can probably do this pretty
transparently.  Qt, I'm not so sure.  Something about QSocketNotifier.

Combining the signals/slots mechanisms between Qt and GTK sounds messy and
scary, but simply running *both* signals/slots mechanisms on top of libevent
should be pretty straightforward.

Have fun,


More information about the xdg mailing list