Hi Sven,

thanks for the answers; especially the article was very informative. I didn't even think of using Announcements, but seeing it in action is really cool!

Peter

On Sun, Apr 5, 2015 at 8:30 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

Hi Peter,

I would call this object logging, plain and simple.

Some of us, myself included, believe this is the way forward.

You could have a look at how Zinc does logging (ZnLogEvent):

��https://www.youtube.com/watch?v=rIBbeMdFCys
��https://www.youtube.com/watch?v=gaUxPNq6_7c

This article might also help:

��https://medium.com/concerning-pharo/lampsort-revisited-visualised-6652055ef858

All in all, it is not too much effort to generate log event objects, and they can used in many different ways. Using Announcement makes this quite practical.

HTH,

Sven

> On 05 Apr 2015, at 20:16, Peter Uhn��k <i.uhnak@gmail.com> wrote:
>
> Hi,
>
> this may be a bit tall order and I am not sure if possible,
> however I would like to know the state of objects at certain points.
>
> Currently what I would do is something like
> self log: 'anObject someProperty:'; logCr: anObject someProperty.
>
> however this is not very practical.
>
> So I would like something like
> self fronzenLog: anObject
>
> and then I could inspect the logger and see the state of the whole objects.
>
> Using debugger and stepping through it is not really practical because I need to observe several possible objects that are in this function at very different times.
>
> Is this possible? Is there a better/somewhat better way to do something like this?
>
> Any pointers appreciated.
>
> Peter