default enabled plugins

[Milian Wolff]

Andreas Pakulat, 12.06.2010:
> On 12.06.10 20:11:32, Andreas Pakulat wrote:
> > On 12.06.10 16:44:24, Milian Wolff wrote:
> > > Hey there,
> > > 
> > > since I'll hopefully have soon the plugins imported into Quanta
> > > (waiting for Apakus help), I'll soon need/want a way to define a set
> > > of plugins that are enabled by default in Quanta or KDevelop.
> > > 
> > > There are a few that should not be enabled _by default_ in Quanta and
> > > vice versa. My current favorite way to handle that would be:
> > > 
> > > X-KDevelop-EnableByDefault=[yes|no|quanta,kdevelop,...]
> > > 
> > > yes == default == enabled in all KDevplatform apps on first start
> > > no == disabled in all KDevplatform apps on first start
> > > 
> > > strlist: only enabled by default in apps with that name, as identified
> > > by the KAboutData of the KDevplatform application.
> > 
> > As milian already said, the decision is to be done by the hosting
> 
> That was meant to be "As Aleix already said" of course :)

Hm ok, so each new plugin has to be registered there to become active by 
default? If you think that's how it should work, I'm OK with it.

Thanks
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100612/058ba497/attachment.sig>