June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] JavaConnect?

by Alexandre Bergel

Ok, I understand. I need to access some Java library within Pharo. What I will do, is probably the following: - built a simple socket transmission between Pharo and Java. Just sending string via sockets - having a Groovy interpreter running on the JVM to access my library I think it will work pretty well and with no effort. Cheers, Alexandre On 27 Jun 2011, at 12:14, Johan Brichau wrote: > Hi Alex, > > JavaConnect has never been finished for Pharo. I worked on it with the idea to also include an abstraction layer over Alien but it proved to be much more work than I thought. > > Coen is actively using and maintaining the Visualworks version. > > I really hope that I can port is someday, but right now it's just not possible for me. > > Johan > > On 26 Jun 2011, at 03:00, Alexandre Bergel wrote: > >> Hi! >> >> Does JavaConnect work with the last Pharo? I cannot install it apparently. Loading it via the configuration freezes the image. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 27, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by StÃ©phane Ducasse

>> >> >>> On 25 June 2011 22:18, Nicolas Cellier >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>> Isn't it one of the features supported by backport ? >>>> >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >>>> >>> >>> yes, sounds similar. >>> Except that i never used this feature since it is mystery to me, how it works. >>> Documentation.... >> >> it is explained in the monticello chapter of pharo by example 2 >> > > so, why you saying it's completely different? > one or another way, backport allows to cherry-pick changes (from what > i have read in link that Nicolas gave). Not from what I understood back when we wrote the chapter. But may be yes. Have a look at what we wrote. Stef

June 27, 2011

Re: [Pharo-project] Moose out of memory

by StÃ©phane Ducasse

>> > > Yes, after some voodoo spells, today i got a VM built. > > Good to know that process are really reproducable: built once using > git+config on my machine locally ==> repeating the same without > problems on hudson slave. > Except that setup is a bit different (tools, installs, paths, Windows > idiosyncrazy etc etc) and i had to fix it before everything could > start running. I'm happy :) You see I'm simple :) Stef

June 27, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by Igor Stasenko

On 27 June 2011 22:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jun 27, 2011, at 1:26 PM, Igor Stasenko wrote: > >> On 25 June 2011 22:18, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> Isn't it one of the features supported by backport ? >>> >>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >>> >> >> yes, sounds similar. >> Except that i never used this feature since it is mystery to me, how it works. >> Documentation.... > > it is explained in the monticello chapter of pharo by example 2 > so, why you saying it's completely different? one or another way, backport allows to cherry-pick changes (from what i have read in link that Nicolas gave). -- Best regards, Igor Stasenko AKA sig.

June 27, 2011

Re: [Pharo-project] Moose out of memory

by Igor Stasenko

On 27 June 2011 22:39, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jun 27, 2011, at 6:20 PM, Igor Stasenko wrote: > >> On 26 June 2011 22:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> I am happy you like Moose. >>> >>> We know that "MooseScripts createModelForConfigurationOfMoose" creates a model that is stored in a global model cache. However, the idea was to reproduce an image that is large enough to not be openable with the Windows VM. The image with three large models opens just fine on Mac. >>> >>> In the meantime, Igor produced a new version of the Windows VM that enables one to load this image. However, now the question is when these fixes will make it in the main branch. >>> >>> Igor, do you happen to have an update on this issue? >>> >> >> I will include fix into my branch. The windows slave is now working, > > Really? > > Excellllllent! After all this fight. > Yes, after some voodoo spells, today i got a VM built. Good to know that process are really reproducable: built once using git+config on my machine locally ==> repeating the same without problems on hudson slave. Except that setup is a bit different (tools, installs, paths, Windows idiosyncrazy etc etc) and i had to fix it before everything could start running. -- Best regards, Igor Stasenko AKA sig.

June 27, 2011

Re: [Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking

by Marcus Denker

>>> >>> currently it is possible to load and successfully initialize Morphic >>> with all packages present in the Core image at once. I already sent to >>> Marcus necessary scripts for Hudson. >> >> I will set it up tonight... >> https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%201.4/lastSuccessfulBuil… but something is strange: -> 25MB -> not loading error message in _report.txt attached -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 27, 2011

Re: [Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking

by StÃ©phane Ducasse

And we should have a look at hazelnut for real because now that benjmain created a path we should use it. On Jun 27, 2011, at 7:42 PM, Marcus Denker wrote: > > On Jun 27, 2011, at 7:06 PM, Pavel Krivanek wrote: > >> Hi, >> >> currently it is possible to load and successfully initialize Morphic >> with all packages present in the Core image at once. I already sent to >> Marcus necessary scripts for Hudson. > > I will set it up tonight... > >> But we still do not have >> something like MinimalMorphic image. > > > We will do some serious Morphic cleanup over the Summer... > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

June 27, 2011

Re: [Pharo-project] Moose out of memory

by StÃ©phane Ducasse

On Jun 27, 2011, at 6:20 PM, Igor Stasenko wrote: > On 26 June 2011 22:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> I am happy you like Moose. >> >> We know that "MooseScripts createModelForConfigurationOfMoose" creates a model that is stored in a global model cache. However, the idea was to reproduce an image that is large enough to not be openable with the Windows VM. The image with three large models opens just fine on Mac. >> >> In the meantime, Igor produced a new version of the Windows VM that enables one to load this image. However, now the question is when these fixes will make it in the main branch. >> >> Igor, do you happen to have an update on this issue? >> > > I will include fix into my branch. The windows slave is now working, Really? Excellllllent! After all this fight. > so there is a little to do.. push the changes and update configs. > > As for, whether this fix will be integrated into main branch, you > asking a wrong person. > >> Cheers, >> Doru >> > > > -- > Best regards, > Igor Stasenko AKA sig. >

June 27, 2011

Re: [Pharo-project] Moose out of memory

by Alain Rastoul

Thanks I missed the point about the moose error. Good news for the vm fixes, I missed Igor posts too :( Cheers Alain "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit dans le message de news: 15309023-B13B-42A2-97A4-CED5D0FEFF56(a)tudorgirba.com... Hi, I am happy you like Moose. We know that "MooseScripts createModelForConfigurationOfMoose" creates a model that is stored in a global model cache. However, the idea was to reproduce an image that is large enough to not be openable with the Windows VM. The image with three large models opens just fine on Mac. In the meantime, Igor produced a new version of the Windows VM that enables one to load this image. However, now the question is when these fixes will make it in the main branch. Igor, do you happen to have an update on this issue? Cheers, Doru On 26 Jun 2011, at 18:43, Alain Rastoul wrote: > Hi, > There was a previous message in the list about an out of memory problem > with > Moose when running > 3 times MooseScripts createModelForConfigurationOfMoose > I downloaded moose suite 4.5 (Pharo 1.3) and played a bit with it reading > the moose book (nice). > > IMHO although something is perhaps not completly clear in the vm in memory > allocation and/or ui process and/or low space watcher (I tryed to debug > the > vm but did not succeed), here the problem seems to be in the Moose model. > I suspect that the problem is just that the cache keeps a reference to > the > Moose model each time the script is run, see at the end of > MooseScripts>>createModelForConfigurationOfMoose the model is added to a > cache ((MooseModel root => MooseGroupRuntimeStorage>> byType) and takes > abut > 130M of memory each time. > clearing the Moose cache resolve the problem. > MooseModel allInstancesDo:[ :m | m remove ] seems to be working here, > except > that there is an exception for the root model (I don't know Moose, it may > not be the best command). > Perhaps the moose model should not be added by type but overriden each > time > (beeing identified by a "name" ?). > > PS: Moose is cool :) > > Cheers > Alain > > > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

June 27, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by StÃ©phane Ducasse

On Jun 27, 2011, at 1:26 PM, Igor Stasenko wrote: > On 25 June 2011 22:18, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Isn't it one of the features supported by backport ? >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >> > > yes, sounds similar. > Except that i never used this feature since it is mystery to me, how it works. > Documentation.... it is explained in the monticello chapter of pharo by example 2 > >> Nicolas >> >> 2011/6/23 Igor Stasenko <siguctua(a)gmail.com>: >>> On 22 June 2011 23:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>>>> Perhaps the "non-applicable" could be streamlined. >>>>>>> I.e., "keep current version" = not applicable. >>>>>>> >>>>>> yes, could be.. >>>>>> but that logic are only for conflics.. and i didn't wanted to mess >>>>>> with it because its a lot more work. >>>>> >>>>> btw, Stephane, this is a good topic for dealing with it on friday, if >>>>> you don't have anything else in mind. >>>> >>>> ok >>>> did you run MC tests? >>>> I htink that we should invest more in running tests. >>>> >>> >>> well, the changes i made are not intrusive, i mean it will work as before >>> unless user plays with this flag using UI. >>> So, MC will behave exactly as before and there is no problem from that side. >>> >>>> >>>> >>>>>> Because strangely , instead of using field to indicate a conflict (in >>>>>> MCPatchOperation record) it does something strange and overly >>>>>> complicated >>>>>> (MCConflict). >>>>>> >>>>>> So, then each entry could contain >>>>>> 'isApplicable' >>>>>> and >>>>>> 'isConflicting' >>>>>> >>>>>> and once user resolves the conflict, the isConflicting should be set to false, >>>>>> while isApplicable are uniformly to indicate which version to use >>>>>> (current or incoming one), when merging. >>>>>> >>>>>> >>>>>>> No need for the extra menu item then. >>>>>>> >>>>>>> Regards, Gary >>>>>>> >>>>>>> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >>>>>>> To: <Pharo-project(a)lists.gforge.inria.fr> >>>>>>> Sent: Wednesday, June 22, 2011 3:40 PM >>>>>>> Subject: Re: [Pharo-project] Merge tool. No way to cherry pick the changes? >>>>>>> >>>>>>> >>>>>>>> Here the code >>>>>>>> http://code.google.com/p/pharo/issues/detail?id=4439 >>>>>>>> >>>>>>>> please tell me if it works for you. >>>>>>>> I tested on simple merge and it works fine (the changes which i marked >>>>>>>> as not applicable are not loaded). >>>>>>>> >>>>>>>> -- >>>>>>>> Best regards, >>>>>>>> Igor Stasenko AKA sig. >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Igor Stasenko AKA sig. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

June 27, 2011