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

[Pharo-project] Two problems yesterday

by Bill Schwab

Hello all, After a few days of getting mostly nothing from an evolving Seaside+Apache setup, I got it running. A lot suddenly happened on two machines, and there is no telling what I might have done to cause trouble on my own. Anyway, two things deserve mention. Sorry to throw these at you, but I think I can explain one of them. The first problem might have been continuations in action. I use streams often and will somewhat frequently read files as I process them, using #ensure: to close them. It ends up looking like in := FileStream read:fileName text:true. [ "code that might raise an error" ] ensure:[ in close. ]. Despite this construction, I ended up with errors trying to open a file, and ended up closing and reopening Pharo to regain access to it. In Dolphin, that was an almost certain sign that I had not properly ensured the closing of a stream. Based on recent discussions of #terminate, I began to suspect that closing the debugger thwarted the ensure block. However, I note that [ nil halt. ] ensure:[ Transcript show:'Did it'. ]. has been doing pretty much what I expect it to do: close the debugger and the block executes. So, I suspect what in fact happened is that a continuation caused me to re-open the file before it was closed. I am starting to like Seaside, but I wish it were based on threads and synchronization objects, but that's another topic. Whether or #ensure: behaves correctly in response to #terminate is something I need to check. For now, I will probably read the file into memory and close it before Seaside gets involved. The second thing that happened was I ended up with an image in which the system browser was out of synch. Clicking on the name of one method would show source for another. When I saw that, I assumed the change log had been clobbered, but not knowing what else to do, I exited w/o saving and recreated what I had lost in the process. The recovery was probably not what you would think. I had been coding on "the other machine" (win2k3 image on a blade via remote desktop), and was trying to integrate a few things into my "real" image (on my local machine) that I did to get the Seaside app working. Somewhere in that process, the browser mess started. I did something along the lines of firing off a new browser (probably from a method I was editing) to add a new method. I have noted that Pharo gets a little upset, (correctly) warning about possible changes elsewhere. The simple explanation is that this time, it "mis-filed" what I did in that new browser. Specifically, I (most likely) overwrote everything and accepted the source of the method. Sorry for the lengthy and un-confirmed guesswork masquerading as a bug report. I'm not sure I _want_ to reproduce it :( Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

Oct. 8, 2008

[Pharo-project] Fwd: [squeak-dev] [ANN] Dependency Browser

by StÃ©phane Ducasse

Begin forwarded message: > From: "HernÃ¡n Morales Durand" <hernan.morales(a)gmail.com> > Date: October 8, 2008 8:17:40 PM CEDT > To: "The general-purpose Squeak developers list" <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] [ANN] Dependency Browser > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Dear Squeakers, > > If you ever wondered how to observe dependencies between > packages in the image, now you can use this new Dependency Browser. > Instructions for using it are in the following pages: > > Castellano : http://cs.hernanmorales.com.ar/DBrowser-es.php > FranÃ§ais : http://cs.hernanmorales.com.ar/DBrowser-fr.php > English : http://cs.hernanmorales.com.ar/DBrowser-en.php > > Regards. > > HernÃ¡n > >

Oct. 8, 2008

Re: [Pharo-project] how to register a tool in the open menu?

by StÃ©phane Ducasse

Damien could you add the MethodFinder to the tools you add to the oneClick image. I added the registration mechanism. I will check the code of the model. Stef On Oct 8, 2008, at 6:52 PM, Damien Cassou wrote: > On Wed, Oct 8, 2008 at 6:46 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> does one of you know how when I load a package I can get an entry >> in the >> open... menu? > > SHWorkspace class>>initialize > TheWorldMenu registerOpenCommand: {'Shout Workspace'. {self. #open}} > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

Re: [Pharo-project] how to register a tool in the open menu?

by StÃ©phane Ducasse

Thanks! Stef On Oct 8, 2008, at 6:52 PM, Gary Chambers wrote: > You'll need to write a class-side initialize method in one of the > classes that gets loaded... > > initialize > "Initialize the application." > > (TheWorldMenu respondsTo: #registerOpenCommand:) ifTrue: [ > TheWorldMenu registerOpenCommand: > { 'Report Builder' . { self . #openDefault }. 'Report bulding > tool' }] > > And, an unload is usually wise too... > > unload > "Remove the world menu open menu entry." > > (TheWorldMenu respondsTo: #unregisterOpenCommand:) > ifTrue: [TheWorldMenu unregisterOpenCommand: 'Report Builder'] > > Regards, Gary. > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr > > > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, October 08, 2008 5:46 PM > Subject: [Pharo-project] how to register a tool in the open menu? > > >> Hi guys >> >> does one of you know how when I load a package I can get an entry >> in the open... menu? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 8, 2008

Re: [Pharo-project] MethodFinder

by StÃ©phane Ducasse

I'm too ignorant for that but if you want to try be my guest. Stf On Oct 8, 2008, at 6:44 PM, Damien Cassou wrote: > On Wed, Oct 8, 2008 at 6:32 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I created a new package MethodFinder and published it to Pharo. >> I really like this tool. So I will give a try to clean it. > > You may want to use OB to implement the GUI. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

[Pharo-project] 10089-10090

by StÃ©phane Ducasse

Hi 10089 fixes the bookMorph 10090 introduces a nice features added to Sunit - the possibility to store the results of tests run and to compare the results This way you can get a package and evaluate if when you run them you really broke something or improved the tests. Now the browser could take avantage of that information. Stef

Oct. 8, 2008

Re: [Pharo-project] how to register a tool in the open menu?

by Damien Cassou

On Wed, Oct 8, 2008 at 6:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > does one of you know how when I load a package I can get an entry in the > open... menu? SHWorkspace class>>initialize TheWorldMenu registerOpenCommand: {'Shout Workspace'. {self. #open}} -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 8, 2008

Re: [Pharo-project] how to register a tool in the open menu?

by Gary Chambers

You'll need to write a class-side initialize method in one of the classes that gets loaded... initialize "Initialize the application." (TheWorldMenu respondsTo: #registerOpenCommand:) ifTrue: [ TheWorldMenu registerOpenCommand: { 'Report Builder' . { self . #openDefault }. 'Report bulding tool' }] And, an unload is usually wise too... unload "Remove the world menu open menu entry." (TheWorldMenu respondsTo: #unregisterOpenCommand:) ifTrue: [TheWorldMenu unregisterOpenCommand: 'Report Builder'] Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, October 08, 2008 5:46 PM Subject: [Pharo-project] how to register a tool in the open menu? > Hi guys > > does one of you know how when I load a package I can get an entry in the > open... menu? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

[Pharo-project] how to register a tool in the open menu?

by StÃ©phane Ducasse

Hi guys does one of you know how when I load a package I can get an entry in the open... menu? Stef

Oct. 8, 2008

Re: [Pharo-project] MethodFinder

by Damien Cassou

On Wed, Oct 8, 2008 at 6:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I created a new package MethodFinder and published it to Pharo. > I really like this tool. So I will give a try to clean it. You may want to use OB to implement the GUI. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 8, 2008