[kdevqtdesigner] Help to port kdevqtdesigner in to KDevelop 5
kfunk at kde.org
Thu Oct 18 06:44:59 BST 2018
On Wednesday, 17 October 2018 14:50:34 CEST René J.V. Bertin wrote:
> On Wednesday October 17 2018 13:06:19 Friedrich W. H. Kossebau wrote:
> >That is why plugins can be disabled if one does not use them.
> >Settings->Configure KDevelop...->Plugins, there disable all those you
> >personally do not need, by untoggling the checkbox of a plugin listed.
> Yeah, but it's never really clear which plugins are enabled when you start a
> new session, and AFAIK it isn't really possible either to unload plugins.
> More plugins also means longer build times if they cannot be (de)selected
> at that level.
> Qt Creator has a -noload option to disable loading of specific plugins at
> startup; I don't KDevelop has something similar, correct?
It has, in form of a env variable you can set:
... or multiple ones:
Wouldn't mind having sth similar as QtC's -noload in KDevelop, though. Patches
welcome, I guess. This one should be relatively trivial.
> >Miss it some more, and once you miss it enough to start researching the
> >state, you will find that it got ported, that it had been done as KPart
> Ah, indeed. I missed that, but then I've been keeping my KDE4 desktop and
> kuiviewer4 works just fine as a standalone viewer :)
> >Not only because KParts with their single-view/single-document principle do
> Can't you create a new, dedicated window and hand that to the KPart?
> >current workflow options available. Everyone has different needs.
> Yep, and you also cannot cater to everyone...
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 195 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop