[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Better toolview
From: Aleix Pol <aleixpol () kde ! org>
Date: 2010-11-29 19:28:27
Message-ID: AANLkTins2JJVV1PN8BfYnKZw_AQ8n+1YdXO9kpr0AdWW () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Nov 29, 2010 at 8:20 PM, Silv=C3=A8re LESTANG
<silvere.lestang@gmail.com>wrote:
> Hey,
> a lot of plugins and features (Build, Run, Debug, Test and Version Contro=
l)
> use the standardouputview for displaying what they need to display. But t=
his
> toolview is quite generic and doesn't correspond to the needs of most of
> them, and thus make it difficult to users to understand the UI (the previ=
ous
> and next buttons doesn't always do something and the two buttons "Select
> activated item" and "Focus when selecting item" are difficult to understa=
nd
> and irrelevant sometimes).
> I try in the last few days to see if it was possible to improve the
> standardouputview to full fit the needs of all plugins and features but I
> arrived to the conclusion that it's useless as every plugins have a sligh=
tly
> different needs.
> So I proposed to create a new toolview for each plugins or features which
> need one, starting by the Build feature.
> I think we need to keep the previous and next item, remove the "Select
> activated item" and "Focus when selecting item" buttons and replace them =
by
> a warning and error buttons that we can toggle to display only warnings
> and/or errors. I make a little mock up here:
> http://www.kdevelop.org/mediawiki/images/b/b8/Build_toolview.png
> What do you think about that?
>
> Silv=C3=A8re
>
>
> --
> KDevelop-devel mailing list
> KDevelop-devel@kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
Well, you don't want to create new toolviews for every plugin, we can
provide actions from the plugins, though.
Aleix
[Attachment #5 (text/html)]
<div class="gmail_quote">On Mon, Nov 29, 2010 at 8:20 PM, Silvère LESTANG <span \
dir="ltr"><<a href="mailto:silvere.lestang@gmail.com">silvere.lestang@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> Hey,<br>a lot of plugins and features (Build, Run, \
Debug, Test and Version Control) use the standardouputview for displaying what they \
need to display. But this toolview is quite generic and doesn't correspond to the \
needs of most of them, and thus make it difficult to users to understand the UI (the \
previous and next buttons doesn't always do something and the two buttons \
"Select activated item" and "Focus when selecting item" are \
difficult to understand and irrelevant sometimes).<br>
I try in the last few days to see if it was possible to improve the standardouputview \
to full fit the needs of all plugins and features but I arrived to the conclusion \
that it's useless as every plugins have a slightly different needs.<br>
So I proposed to create a new toolview for each plugins or features which need one, \
starting by the Build feature.<br>I think we need to keep the previous and next item, \
remove the "Select activated item" and "Focus when selecting \
item" buttons and replace them by a warning and error buttons that we can toggle \
to display only warnings and/or errors. I make a little mock up here: <a \
href="http://www.kdevelop.org/mediawiki/images/b/b8/Build_toolview.png" \
target="_blank">http://www.kdevelop.org/mediawiki/images/b/b8/Build_toolview.png</a><br>
What do you think about that?<br><font color="#888888"><br>Silvère<br><br>
</font><br>--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
<br></blockquote></div><br><div><meta http-equiv="content-type" content="text/html; \
charset=utf-8">Well, you don't want to create new toolviews for every plugin, we \
can provide actions from the plugins, though.</div> <div><br></div><div>Aleix</div>
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic