October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fwd: Epicea

by Martin Dias

On Wed, Oct 23, 2013 at 4:10 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > Hey Martin, > > Epicea looks really cool. I can't wait to have it in Pharo 3.0. > > :p thanks! a bit early to say but why not in the future. > 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...)? > Yes, it's the main use case. For the moment, to browse you have to drag the .ombu file and drop it into the image. You will recognize the .ombu file because they're prefixed as your .image file name. When the logging is enabled, each time you open an image (i.e. a session starts), a new file is created but a new suffix. > > - 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 ? > Yes, the same as for the previous question. > > Thanks for your future answers, > > Best, > > > 2013/10/23 Martin Dias <tinchodias(a)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 >> >> [2]: >> https://ci.inria.fr/pharo-contribution/job/Epicea/PHARO=30,VERSION=stable,V… >> >> >> >> >

Oct. 23, 2013

Re: [Pharo-dev] Issue 4255 ?

by Sven Van Caekenberghe

On 23 Oct 2013, at 16:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 23 Oct 2013, at 16:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 23 Oct 2013, at 16:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> I am confused, I was under the impression that these would already have been integrated (I was waiting for the summary mails): >>> >>> https://pharo.fogbugz.com/f/cases/4255/Deprecate-MIMEType >>> https://pharo.fogbugz.com/f/cases/11964/Update-Zinc-Resource-Meta-Core >>> >>> The slice was written against #30512 after loading Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 - I hope it still works. >>> >>> Both issues were marked âFix to includeââ¦ >>> >>> >> >> Yes, this means âthe integrator should integrate themâ. >> >> I did not yet because keeping the name Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 in the image means manual work >> (creating a .cs, adding it to the update stream, doing update, later fixing the out-of-sync Scriptloaderâ¦) >> >> Maybe I will just merge it the normal wayâ¦ much easier. >> >> > > I integrated that in 519, now in testing stage Thx! > Marcus

Oct. 23, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by Camille Teruel

On 23 oct. 2013, at 16:29, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > did you push ? Yes > I do not see any change :( I just enclosed the script. That's how I interpreted the request for formatting. > Ben > > On 23 Oct 2013, at 16:24, Camille Teruel <camille.teruel(a)gmail.com> wrote: > >> >> On 23 oct. 2013, at 15:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> On 2013-10-23, at 15:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> On 2013-10-23, at 13:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> On Oct 22, 2013, at 9:34 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> >>>>>> I'll remove the script again, this is silly duplication that is going to be >>>>>> outdated very quickly. It points already to the jenkins job, this is where >>>>>> everything happens. >>>>> >>>>> so I will readd it. >>>>> Camillo can you respect people that do not think like you? >>>> >>>> well respect at least markdown and make it look properly formatted... >>> >>> Can you PLEASE take some minutes to make this look properly? >>> >>> https://github.com/pharo-project/pharo-update/blob/30/README.md >> >> done >> >> >

Oct. 23, 2013

Re: [Pharo-dev] Issue 4255 ?

by Marcus Denker

On 23 Oct 2013, at 16:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 23 Oct 2013, at 16:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> I am confused, I was under the impression that these would already have been integrated (I was waiting for the summary mails): >> >> https://pharo.fogbugz.com/f/cases/4255/Deprecate-MIMEType >> https://pharo.fogbugz.com/f/cases/11964/Update-Zinc-Resource-Meta-Core >> >> The slice was written against #30512 after loading Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 - I hope it still works. >> >> Both issues were marked âFix to includeââ¦ >> >> > > Yes, this means âthe integrator should integrate themâ. > > I did not yet because keeping the name Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 in the image means manual work > (creating a .cs, adding it to the update stream, doing update, later fixing the out-of-sync Scriptloaderâ¦) > > Maybe I will just merge it the normal wayâ¦ much easier. > > I integrated that in 519, now in testing stage Marcus

Oct. 23, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by Benjamin

did you push ? I do not see any change :( Ben On 23 Oct 2013, at 16:24, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 23 oct. 2013, at 15:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> On 2013-10-23, at 15:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> On 2013-10-23, at 13:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> On Oct 22, 2013, at 9:34 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>>> I'll remove the script again, this is silly duplication that is going to be >>>>> outdated very quickly. It points already to the jenkins job, this is where >>>>> everything happens. >>>> >>>> so I will readd it. >>>> Camillo can you respect people that do not think like you? >>> >>> well respect at least markdown and make it look properly formatted... >> >> Can you PLEASE take some minutes to make this look properly? >> >> https://github.com/pharo-project/pharo-update/blob/30/README.md > > done > >

Oct. 23, 2013

Re: [Pharo-dev] Issue 4255 ?

by Marcus Denker

On 23 Oct 2013, at 16:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I am confused, I was under the impression that these would already have been integrated (I was waiting for the summary mails): > > https://pharo.fogbugz.com/f/cases/4255/Deprecate-MIMEType > https://pharo.fogbugz.com/f/cases/11964/Update-Zinc-Resource-Meta-Core > > The slice was written against #30512 after loading Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 - I hope it still works. > > Both issues were marked âFix to includeââ¦ > > Yes, this means âthe integrator should integrate themâ. I did not yet because keeping the name Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 in the image means manual work (creating a .cs, adding it to the update stream, doing update, later fixing the out-of-sync Scriptloaderâ¦) Maybe I will just merge it the normal wayâ¦ much easier. Marcus

Oct. 23, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by Camille Teruel

On 23 oct. 2013, at 15:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-10-23, at 15:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> On 2013-10-23, at 13:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> On Oct 22, 2013, at 9:34 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> I'll remove the script again, this is silly duplication that is going to be >>>> outdated very quickly. It points already to the jenkins job, this is where >>>> everything happens. >>> >>> so I will readd it. >>> Camillo can you respect people that do not think like you? >> >> well respect at least markdown and make it look properly formatted... > > Can you PLEASE take some minutes to make this look properly? > > https://github.com/pharo-project/pharo-update/blob/30/README.md done

Oct. 23, 2013

Issue 4255 ?

by Sven Van Caekenberghe

I am confused, I was under the impression that these would already have been integrated (I was waiting for the summary mails): https://pharo.fogbugz.com/f/cases/4255/Deprecate-MIMEType https://pharo.fogbugz.com/f/cases/11964/Update-Zinc-Resource-Meta-Core The slice was written against #30512 after loading Zinc-Resource-Meta-Core.SvenVanCaekenberghe.20 - I hope it still works. Both issues were marked âFix to includeââ¦ Sven

Oct. 23, 2013

Re: [Pharo-dev] Fwd: Epicea

by Benjamin

It seams data are written in a .ombu file "will be written in .ombu files " So I guess the work remain the same here :) Ben On 23 Oct 2013, at 16:10, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 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(a)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 > > [2]: https://ci.inria.fr/pharo-contribution/job/Epicea/PHARO=30,VERSION=stable,V… > > > >

Oct. 23, 2013

Re: [Pharo-dev] Fwd: Epicea

by ClÃ©ment Bera

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(a)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 > > [2]: > https://ci.inria.fr/pharo-contribution/job/Epicea/PHARO=30,VERSION=stable,V… > > > >

Oct. 23, 2013