Automatically add project to buildset?
Vladimir Prus
ghost at cs.msu.su
Fri Apr 25 08:44:06 UTC 2008
On Friday 25 April 2008 12:29:54 Andreas Pakulat wrote:
> On 25.04.08 10:52:16, Vladimir Prus wrote:
> > On Friday 25 April 2008 10:28:39 Andreas Pakulat wrote:
> > > On 25.04.08 09:01:00, Vladimir Prus wrote:
> > > > On Friday 25 April 2008 00:46:23 Andreas Pakulat wrote:
> > > > > Hi,
> > > > >
> > > > > apparently its a bit mysterious how to do building in KDevelop4, besides
> > > > > the actions beeing always active - which is going to be fixed sooner or
> > > > > later. So I'm wondering wether it makes sense to simply add a project to
> > > > > the buildset automatically when opening it and no item from that
> > > > > project is in the buildset? Better ideas?
> > > >
> > > > Have a notion of current project?
> > >
> > > We already have that, just not in the GUI. The project tree has a
> > > selection model, so we could just build the current selection. And once
> > > we disable the build actions when nothing is selected, it should be
> > > pretty clear where to go to build something.
> > >
> > > > While buildset might be handy, it's probably not as common as desire
> > > > to build just one project one is hacking on right now.
> > >
> > > Hmm, we can have support for building the active document, or even the
> > > target of the active document - if it is in a known project.
> >
> > I'm not sure if I like implicit behaviour. Maybe, the toolbar (currently
> > underused), should have a combobox that used to select what to build?
> >
> > In fact, I'm thinking about right debugger configuration, and thinking
> > about adding a combo to select the current debugger configuration. This
> > mean that the toolbar might have two comboboxes:
> >
> > 1. What to build.
> > 2. What to run/debug/valgrind/etc
> >
> > Which seems like a fairly clear approach to me.
>
> I could agree on the expandable toolbutton that eclipse has, as I think
> a combobox wastes too much space.
This is a matter of taste, but I think a "Build" button with dropdown list
attached will work equally well.
I'm not sure about "Run" and "Debug" -- because I prefer there to be a
single configuration that both Run and Debug uses, and the expandable button
does not make this link explicit.
>
> On a second thought: This would only allow to build individual projects,
> so for anything else you'd have to open the project manager again and
> add to your buildset what you want to build. Those buildsets then might
> also show up in the dropdown, but obviously listing all possible targets
> is not an option...
Yes. So maybe the dropdown can be initially populated with list of projects...
> Maybe the dropdown should have an action that activates the buildset
> editor, similar to the "Open Run dialog" in eclipse?
..and have an item to activate buildset editor, and as soon as you have some
buildsets, those appear in the list as well? We can also have default buildset
"All" that is always present in the list and builds, well, everything.
- Volodya
More information about the KDevelop-devel
mailing list