Situation: you are writing code, it compiles OK, you execute it, but there are exceptions being thrown in the output window--e.g. "use getContentPane().add() vs. add()". The IDE could scan all messa
ges being displayed in the output window, looking for any that look like an exception with stack trace. For any such exceptions, it is possible to mechanically scan through the trace and find which c
lass was affected at each level in the backtrace, and if source if available, which line in the source file. For any such lines which are user-written classes--with source code present in the reposito
ry--the corresponding source file should be displayed in the Editor if it is not already; any line present in the backtrace marked with a special color (analogous to compiler error line markings, see
NbDocument.Colors); that line in the output window specially highlighted somehow; and double-clicking on such lines in the output window take you to the corresponding source lines, as with compiler er
This would greatly speed up the process of trying to figure out what you did that caused the exception, even if it was not your code that actually threw it.
Note that it is possible for the line numbers to be out-of-date w.r.t. to the class files, as the user may have edited the source before executing the class; ideally Positions in the editor would be e
mployed to smooth over this problem, although that would be more work, and would only work for the case of the user having compiled a source file and modified it before execution while leaving that ed
itor buffer open.