- Pharo-dev - lists.pharo.org

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

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

by Camillo Bruni

On 2013-10-23, at 13:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > On Oct 23, 2013, at 10:52 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> On 2013-10-22, at 10:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> For retracting files you need access to files.pharo.org. >>>> >>>> This is what should be written in the readme. >>> >>> BTW have you tried that you actually have access to the machine? >>> Because I remember that it didn't work for you nor Esteban... >> >> >> So stef, did you check that you can actually edit the file? > > I cannot access it but I least I know that I should not look for it. > And next time if there is a problem I just stop integrated and continue hacking on my cool stuff and look smart. Why can't you access it? What do you want instead? How do we avoid this situation in the future? (happened already before a couple of times)

Oct. 23, 2013

Re: [Pharo-dev] VM for Athens Graphics

by Henrik Johansen

On Oct 23, 2013, at 1:52 , StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Oct 22, 2013, at 7:37 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> For the ipad , best would be to implement a quartz backend for athens. >> As a temporary solution we could try to compile cairo library for it, but i am not expert in iOS >> to say if it can be done without much fuss. >> Also, since iOS is famous for banning any applications which using generated code, >> that means it should be done by writing a VM plugin and then adopting new primitives to >> work with Athens API. > > Igor it also means that we should find a way to get nativeboost wroking on iPad (probably by generating a "DLL" from NB). >> There's another reason why Igor said a plugin backend would be the easier way, if you were to use NB, you'd also first need to implement AsmJit for ARM, as well as an ARM version of the entire NB FFI machinery , which would be large efforts in and of themselves. Cheers, Henry

Oct. 23, 2013

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

by Camillo Bruni

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

Oct. 23, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30518 Home: https://github.com/pharo-project/pharo-core

Oct. 23, 2013

[pharo-project/pharo-core] 302f63: 30518

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 302f637c373afaccdd766b66a664e248469e3cd8 https://github.com/pharo-project/pharo-core/commit/302f637c373afaccdd766b66… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-23 (Wed, 23 Oct 2013) Changed paths: R Nautilus.package/Nautilus.class/class/accessing/groupsManager.st R Nautilus.package/Nautilus.class/class/browser compatibility/addGroupForClasses_named_.st R Nautilus.package/Nautilus.class/class/browser compatibility/addGroupForPackage_.st M Nautilus.package/Nautilus.class/class/cleanup/cleanUp.st R Nautilus.package/Nautilus.class/class/groups/importAGroup_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script173.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30518.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SmalltalkImage.class/instance/housekeeping/fixObsoleteReferences.st M Tests.package/ReleaseTest.class/instance/testing/testObsoleteClasses.st M Tools.package/ImageCleaner.class/instance/cleaning/cleanUpMethods.st R Tools.package/ImageCleaner.class/instance/cleaning/fixObsoleteReferences.st Log Message: ----------- 30518 11976 clean up class side #groupsManager method Nautilus https://pharo.fogbugz.com/f/cases/11976 11977 #fixObsoleteReferences should call #flushCache on all changes CMs https://pharo.fogbugz.com/f/cases/11977 http://files.pharo.org/image/30/30518.zip

Oct. 23, 2013