Re: UI changes in reporting of exceptions
Jesse Glick <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.user-interface |
|---|---|
| Organization | Sun Microsystems / NetBeans |
| Message-ID | <[email protected]> |
Jindrich Sedek wrote: > http://www.netbeans.org/source/browse/*checkout*/logger/uihandler/src/org/netbeans/modules/uihandler/api/doc-files/ui.html > http://wiki.netbeans.org/wiki/view/ReportExceptionProject IMHO: keep it very, very simple for the user. Do not require them to register on netbeans.org or you will lose most of the potential reports. Do not make them wait while you look for duplicates; duplicates can be detected using a database query later. Do not even ask them for component and subcomponent; if it's a stack trace, we can get that information ourselves. And do not bother asking "what were you doing?" - they were using the IDE, and it broke. If the stack trace does not include enough information to diagnose and maybe fix the problem, it is the developer's responsibility to include information assert statements earlier in the source, attach information about the problematic content, etc. - then someone using a later version of the IDE who has the same problem will produce a more useful stack trace. -J. -- [email protected] x22801 netbeans.org ant.apache.org http://google.com/search?q=e%5E%28pi*i%29%2B1