Smalltalk › Pharo › Pharo Smalltalk Developers

confused about the "image opening session"

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

stepharo

confused about the "image opening session"

Hi

I saw that we have a new cool feature that presents changes that would
have been loaded but not save in the image.

Now I got confused because several times I prompted with this list and I
do not see how I ended up having it

since I save my image and did not get crash (or idea that I lost changes).

Is it me that do not understand correctly this feature?

At the minimum it would be nice to have a little bit more explanation
about what is happening.

Because I imagine new guys coming and seeing this list without any
further explanation could be confused.

Stef

Nicolas Passerini

Re: confused about the "image opening session"

Me too :)

On Tue, Jul 5, 2016 at 9:50 PM, stepharo <[hidden email]> wrote:

Hi

I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image.

Now I got confused because several times I prompted with this list and I do not see how I ended up having it

since I save my image and did not get crash (or idea that I lost changes).

Is it me that do not understand correctly this feature?

At the minimum it would be nice to have a little bit more explanation about what is happening.

Because I imagine new guys coming and seeing this list without any further explanation could be confused.

Stef

demarey

Re: confused about the "image opening session"

In reply to this post by stepharo

yes, what is bad now is that there is ‘no crash detector’.
If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose.
Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash.

> Le 5 juil. 2016 à 21:50, stepharo <[hidden email]> a écrit :
>
> Hi
>
> I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image.
>
> Now I got confused because several times I prompted with this list and I do not see how I ended up having it
>
> since I save my image and did not get crash (or idea that I lost changes).
>
> Is it me that do not understand correctly this feature?
>
> At the minimum it would be nice to have a little bit more explanation about what is happening.
>
> Because I imagine new guys coming and seeing this list without any further explanation could be confused.
>
> Stef
>
>

EstebanLM

Re: confused about the "image opening session"

> On 06 Jul 2016, at 09:00, Christophe Demarey <[hidden email]> wrote:
>
> yes, what is bad now is that there is ‘no crash detector’.
> If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose.
> Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash.

+100

>
>> Le 5 juil. 2016 à 21:50, stepharo <[hidden email]> a écrit :
>>
>> Hi
>>
>> I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image.
>>
>> Now I got confused because several times I prompted with this list and I do not see how I ended up having it
>>
>> since I save my image and did not get crash (or idea that I lost changes).
>>
>> Is it me that do not understand correctly this feature?
>>
>> At the minimum it would be nice to have a little bit more explanation about what is happening.
>>
>> Because I imagine new guys coming and seeing this list without any further explanation could be confused.
>>
>> Stef
>>
>>
>
>

Denis Kudriashov

Re: confused about the "image opening session"

In reply to this post by demarey

2016-07-06 9:00 GMT+02:00 Christophe Demarey <[hidden email]>:

yes, what is bad now is that there is ‘no crash detector’.
If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose.
Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash.

We could introduce special Epicea event "Image Shutdown". In this case current detector will not detect lost changes. Right now it analyses that last event is about code change.

I guess it is not difficult to do and there is existing example: "image snapshot" event.