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