Re: UI changes in reporting of exceptions

<quote who="Marian Mirilovic">
> 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

This is what we need for sure.

> - provide a way to not show this dialog again

Do we really need it or want it? I do not think so. Jesse mentioned that he 
wants it, but imho it is not desirable to supres the dialog. We want bug 
reports and ignoring bugs in dev builds should not be easy.

> 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/proposals/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 want to unify the user experience when using UI Gestures. After each report 
(triggered by exception or explicitly in toolbar) a browser is opened and the 
user gets some value back. This does not work with automatic reports. That is 
one reason why I do not want that to be supported. The other includes ethical 
problems.

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

Ok.

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

Yes, red icon is fine.

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

Browser window that will say thank you and possibly will provide some useful 
suggestion for example describe a workaround to prevent that bug from 
appearing.

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

An interesting option is to leave her a message which she will see next time 
she submits something to the server.

> Do you want to send message.log file as a part of the report ?

I send var/log/uigestures.gz

> Probably sending a few UI Gestures collected right before exception
> would help, but I think we will still miss the contact on the reporter.

We really need an "identity". Not only to contact the reporter, but also allow 
people to use multiple userdirs and still share the same statistics. I plan 
to enhance the server side to have single sign-on with netbeans.org, but I 
need to learn javascript first...

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

Working with such talented, gifted and smart reviewer makes every problem easy 
thing to solve. Thank you for excellent feedback.

-jst