[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Swfdec/Konqi integration
From:       "koos vriezen" <koos.vriezen () gmail ! com>
Date:       2007-05-03 21:35:09
Message-ID: d4e708d60705031435o6cddeb3oe023f9f34bf3ed24 () mail ! gmail ! com
[Download RAW message or body]

2007/5/3, Thiago Macieira <thiago@kde.org>:
> koos vriezen wrote:
> >2007/5/3, Thiago Macieira <thiago@kde.org>:
> >> You cannot rely on the glib mainloop being used at all.
> >
> >The whole point of this glib mainloop was to make it easier for these
> >kind of things IIRC. Makes sense to me to advice this in the qt-copy
> >readme's.
>
> That would make glib a mandatory dependency for KDE in all KDE platforms,
> while right now it isn't so. (Yes, I know about shared-mime-data, but
> that's an external program that can be statically linked or duplicated)
>
> And I repeat: it can be turned off at runtime. You can't rely on it being
> there at all, unless you built your Qt.

So then you break it, really ..

> >But nspluginviewer now uses qxembed to embed in the nsplugin and dcop
> >for communications. Latter probably dbus in kde4. So why not
> >completely write nspluginviewer in gtk using gtkplug?
>
> That would make a fully-functional KDE-based browser dependent on gtk.
> It's out of the question.

On my system all plugins in /usr/lib/iceweasel/plugins are linked against
gtk. But if you say that moz-plugins can be linked w/o, than youre right
indeed.

Koos
[prev in list] [next in list] [prev in thread] [next in thread]