On Wednesday 30 April 2008, Emmanuele Bassi wrote:
> On Wed, 2008-04-30 at 19:06 +0200, Pau Garcia i Quiles wrote:
> > > by the way: GIO implements various fd.o specifications - the
> > > thumbnailing specification, the trash spec, the shared mime info spec,
> > > etc. exactly like KIO does.
> >
> > KIO and GIO could have shared plugins ("slaves", in KIO slang) but
> > they do not. That would have been very useful.
>
> how would have this been even possible? GIO backends are implemented as
> GObject using the GModule API, and they are even out of tree from the
> GIO main library (see the gvfs module inside GNOME's SVN).someone's already done it ;) KIO slaves run out-of-process and have no inherent event loop of their own. they just need to implement the proper IPC (d-bus) interface to communicate and register with the system configuration (a .desktop file). even if there was a Qt event loop, however, Qt4 builds with the glib event loop if glib is available on the system. this allows us to run glib based plugins, etc within a Qt (and by extension, KDE) based application. the reverse should also be true, at least as far as the event loop part goes. this is not theory, either, i've seen gtk+ based plugins running in a Qt app due to using the glib event loop as a common basis. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Trolltech
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
