Re: [tasklist] compiler module feedback

Hi Tor,

> I've tried the compiler module now. (Unfortunately I build mostly
> via ant, so until that issue is resolved it won't help me a lot.
> But once the full projects support is added, I'll probably switch
> back to regular compilation.)

I use it for single files (F9)

>
> Anyway, Jesse Glick reads this newsgroup now and then, and I'm
> pretty sure he wrote the ant integration module (or at least has
> done some work on it) so he may have ideas for how this could be
> done.  Perhaps we'll need a third integration module, one which
> hooks into the ant module's apis for replacing its output API
> calls...

What about the TL API enhancements?

>
> Now some UI feedback.
>
> First, I see that you let each compiler error take up multiple
> lines in the output.
>
> I presume this was done so that the user can easily see all the
> output from the compiler. But I think it's a bit confusing.

No. It is an error in the core. The output of a compiler is not parsed well.
This is why calling javaparser:handleError is not a good idea right now.

>
> Finally, a very minor comment. The warning icon is a bit larger than
> the error so it stands out a bit. I had created a warning icon
> for the javaparser module earlier (when I thought I could get warnings
> from the background parse - but it turns out they're not generating
> warnings at all). It's the same as the error icon, but with
> warning-colors instead. I've attached it, in case you like it.

I created a big error icon instead.

> P.S. I notice you've added some good generic cell renderers to the
> compiler module, for example one which renders strings in a "normal"
> color, not the grayed-out color used for read only fields elsewhere.
> Perhaps these could be moved to the core module so that they're
> available elsewhere? In the buglist module, for example, all fields
> are "gray" (because they're read only) but that seems a bit unnecessary,
> and makes it harder to read.
>
OK

Tim