Adding build-set to working file set

[Aleix Pol]

On Thu, Jul 23, 2009 at 4:21 AM, David Nolden <
david.nolden.kdevelop at art-master.de> wrote:

> I think the build-set still lacks flexibility and manageability.
>
> Now the targets you want to build usually correlate with the files you
> edit,
> so what about merging the build-set into the working-set?
>
> To make it even more consistent, I propose renaming "Buildset" to
> "Targetset".
> Then the working-set tooltip would show under the "Documents:" a "Targets:"
> list if t here is a target-set, allowing easy management and overview of
> build
> targets.
>
> Also, that target-set could/should be used as default 'run' or 'debug'
> target,
> if there is only one runnable target in the target set, else a selection
> dialog could be shown.
>
> Last but not least, if it is empty the target-set should be auto-filled
> with
> the target that contains the currently active file, or if there is no
> active
> file, with all currently open projects.
>
> Using that scheme, we could solve some usability problems, as the simple
> cases
> would work configuration-less:
> - Usually, if you have one executable in your build-set, you will also want
> to
> run/debug that one
> - Usually, if you edit a source file that belongs to one executable, you
> will
> also want to build/run/debug that executable
>
> And for the more complex cases, the working sets would allow comfortable
> management of the build set.
>
> Greetings, David
>
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

Aren't you trying to make this whole workingset too complicated?

It's already complicated for users to understand them with just files. I
wonder if that won't make it harder to understand...

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090723/37426ee4/attachment.html>