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

Levi Bard taktaktaktaktaktaktaktaktaktak at gmail.com
Fri Oct 16 08:54:42 EDT 2009

>> 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.

> If we get this right, we will make users happier. If we are too
> disruptive without considering the consequences, we will lose users.
> Don't forget that users come from different perspectives, and emacs
> and Xcode users like yourself are a tiny minority compared to those
> who are familiar with other IDEs, especially VS. Blithely dismissing
> these other viewpoints is incredibly counterproductive. We should be
> discussing how we can make it more usable for everyone.

I'm in agreement here as well - forcing users to conform to a
particular worldview is one of the reasons Eclipse is so polarizing.


More information about the Monodevelop-list mailing list