From kde-devel Sun Apr 30 19:39:00 2000 From: Stephan Kulow Date: Sun, 30 Apr 2000 19:39:00 +0000 To: kde-devel Subject: Re: calling pluginscan in kdeinit X-MARC-Message: https://marc.info/?l=kde-devel&m=95712376326183 Stefan Schimanski wrote: > > Am Sun, 30 Apr 2000 schrieb Stephan Kulow: > > Stefan Schimanski wrote: > > > Hi, > > > I would like to add pluginscan (that registers netscape plugins) into the > > > start process of KDE. I would launch it in kdeinit like klauncher and > > > kdesktop. Is this the right place to do this? > > > > Definitly not. correct me if I'm wrong, but netscape plugins are only > > useful for webbrowsing, no? > > Maybe I have to explain why I want to start it there: > pluginscan scans several local dirs to find netscape plugins. for these it > creates .desktop mime definitions in the user's ~/.kde directory to set the > nsplugin kpart as the default app for those files. > Because the user can install new plugins as he wants we have to find out > about it before any plugin code can be run. > We have to start pluginscan somewhere, optimally on every startup. We can't > do this anywhere in the nsplugin code because this is loaded as a kpart as > reaction on an installed mime type. Somehow we have to create these mime > definition at first. > Is there another way to this than in kdeinit? Then please tell me. > Then start it at the same time as the user would rerun kappfinder. We don't scan for new apps on each start either - why should we for nsplugins? Greetings, Stephan -- It said Windows 95 or better, so in theory Linux should run it GeorgeH on /.