Re: UI changes in reporting of exceptions

Marian Mirilovic wrote:

> Ahoj Jarda,
>
> Jaroslav Tulach wrote:
>
>> We have to solve http://www.netbeans.org/issues/show_bug.cgi?id=92075
>>
>> I propose to do it like this:
>> http://www.netbeans.org/source/browse/logger/uihandler/src/org/netbeans/modules/uihandler/api/doc-files/ui.html?r1=1.4&r2=1.4.2.1 
>>
>> e.g. keep to old dialog and just add to it the "Report..." button. I 
>> hope this is "compatible" change that will surprise nobody and give 
>> users an easy to use reporting style.
>
>
> I would say we can use the old dialog, we need to add just two 
> additional components to:
> - provide a way to Report a problem
> - provide a way to not show this dialog again
>
> The way we layout these components into current Unexpected Exception 
> Dialog depends on design and from my point of view is not so important.
> (link to original Exce.dialog/Red icon UI spec
> http://core.netbeans.org/proposls/exception_notification.html)
>
> What I am interested in is : do you want to report a problem 
> automatically (or it will report only if user pushes the "Report" 
> button) ?
>
I am for to send it automatically after agreement (selecting a check box).

>> PS: There was a suggestion to add a "Do not report again" button to 
>> the "Unexpected Exception Dialog" which could than stay on even in 
>> releases. I disagree. In my opinion until we are in production we 
>> need to shout about each error as much as we can, but when we get 
>> into a production, we need to be as quite about each error as 
>> possible. That is why I like current state. 
>
>
> I fully agree with your suggestion ... shout about each error until 
> FCS build, then be quiet !
>
> From users point of view, there are two separate "things" :
> - she encountered bug in the application
> - she could help - submit exception to NB-QE for processing
>
> For the first one, we need to inform user that "there is a problem" - 
> I think the current solution is fine - the red icon blinks for some 
> time and if user is interested in - she could open the dialog.
>
> For the second one, we need to ask user : she needs to agree with 
> submitting or submit exception explicitly into our DB. If the 
> exception will not be reported automatically and user has to push the 
> button - what will be the feedback for her ?
>
> If I was the person processing such reports(on NB-QE side) I would 
> need additional informations (the exception stack-trace itself is not 
> the only one information you need to evaluate a bug, so in this case 
> you need to contact reporter and ask her to provide more 
> informations), how do you want to get them if you don't have her email?
> Do you want to send message.log file as a part of the report ?
> Probably sending a few UI Gestures collected right before exception 
> would help, but I think we will still miss the contact on the reporter.
>
Jindrich Sedek is working on new Exception reporter project.

http://wiki.netbeans.org/wiki/view/ReportExceptionProjectUI

The exception stacktraces will be stored to database.  Description, 
module name, issue id, and commend  can be assinged To stacktrace. He is 
now experimenting with identification of duplicate exceptions. User will 
be inform that the exception was already reported and asked to add some 
comments to report. User can add to report his netbeans.org login name. 
The  reports  will be  analyzed  and reported to  issuezilla manually 
by  QA.  If user adds to report his netbeans.org user id QA can add his 
email to cc of issue. Does it make sence?

Petr

> Anyway, I think it's a nice way to help users report problems and 
> thank you Jarda for your asset, help and patience.
>
> *Marian