VCS Changes Toolview

[Aleix Pol]

On Fri, Jun 10, 2011 at 5:50 PM, David Nolden <zwabel at googlemail.com> wrote:

> I read the blog-post about the VCS changes toolview, but didn't test it
> yet.
>
> In general though, do we really need a new toolview for this? To me,
> this functionality belongs into the "Project" treeview. In general, it
> should be possible to see the VCS status of files in the projects
> toolview.
>
> Showing _only_ the changed files equals a filter of the project tree,
> and could be done by generalizing the filtering-capability. Instead of
> having a filter-line, we could have a filter drop-down, with these
> items (for example):
> * All (the default)
> * Open (would show only the files currently open, could eventually
> replace the "documents" view)
> * VCS Changes (would show the files that changed according to VCS)
> * [[filter-line-edit]] (would show the current filter line-edit)
>
> Instead of creating more and more hardly discoverable toolviews, we
> should search ways to consistently integrate the whole stuff.
>
> Greetings, David
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

The main difference is that in this case a plain list is easier to read
while the project view is a tree, and information gets hidden quite easily.

I agree that this information should be displayed in the project view, also,
but I think it's a different use case. I don't think it's about filtering.

I also agree that having too much toolviews can be counterproductive, but I
also think that rushing into having all data in the same place is not the
best scenario and could let us into a terribly cluttered interface that
wouldn't let one use case or the other.

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