DrJava Legacy SVN Repository

Creating a document lock free copy of the trunk

Moved the place the last survey result is saved so DrJava does
not ask again the next time it starts in case "No" was pressed.

This commit fixes a problem with the DrJavaErrorWindow. If an
unhandled exception occurred before MainFrame was completely
initialized, the DrJavaErrorWindow was not displayed, yet the
application did not terminate.
When the "Tabbed Panes" are detached, now displayes the
detached window when the panes are displayed by invoking
Find/Replace, Bookmarks Panel, Breakpoints Panel, Compile,
Test, etc.
Renames the debugger's detached frame "Debugger" (accidentally
left as "Tabbed Panes").

M src/edu/rice/cs/drjava/ui/MainFrame.java
M src/edu/rice/cs/drjava/ui/DrJavaErrorPopup.java
M src/edu/rice/cs/drjava/ui/DetachedFrame.java
M src/edu/rice/cs/drjava/ui/DrJavaSurveyPopup.java
M src/edu/rice/cs/drjava/ui/ExecuteExternalDialog.java
M src/edu/rice/cs/drjava/ui/DrJavaErrorWindow.java

Made debugger pane detachable (Debug menu, Detach Debugger).
Fixed problem with two modal windows both trying to stay on top,
which caused flickering and made DrJava unresponsive.
Added revision number and build time to the DrJava survey.

M src/edu/rice/cs/drjava/config/OptionConstants.java
M src/edu/rice/cs/drjava/ui/MainFrame.java
A src/edu/rice/cs/drjava/ui/DetachedFrame.java
D src/edu/rice/cs/drjava/ui/TabbedPanesFrame.java
M src/edu/rice/cs/drjava/ui/DrJavaSurveyPopup.java
M src/edu/rice/cs/drjava/ui/config/ConfigFrame.java
M src/edu/rice/cs/drjava/ui/DrJavaErrorHandler.java

This revision (i) streamlines the implementation of findNext (by
relying on hourglassOn instead of read locking to ensure mutual
exclusion) and (ii) re-implements the aborted changes to
ReducedModelBrace. I have no idea why the changes in (ii) did not
produce the same performance bug introduced in r4521. This revision
also includes some cosmetic formatting changes.

The following files were modified:

M src/edu/rice/cs/drjava/DrJavaRoot.java
M src/edu/rice/cs/drjava/model/debug/jpda/JPDADebugger.java
M src/edu/rice/cs/drjava/model/definitions/ColoringGlyphPainter.java
M src/edu/rice/cs/drjava/model/definitions/CompoundUndoManager.java
M src/edu/rice/cs/drjava/model/definitions/ColoringView.java
M src/edu/rice/cs/drjava/model/definitions/DefinitionsDocumentTest.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/ReducedModelComment.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/AbstractReducedModel.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/ReducedModelControl.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/TokenList.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/BraceReduction.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/ReducedModelBrace.java
M src/edu/rice/cs/drjava/model/definitions/reducedmodel/ReducedModelTest.java
M src/edu/rice/cs/drjava/model/junit/DefaultJUnitModel.java
M src/edu/rice/cs/drjava/model/repl/InteractionsScriptModel.java
M src/edu/rice/cs/drjava/model/AbstractDJDocument.java
M src/edu/rice/cs/drjava/model/DummyOpenDefDoc.java
M src/edu/rice/cs/drjava/model/FindReplaceMachine.java
M src/edu/rice/cs/drjava/model/AbstractGlobalModel.java
M src/edu/rice/cs/drjava/model/DJDocument.java
M src/edu/rice/cs/drjava/config/ConfigOptionListeners.java
M src/edu/rice/cs/drjava/ui/MainFrame.java
M src/edu/rice/cs/drjava/ui/ExternalProcessPanel.java
M src/edu/rice/cs/drjava/ui/EditExternalDialog.java
M src/edu/rice/cs/drjava/ui/NewVersionPopup.java
M src/edu/rice/cs/drjava/ui/config/KeyStrokeOptionComponent.java
M src/edu/rice/cs/drjava/ui/MainFrameTest.java
M src/edu/rice/cs/drjava/ui/ExecuteExternalDialog.java
M src/edu/rice/cs/drjava/ui/FindReplacePanel.java
M src/edu/rice/cs/drjava/ui/InteractionsController.java
M src/edu/rice/cs/drjava/ui/ReverseHighlighter.java
M src/edu/rice/cs/util/swing/FontChooser.java
M src/edu/rice/cs/util/swing/ScrollableListSelectionDialog.java
M src/edu/rice/cs/util/swing/SwingWorker.java
M src/edu/rice/cs/util/swing/ScrollableListDialog.java

Added "Detach Tabbed Panes" menu item in "Edit" menu to
move tabbed panes from bottom of MainFrame into separate
window.

Fixed problems with series of external processes on Windows.
The problem was that the process separator colon (':') was also
used in drive letters (e.g. "C:\WINDOWS") and that the colon
in the drive letter was used to split the path in two (i.e.
"C" and "\WINDOWS").
To keep things simple, I changed the process separator from
':' on Windows and ';' on Unix to '#' (pound) on all systems.
The pipe separator to pipe output from one process into the
next process remains '|' (pipe).

Added ObjectUtil. Implemented IterUtil.conditionalSnapshot and CollectUtil.conditionalSnapshot (with Composeable interface used for support); various CollectUtil methods.

This commit moves all Swing pack operations inside the event thread.
Is this necessary? Without a detailed analysis of the Swing library,
we don't know for certain. Sun recommends that all GUI code run in
the event thread (with a very short list of exceptions), but we have
found this practice produces unacceptable startup overhead. An
earlier discpline promulgated by Sun stated that GUI components could
be manipulated outside the event thread until they were "realized" but
this guidance is rather vague. If it means before any GUI component
is realized (which starts the event thread), then it clearly looks OK
but how can a programmer designing a specific GUI class know if any
other GUI component has been realized?. This is a global property of
a program. On the other hand, the more liberal interpretation that
each individual GUI component can be manipulated before it is realized
is clearly too liberal because the manipulation might link this
component into an existing GUI component that has already been
realized and is being accessed by the event thread potentially
traversing the unrealized component in the process. So I think Sun
really intended to mean that a GUI component can be safely manipulated
outside the event thread until it becomes accessible to the event
thread. The tricky issue is determining when a GUI component becomes
accessible to the event thread. The pack() operation is particularly
problematic because it may operate on the component after making it
accessible to the event thread. In contrast, setVisible(true) seems
less threatening because it intuitively involves creating a single
reference to the GUI component (in a data structure recording what is
visible) and nothing more.

If we subsequent study the Swing library (which of course can change
from one release to the next) and determine these concerns are
misplaced (because, for example, the pack method is very carefully
coded not to perform any operations on the packed component after it
has been made known to the GUI, then all of these pack operations can
be moved back to their "parent" threads.

The following files were modified:

M src/edu/rice/cs/drjava/DrJavaTestCase.java
M src/edu/rice/cs/drjava/model/MultiThreadedTestCase.java
M src/edu/rice/cs/drjava/ui/config/KeyStrokeOptionComponent.java
M src/edu/rice/cs/drjava/ui/ProjectMenuTest.java
M src/edu/rice/cs/drjava/ui/MainFrameTest.java

This commit is an attempt to fix an occasional
ArrayOutOfBoundsException bug in the setUp method for ProjectMenuTest.
This attempted fix probably does not address the real problem since the
exception was thrown in the bowels of Swing library code invoked from
MainFrame.<init> and this fix simply moves the subsequent frame.pack()
operation to the event thread. Why not move MainFrame <init> to the event
thread? It slows down unit testing considerably.

I don't know what the event thread is doing between tests in a unit
testing suite. Is is already running when the test starts?

The following file was updated:

M src/edu/rice/cs/drjava/ui/ProjectMenuTest.java