Linked by Thom Holwerda on Mon 6th Jul 2009 15:43 UTC
Thread beginning with comment 371919
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2008-12-26
Yes, Qt can (and does) use the glib event loop. This is a big deal, since it means you can use libs from gnome/glib crew that interact with the event loop (register timeouts, use dbus, poll on sockets...) without modifications.
Conserving memory is besides the point.
It might be cool to factor the event loop out from the rest of the glib, and establish it as a lean "Unix event loop" :-). Rest of the glib is pretty pointless when you have QtCore around.
Incidentally, I'd like too QtCore & C++ pushed forward in Linux userspace "core" development much more now that it's LGPL, instead of being systematically shot down in favor of glib; see
http://lists.kde.org/?l=kde-core-devel&m=124656875804833&w=2