#99 compiler message printing

[Christopher Haynes]

When students come for help, it helps a lot if they bring
a printout of the compiler error messages, as well as
the source code.

Please provide a way to print these messages, ideally
with a print command for the purpose (might also be
commands for printing the interactions and console
window contents, though that is currently possible with
copy and paste). At the least, make copy work in the
compiler output tab.

[Charles Reis]

Logged In: YES
user_id=429731

Seems like Test Failures would also be a good candidate for
printing support. I hate to have up to 4 print items in the
File menu, though-- perhaps choosing Print can bring up a
dialog asking which component to print (Definitions,
Interactions, Compiler Output, or Test Output).

The flip side is that it should also be easier to copy
compiler output. Both the Compiler Output and Test Output
tabs are due for a refactoring, and I think this is the only
easy way to address this issue (because of the way the
components are laid out). But that shouldn't take very
long, and should allow us to have a much cleaner error
interface.

[Christopher Haynes]

Logged In: YES
user_id=559566

I agree all 4 print options are desirable. It's not important to
me what the user interface for it is.

I also agree that it is highly desirable for coping be possible
just about everywhere. I'm frequently bothered that text in
dialog error messages, even those with a lot of specific
detail, usually can't be copied.

[Charles Reis]

Logged In: YES
user_id=429731

I haven't gotten to changing the print framework yet, but
the text from the Compiler Output and Test Output tabs can
now be selected and copied. To make this easier, the error
highlight goes away if the user is selecting text in the
tab. (This is present in the drjava-20021029-1841 commit.)

[Peter Centgraf]

Logged In: YES
user_id=431096

I've added more discussion for this in the "Print Interactions
Pane option" request.

<http://sourceforge.net/tracker/index.php?
func=detail&aid=591642&group_id=44253&atid=438938>

The guts of our compiler error handling have been significantly
refactored as part of our Javadoc integration work, and I
agree that the view needs similar work. See also "Modify
compiler errors interface":

<http://sourceforge.net/tracker/index.php?
func=detail&aid=540293&group_id=44253&atid=438938>

We should ensure that our changes for that feature request do
not conflict with the ability to copy/paste easily.