plugin badness

Koos Vriezen koos.vriezen at xs4all.nl
Sun Mar 21 19:38:59 GMT 2004


David,

I afraid that I didn't get the message (and something has to be done because
sites are broken in 3.2.1 because of this). The plan is to let plugin provide
a pluginsinfo file. Is that okay with you?
A hardcoded list is the last thing we want IMO. It would mean third parties
can't add an entry (unfortunately KDE fails to attract those, but one day ..)

Koos

On Thu, Mar 18, 2004 at 09:18:35AM +0100, David Faure wrote:
> On Wednesday 17 March 2004 18:05, Koos Vriezen wrote:
> > On Tue, Mar 16, 2004 at 05:29:40PM -0500, George Staikos wrote:
> > > On Tuesday 16 March 2004 15:15, Koos Vriezen wrote:
> > > > > Now how could a kpart present itself as more then one plugin more
> > > > > generally? Also using properies in .desktop files.. doesn't sound that
> > > > > dynamic... Hmm, what if we add a pluginsinfo property that points to this
> > > > > file. So if a part has this property, try open this file and register
> > > > > plugin as it used to be.
> > > >
> > > > Attached this propery points to plugin info filename idea. Needs also a
> > > > small change in nspluginscan to add to
> > > > ~/.kde/share/services/nsplugin.desktop
> > > > X-KDE-BrowserView-PluginsInfo=nsplugins/pluginsinfo
> > > 
> > >    I really can't test or properly review right now, sorry.  I have to leave 
> > > it up to you to patch as you see fit.  In any case, KHTML generally gets 
> > > fully backported so you can expect that these things will end up in the 
> > > branch.  Please backport the fixes, though, in case they get lost somehow.
> > 
> > Ok, for others to comment a final version. It should be backwards compatable
> > with pre 'this stuff' plugin scans. Also changes for kjavaappletviewer
> > to participate in this plugin array.
> 
> Looks ok, but doesn't fully solve the problem, does it?
> 
> AFAICS this change means that there is now no more entry in navigator.plugins
> for "a postscript viewer" if one doesn't have a netscape plugin for it (but kghostviewpart)?
> Or SVG, which should embed ksvg.
> 
> I guess we also need a hardcoded list of mimetypes we accept to export to
> navigator.plugins then? (and to keep the code that your patch is deleting,
> for those .desktop files that don't have PluginsInfo but that we still want
> to export).
> Ah, either that or we ask e.g. kghostview and ksvg to provide a pluginsinfo
> file (was that the plan?).
> 
> -- 
> David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
> 




More information about the kfm-devel mailing list