- Pharo-dev - lists.pharo.org

[Pharo-project] kill -9 MyClass allInstances
by laurent laffont July 1, 2010

July 1, 2010

Hi, It seems I've messed up something on Autotest unit tests and I have an Autotest instance running, I don't know where it's referenced. I've tried Smalltalk>>#garbageCollect and #garbageCollectMost .... still here. How can I find why an instance is not garbage collected ? How to kill it ? Cheers Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

4 4

[Pharo-project] squeaksource is down (again ...)
by Torsten Bergmann July 1, 2010

July 1, 2010

>What could be done is moving to an up to date image/vm but this is a bit >of work. Would you be able to at least make the image available somewhere so one knows about the loaded packages and applied patches. Maybe someone has a minute ... Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

6 6

[Pharo-project] Setting new world in 1.1
by Denis Kudriashov July 1, 2010

July 1, 2010

How I can install new World in Pharo 1.1? In pharo 1.0 I do : newWorld beWorldForProject: nil. But #beWorldForProject: absent in 1.1

2 2

Re: [Pharo-project] CLFramework and Pharo
by Rob Rothwell June 30, 2010

June 30, 2010

Message: 5 > Date: Wed, 30 Jun 2010 23:50:24 +0200 > From: St?phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] CLFramework and Pharo > To: Pharo-project(a)lists.gforge.inria.fr > Message-ID: <77E6AD68-79FF-4590-9FB6-7B2E1C961001(a)inria.fr> > Content-Type: text/plain; charset=iso-8859-1 > > But you rely on XML. > Second the builder (ie generating the XML) is not the problem as far as I > know. > but more how to assemble the widget and make sure that the layout > are kept or specified. > > Then how using an external tools can make sure that this tool got well the > way layoutMorph > and other works? > > Stef > > > My knowledge is limited, but XML seems more portable than code Smalltalk. > > I do not understand why we want portability. > Please note that the VWspec are as portable as XML between Smalltalk they > are just arrays ( > probably we would get a problem for the UI.Node notation but this is not > the problem. > Another place to see such an example is Smalltalk/X. I think they conformed to the VW Specs as well... Rob

1 0

[Pharo-project] [update 1.2] #12026
by StÃ©phane Ducasse June 30, 2010

June 30, 2010

12026 ----- - Issue 2069: Be able to load DummyUIManager in a Pharo image. Part two

1 0

[Pharo-project] [update 1.2] #12024 (new version)
by StÃ©phane Ducasse June 30, 2010

June 30, 2010

12024 ----- - Issue 2105: Packages remodularization and now without obsolete classes Stef (thanks Pavel)

3 4

[Pharo-project] Changing color/fillStyle by morph halo menu in 1.1rc2
by Denis Kudriashov June 30, 2010

June 30, 2010

I try last Pharo 1.1 rc2 10.06.10. I found that tool for changing color by user is changed. ColorPickerMorph is removed. Now I can't dynamically change color by mouse and see my changes immediately. Now I must select color in new tool, press ok button. And after that tool close and I must open it again if I dont like my changes. It is bad behavior compare with pharo 1.0/squeak. But I really like new color picker morph. New tool is ColorSelectorDialogWindow. How I can hookup It for tracking color selection? Maybe I must add some event triggering in #basicSelectedColor: method. But I see many #changed: sends in #basicSelectedColor: method. And maybe I already can implement some dependent class for needed stuff. What you think?

2 7

June 30, 2010

12025 ----- - Issue 2599: better extract parameter - Issue 2604: a script as argument squeak mysqueak.image file.st squeak mysqueak.image scripts/file.st squeak mysqueak.image ../../svn/scripts/file.st Stef and Hilaire happily hacking to relax :)

1 0

June 30, 2010

Pavel can you have a look to see if everything is ok? 12024 ----- - Issue 2105: Packages remodularization

2 10

June 30, 2010

12025 ----- - Issue 2105: Packages remodularization - Post actions Pavel I just did the DecompilerTests compileAll. LanguageEnvironment compileAll. FileServices cleanUp. CodeHolder compileAll. CompiledMethod compileAll. Debugger compileAll. Object compileAll. MCMczInstallerTest compileAll. MCInitializationTest compileAll.

1 0