Debugger configurations and KCM

Andreas Pakulat apaku at
Fri May 9 06:39:05 UTC 2008

On 09.05.08 02:09:50, Vladimir Prus wrote:
> Hi,
> right now the project configuration dialog is KSettings::Dialog. I
> would like to implement "launch configurations" where each project
> can have several configurations, and for each configuration we have
> several pages -- application, general GDB settings, maybe specific
> gdb settings, maybe valgrind settings, so on.
> So, instead of letting KSettings::Dialog load KCM pages, I need to
> have top-level configuration name selector, and based on selected
> configuration, show a specific set of pages. Am I right that KSettings::Dialog
> and KCModule are basically of no help here?

Well, in theory you could do that, because KSettings::Dialog allows to
specify a list of component names to load. That is already used to not
load qmake kcm for cmake projects (see ProjectControllerPrivate).

However I've already thought a couple of times that KSettings::Dialog
might not be flexible enough for our needs for project configuration. So
maybe we need to write our own dialog, but I don't think we should drop
kcm's as well. We may just need to expand their .desktop files a bit to
carry some more information.


You will feel hungry again in another hour.

More information about the KDevelop-devel mailing list