Debugger configurations and KCM

Andreas Pakulat apaku at
Fri May 9 19:19:34 UTC 2008

On 09.05.08 11:22:13, Vladimir Prus wrote:
> On Friday 09 May 2008 10:39:05 Andreas Pakulat wrote:
> > 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).
> Well, yes, but, I want to have a launch configuration selector at the top
> of dialog, and depending on selected configuration, repopulate the list of
> pages. Like, if you select "Python application" configuration, it does
> not make sense to present GDB options.

I think I'm missing your vision :) If you have a dialog which shows run
configurations and a selector how do you see multiple different launches
at once? i.e. one for each executable in each of the projects?

Currently the run config dialog does have that in itself, i.e. there's a
combobox to select the run config and then you can tweak its settings.
However that run dialog doesn't belong into the project options, running
something doesn't depend on a project.

Does it make any sense at all to have a combobox which switches the
kcm's? I mean shouldn't we maybe have just the tree like eclipse has? I
can't help it but I think it makes sense to see the launches under the
launch config type in a 2-level-tree instead of having to work with a

oh and in the above text I use launch and run interchangeably.


You are a bundle of energy, always on the go.

More information about the KDevelop-devel mailing list