Hey Martin,

Epicea looks really cool. I can't wait to have it in Pharo 3.0.

Some questions however:

- Can we use Epicea to recover lost changes ? I mean let's say you have an image with a lot of work inside, then it crashes before you save the image. How do you then recover lost changes with Epicea (as now we do worldMenu>tools>recover lost changes...)?

- Moreover, in the case the image has a lot of work inside and crashes but you cannot reopen it (the saved image is corrupted too), what can you do with Epicea ? Usually I take the changes file and put it in a fresh image to restore my work. Does Epicea save data into an external file too ? If not how to recover data from a corrupted image ?

Thanks for your future answers,�

Best,


2013/10/23 Martin Dias <tinchodias@gmail.com>
Hello,

This announcement is for those who develop in latest Pharo 3 and are curious about a more advanced way of recording code changes than the current ".changes" mechanism.�

In particular, it should be useful when your image crashes and you want to recover lost changes. Some of you may have seen a demo at ESUG.

Epicea is far from stable or beautiful [1], but you can try it and any feedback or collaboration would be welcome.


Download it

You can download an image from Jenkins ci build [2]. Also you can load it with:

Gofer it
� smalltalkhubUser: 'MartinDias'�
� project: 'Epicea';
� loadStable.

Use it

Record

To start recording, do:

EpLog current enable.

After that, any change you do in the image (e.g. creating a class, modifying a method) will be written in .ombu files in the current working directory. In fact, not only code changes are recorded but also other events like snapshots, test runs, Monticello loading and saving, etc.

Browse

You have two ways of browsing the recorded stuff:

To browse the current log, do:

EpLog current�browse.

To browse any .ombu file in your disk, you can simply drag&drop it into the image (from Finder in Mac).



Best regards,
Mart�n


[1]: It's needed to:
- implement export/import use case (an alternative to�.cs�files)
- rethink some concepts
- unit tests
- write more comments
- a lot more