Linked by Thom Holwerda on Mon 6th Jul 2009 15:43 UTC
Thread beginning with comment 371914
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.
RE[3]: Comment by Mark Williamson
by vivainio on Mon 6th Jul 2009 18:56
in reply to "RE[2]: Comment by Mark Williamson"
GLib is an optional dependency of Qt. I think Qt can share even loop and some other part with glib so only one will run in the background and be loaded in memory, even if both Qt/KDE and Gnome apps are used at the same time.
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




Member since:
2006-06-12
GLib is an optional dependency of Qt. I think Qt can share even loop and some other part with glib so only one will run in the background and be loaded in memory, even if both Qt/KDE and Gnome apps are used at the same time.