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

[Pharo-project] [update 1.4] #14016

by Marcus Denker

Issue 4456: 1.4: relead dirty package http://code.google.com/p/pharo/issues/detail?id=4456 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 27, 2011

Re: [Pharo-project] JavaConnect?

by Johan Brichau

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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

June 27, 2011

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

by Tudor Girba

Great work! Doru On 27 Jun 2011, at 11:30, Marcus Denker wrote: > > https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%201.4/ > > There is now a Pharo-Kernel-Gofer (3MB) that has networking and Gofer loaded back into the Kernel. > Thanks Pavel! This is starting to get really interesting... > > TODO: > -> Tests for Kernel > -> reload everything to re-create Pharo 1.4 > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

June 27, 2011

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

by Marcus Denker

https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%201.4/ There is now a Pharo-Kernel-Gofer (3MB) that has networking and Gofer loaded back into the Kernel. Thanks Pavel! This is starting to get really interesting... TODO: -> Tests for Kernel -> reload everything to re-create Pharo 1.4 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 27, 2011

Re: [Pharo-project] UIManager>>chooseFileName* flavour to get full path?

by Gary Chambers

There is currently MorphicUIManager>>chooseFullFileNameMatching:label: Feel free to add in ones that take a path/preview if necessary. Regards, Gary ----- Original Message ----- From: Guillermo Polito To: Pharo Development Sent: Saturday, June 25, 2011 9:04 PM Subject: [Pharo-project] UIManager>>chooseFileName* flavour to get full path? Hi! I was wondering why UITheme>>chooseFileNameIn: title: patterns: path: preview: and UITheme>>chooseFileNameIn: title: extensions: path: preview: do fd := FileDialogWindow basicNew previewType: preview; initialize; title: title; answerFileName. And actually there is no variant using answerPathName what is a bit more useful because it answers the entire path to the selected file... Thanks! Guille

June 27, 2011

[Pharo-project] [TODO] 1.3

by Marcus Denker

CORE ====== -> Core is green and no issue is tagged 1.3 FULL ====== FULL has three open reports, all of which are solved but not integrated. Issue 4390: OCompletion does not respect #enabled setting; it has no "off switch" Issue 4394: GoferApiTest >> testRepositoryErrors fails in Full but not in Core Issue 4447: Appl-k shortcut not working in Pharo 1.2.2 image http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.3-DevImage Any help to actually get them integrated is very welcome. All of them are not real show stoppers, I suggest we release end of the week nevertheless. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 27, 2011

Re: [Pharo-project] Moose out of memory

by Tudor Girba

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 26, 2011

Re: [Pharo-project] Moose out of memory

by StÃ©phane Ducasse

Alain igor fixed a problem in the windows VM. Now I do not know if this is available. Stef TX for the fix I will pass it to moosers On Jun 26, 2011, at 6:43 PM, 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 > > > >

June 26, 2011

[Pharo-project] Moose out of memory

by Alain Rastoul

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

June 26, 2011

[Pharo-project] [update 1.4] #14015

by Marcus Denker

14015 ----- Issue 4455: Subclasses of Obsolete classes to be removed http://code.google.com/p/pharo/issues/detail?id=4455 Issue 4454: ScriptLoader: remove 1.3 update and script methods. http://code.google.com/p/pharo/issues/detail?id=4454 Issue 4452: Build of 1.3 full is broken http://code.google.com/p/pharo/issues/detail?id=4452 TODO: there is now one package dirty. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 26, 2011