[DrJava] [ drjava-Refactorings-686785 ] Move "Save Interactions History" functionality to the model!

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

Refactorings item #686785, was opened at 2003-02-14 15:14
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=451586&aid=686785&group_id=44253

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Eric E. Allen (eallen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Move "Save Interactions History" functionality to the model!

Initial Comment:
Currently, the functionality called for saving interactions histories is in the view. Clearly, this functionality should be in the model. 

In fact, there is functionality to do it in the model, but this functionality doesn't allow for editing of the history before saving. In order to allow for editing, we'll have to augment the GlobalModel interface to allow for the recording of edits. We'll also have to add call backs to the view to start up the editing window.

Actually, what we'd really want to do is to be able to edit the interactions history in the definitions pane. Doing that would involve distinguishing Java files from history files in definitions.

Another more radically change would be to store interactions histories _as_ Java files, i.e., store all statements in a main method of a new class.Then we could replace the "save interactions histories" functionality with functionality that loaded interactions history into a new document in definitions. The user could then edit and save at will. Loading would involve interpreting the code in the main method.

The main task in this last idea would be to make sure that we only stored valid Java files.

-- Eric

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=451586&aid=686785&group_id=44253