Re: [WWdevel] WeBWorK 2.2 prerelease, code freeze in a branch?

[Michael G. <ga...@ma...>]

>
>> Then there is the issue of opening new windows, which I always  
>> found terribly confusing, and I think may have been the real  
>> source of problem for our professors   For example, if you edit a  
>> problem then view it, you get a new window (fine) and in that  
>> window there is "Edit this problem", and pressing this gets me an  
>> editor in the same window.  I now have two edit windows that I  
>> think of as being the same file, but they aren't.  The new window  
>> opened a view of a TEMPORARY file, and we are now editing the  
>> temporary file as a SECOND temporary file.
> Is this really true?  I don't think that more than one temporary  
> file is created -- that certainly wasn't intended.  The original  
> editor kept all temporary data in the HTML itself.  In some sense  
> this was good, but lead to pretty large files being transmitted  
> back and forth -- if your login timed out you were likely to loose  
> all your edits.  The current effort is to mimic this behavior but  
> keep the temporary data on the server.

I haven't been able to duplicate this behavior yet. I'll try again a  
bit later tonight.

  However I do get messages such as the one below when I "view"  
changes in a problem.