The state of the object where the exception occurred can be very useful as well. A well implemented toString() is all you need. This will need to be done for every object, but that's a good idea anyway.
cc Chris Merrill wrote: > +1 > > We've implemented something similar - and it has been > a great convenience for our customers. Our next step > is to automatically submit a bug report with all > pertinent information (version, error log, open file, > license info, etc.) and the user's description of what > they were doing at the time. > > Nivy, Ofer wrote: > > > My suggestion: > > 1. Remove the DOS window. > > 2. Show these errors/exception in a dialog, WHEN the error happens. > > 3. Don't bother to implement some fancy report mechanism. A text pane with > > the stack trace and some additional data (e.g. JVM version, OS), formatted > > in your preference, will do the work. > > 4. Important: make it optional. Not all the users wishes to report bugs, and > > they would prefer not to be bothered with this dialog. If there'll be an > > error that appears frequently, even the most active bug reporter, will wish > > to turn this feature (dialog) off. > > 5. Write everything to a log file. > > ********************************* > Chris Merrill > [EMAIL PROTECTED] > ********************************* > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
