Well that's called database ;)
Cheers!
-Boris (via BlackBerry)
----- Original Message ----- From: squeak-dev-bounces@lists.squeakfoundation.org squeak-dev-bounces@lists.squeakfoundation.org To: The general-purpose Squeak developers list squeak-dev@lists.squeakfoundation.org Sent: Sun Jan 13 04:25:23 2008 Subject: Re: Programmatically save image, and also do it periodically
Yea, code is journaled for sure. I have recovered code from a crash before. My impression was that they want this image save due to losing application data which isn't journaled.
On Jan 10, 2008 5:48 AM, Boris Popov boris@deepcovelabs.com wrote:
I'm not a Squeak user, but in VisualWorks if you work in chunks and publish your work in progress few times a day you can easily recover anything in between from a change set in a minute or two at most depending on complexity of changes. Doesn't Squeak have the same capability? Image auto save just smells wrong to me.
Cheers!
-Boris (via BlackBerry)
----- Original Message ----- From: squeak-dev-bounces@lists.squeakfoundation.org squeak-dev-bounces@lists.squeakfoundation.org To: squeak-dev@lists.squeakfoundation.org squeak-dev@lists.squeakfoundation.org Sent: Wed Jan 09 20:44:20 2008 Subject: Re: Programmatically save image, and also do it periodically
"tim Rowledge" tim@rowledge.org wrote
Auto-save, here I come ... :-)
Beware of the dangers herein. If you make some dangerous change and it auto-saves ... you've now got a live image with the dangerous state and
a
saved image with the dangerous state.
Ah, thank you for the warning! Perhaps I will use Save as New Version, (and set the timer a bit longer :-)
Sophie
squeak-dev@lists.squeakfoundation.org