Re: philosophical question about frequent saving of files

Tor,

Couldn't agree more.

>> So you'll end up with a lot of "saved for build on <date-timetamps>".
>> Sounds like a recipe for information overload :-)
>>
>> What I"m saying, unlike what Mr. Hollingsworth read, is wouldn't it be
>> possible to factor the three systems you're now proposing undo/redo,
>> short-term saves and sccs saves into something that uses only two
>> mechanisms? Otherwise it's going in the direction of PERLs a curlique
>> per itch.
>
>
> I think we agree that SCCS/VCS is not the right place for this.
>
> Yes, we can couple undo/redo with auto saves. But I want more than  
> Undo/Redo offers. I want persistence across IDE sessions. I want to  
> be able to view the "deltas", not just be able to apply them (back  
> with undo, forward with redo) and diff them.
>
> This could obviously be combined with the undo concept somewhere -  
> but personally I found the Versioning tab in JBuilder intuitive and  
> useful. I didn't experience the information overload you're  
> describing - I only see the save versions when I open the Versioning  
> tab for a particular file - and in that case I really do want to see  
> what backups I have available.

+1

Richard