[DrJava] [ drjava-Feature Requests-520719 ] make Compile button semantics intuitive

[<no...@so...>]

Feature Requests item #520719, was opened at 2002-02-20 15:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=438938&aid=520719&group_id=44253

Category: User interface
Group: None
Status: Open
Priority: 5
Submitted By: John Garvin (johngarvin)
Assigned to: Nobody/Anonymous (nobody)
Summary: make Compile button semantics intuitive

Initial Comment:
I was going to submit this as a bug, but the code
actually follows the specification, so it's not
"really" a bug.  I just think the specification is
wrong.

You have to save before you can compile.  We know this,
but to a new user, this fact is hardly intuitive. 
There is no immediately obvious reason why the Compile
button is initially unavailable, and it's not at all
clear what has to be done to allow one to compile.

Possible solution: the Compile button should really be
a "Save and Compile" button, which will (a) decide if
saving is necessary, (b) if so, save the file, and (c)
compile.  If the current document is untitled, it
should pop up a "Save As..." dialog.  Right now,
there's no connection between the Save and Compile
actions, which is quite confusing.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=438938&aid=520719&group_id=44253