Linked by Thom Holwerda on Sat 25th Feb 2006 12:59 UTC, submitted by nzjrs
Qt "Yesterday, I got Qt running on top of the Glib main loop. By using the QAbstractEventDispatcher API, I was able to completely replace the entire event dispatching mechanism of a Qt 4 application with less than 600 lines of code. What does this mean?"
Thread beginning with comment 99076
To read all comments associated with this story, please click here.
by michi on Sat 25th Feb 2006 17:40 UTC
Member since:

This is great! I am really glad to see all this integration work. First a KDE frontend for beagle and now integration of the glib main loop into KDE.

As far as I understand this, this would make it possible to use gtk/gnome plugins in KDE applications and the other way round. Just imagine that all the plugins from gimp could be used in digikam/krita and the plugins from digikam/krita could be used in gimp. Of course it would require a lot of work to actually make this working and the projects would have to use a common plugin API, but I think the possibility is very nice.

And, as far as I understand, that would in prinicple also make it possible to use kparts in gtk/gnome applications and gparts (which don't exist yet) in KDE applications. A lightwight khtml-based webbrowser for gnome (it could just use the konqueror-kpart) would definitifely be a good idea.

I hope that this really will be used in future Qt releases.

Edited 2006-02-25 17:46

Reply Score: 2

RE: Great!
by Mystilleef on Sat 25th Feb 2006 18:17 in reply to "Great!"
Mystilleef Member since:

The equivalent of Kparts for GNOME is libbonobo(ui) or ORBIT. Most developers today acknowledge the COM fad is over and won't use such frameworks unless there's compelling reason to do so.

Reply Parent Score: 1

RE[2]: Great!
by g2devi on Sun 26th Feb 2006 01:00 in reply to "RE: Great!"
g2devi Member since:

There's one other alternative that's closer to Kparts that depends on the main loop integration:

Reply Parent Score: 1

RE[2]: Great!
by MightyPenguin on Mon 27th Feb 2006 15:48 in reply to "RE: Great!"
MightyPenguin Member since:

You mean most gnome developers have given up on COM ;) KDE folks still love and use kparts. I think gnome's COM failure had more to do with idealogical reasons then technical.

Reply Parent Score: 1