Re: UI changes in reporting of exceptions

Jindrich Sedek wrote:
> We don't need mounts of stacktraces without any info. It's not
> valuable for us.

I disagree. *One* stack trace without any info is not very valuable. 
5113 identical stack traces in the first month after a release is very 
valuable information. It means that part of the code is badly broken and 
unreliable. It may not be obvious at first why the code is broken, but 
the developer responsible for this code had better spend some time 
looking at it very carefully, and making some kind of fix - at a 
minimum, adding better diagnostics.

> I believe user can give us some more information, why not to ask him
> to give us some help?

We don't want to make it look like work or most people will just hit 
Cancel. The user is already probably frustrated and has a low opinion of 
the IDE if an exception was just thrown. Maybe offer an "Advanced>>" 
section for people who are knowledgeable about nb.org issue tracking to 
select a specific component, add details about how to reproduce, enter a 
nb.org user ID, etc. Just make it clear that the average user does not 
need to do anything except click "Send".

-J.

-- 
[email protected]  x22801  netbeans.org  ant.apache.org
       http://google.com/search?q=e%5E%28pi*i%29%2B1