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

List:       kde-devel
Subject:    nsplugin integration / move to kdebase/network
From:       Stefan Schimanski <1Stein () gmx ! de>
Date:       2000-05-03 14:02:18
[Download RAW message or body]

Hi,
as the netscape plugin support is quite stable now I would like to move it 
into one of the main modules, either kdebase/konqi or kdenetwork.

There is still another issue with the pluginscan utility. It has to be called 
by the user once to register installed plugins. This has to be done somewhere 
outside of the nsplugin code. These ways come to my mind:

1. call it once in kdewizard and let the user manually update his plugin list 
1.1 either with a kcontrol module
1.2 or somewhere in the browser setting dialog of konqui/khtml

The user would have to update manually when he adds new plugins to netscape 
in this case. Though users that know how to install netscape plugins will 
also be able to update the plugins in konqi. In a public network with a 
operator and several users this would be different of course.

2. call it everytime kde starts in kwelcome or kdeinit. This would be 
obviously the easiest for the user, but it increases kde startup time by less 
than a second. As Coolo said this isn't good at all for kde because kde's 
acceptance will partly depend on the speed of its startup.

3. call it on konqi startup. This would add slow down the startup time like 
above. But it would also remove the need of a kcontrol module or something 
like that. Everything is done automatically.

4. let the user decide whether it want konqi automatically look for new 
plugins.

What do you think about these options?

Stefan

-- 
-------------------------------------------------------
I have that old biological urge,
I have that old irresistible surge,
I'm hungry.

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