Default-Selection of plugins

[Andreas Pakulat]

Hi,

I'm currently implementing the plugin selection (via kpluginselector) and
found one small issue:

Who should decide which plugins are loaded "by default", i.e. when
initially starting the kdevplatform application.

The way supported "out of the box" by KPluginSelector and KPluginInfo is a
key in the .desktop file of the plugin. 

The other way would be what we're using right now: a list supplied by the
actual application thats built on top of kdevplatform (currently hardcoded
in code, but could be moved to a .desktop file).

On the pro side of the first option is that the code is there, in kdelibs,
we don't need to maintain it (we just need the reading/writing of the
relatively special config infos). On the downside: all applications using
kdevplatform will load all installed plugins that are flagged "enable by
default". So even when starting quanta you'd end up with kappwizard loaded
if kdevelop has been installed -> not so nice.

I guess I just answered my question which way to go, because that last part
is simply unacceptable I think. Opinions?

Andreas

-- 
Give your very best today.  Heaven knows it's little enough.