[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ant-dev] Ant Console vs. Debug Console
|
personally I think this will look like angry fruit salad (technical term :
-). In large logs (e.g., eclipse build logs) it is useful to be able ot
just collapse whole targets. The color thing doesn't scale well
cognitively. That is, show me 2 or three colors ok, great. Show me a log
with 10 colors and I start wondering what color puce is anyway. Structure
is way better. That's why Explorer uses tree lists with indentation
instead of coloring depth 1 things blue, depth 2 things red, ...
Having said thta, there is a good argument for just giving the standard Ant
output as some people/tools are used to that.
Jeff
Jared Burns
<jared-eclipse@xxxxxxxx To: platform-ant-dev@xxxxxxxxxxx
m> cc:
Sent by: Subject: Re: [platform-ant-dev] Ant Console vs. Debug
platform-ant-dev-admin@ Console
eclipse.org
10/22/2002 03:02 PM
Please respond to
platform-ant-dev
I should add that as a replacement for the structured output pane, I'd like
to
just structure the output such that you can see where each message was
generated. Something like so:
<bk> - black
<bl> - blue
<rd> - red
<bk><project: foo></bk>
<bk><target: grah></bk>
<bl>This is my output</bl>
<bk><target: blah</bk>
<rd>This is my error message<rd>
The benefit of this approach is that you can immediately see where the
output
was generated. For example, it's clear that "This is my output" was
generated
by the "grah" target.
- Jared
On Tuesday 22 October 2002 01:38 pm, Darin Wright wrote:
> I appreciate the feedback and requests we have received from
> users/developers regarding Eclipse's Ant integration.
>
> One of our goals is to combine the Log Console with the Debug Console
> (thus, only having one console, and the ability to look at past output
> from previously run Ant scripts). However, there are a couple of features
> the Log Console supports that are not provided by the debug console:
>
> * Structured Output: The log console provides a tree view of the output,
> corresponding to Ant tasks. The debug console does not support structured
> output.
> * Colored coded output for five message types (error, warning,
> information, verbose, and debug). The debug console provides colors to
> distinguish between standard error, out, and in.
>
> Thus, I would like to hear from users if they actually use these
features,
> and if they would be missed. We do not neccessarily need to lose these
> features - but adding these concepts to the generic debug console would
be
> more work. We need a way to prioritize the work.
>
> Please note that one of our goals is to provide "hyper-links" from Ant
> error output in the console, to the associated task in an editor. This
> might be viewed as a replacement for determining which task error output
> is associated with (if the tree view is used for that currently). As
well,
> we could provide links from information messages to associated tasks in
an
> editor.
>
> I will also post this note to the newsgroup, where a wider audience may
be
> available.
>
> Thanks,
>
> Darin
_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
