[MonoDevelop] Fatwa: bring the XCode error/warning reporting to MonoDevelop.

[Chris Howie]

On Fri, Oct 16, 2009 at 8:54 AM, Levi Bard
<taktaktaktaktaktaktaktaktaktak at gmail.com> wrote:
>>> I never get the error pad and think to myself "Let us look at all the
>>> possible errors and pick the one I want to fix first".   When you are
>>> developing, all you care about is hitting the next one.   We can keep it
>>> around for log or diagostic purposes, but with bubbles, it becomes
>>> effectively useless.   I have yet to use that in XCode, ever.
>>
>> Well, *I* like to be able to skim the list of errors first to get an
>> idea of what was broken. Things can be more complicated, for example,
>> when autogenerated code is involved, and you sometimes need to get the
>> big picture to see what's happened.
>
> I agree with this - I always want to see the full list of errors,
> particularly if jumping to the "first" one is going to rudely yank me
> into another source file halfway across the solution.

I don't like to "me too" very much, but I feel I should here.  It's
very useful to be able to skim the list of errors, especially because
sometimes one error is actually only caused by another error.  Usually
I can do a better job of figuring out where the real problem is than
the IDE, and I would prefer to investigate the error list instead of
being thrown to the first error.

Personally, I just unpin the error list, and that works well enough
for me.  I would at least argue that even if there is another,
alternative workflow introduced, it should not remove the possibility
of MD behaving like it does right now.  I might consider using the
error bubbles, but usually by the time I double-click the build error
to fix it, I already know what the problem is and don't need to see
the error again inline.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers