- Pharo-dev - lists.pharo.org

[Pharo-project] while chasing some block arg assignment

by StÃ©phane Ducasse

I did ImageSegment compileAll and I got a error in SyntaxError apparently it may happen that the category is nil I'm the train so cannot add to the bugtracker. If someone can it would be great. Stef

March 31, 2009

[Pharo-project] SUniGUI profiled DNU

by StÃ©phane Ducasse

lukas how to you invoke the coverage for a test? I tried with profiled and I got a DNU. Stef From: zork To: Pharo-project(a)lists.gforge.inria.fr Subject: [BUG]UndefinedObject(Object)>>doesNotUnderstand: #terminate here insert explanation of what you were doing, suspect changes you've made and so forth. 31 March 2009 8:36:50 pm VM: Mac OS - a SmalltalkImage Image: Pharo0.1 [Latest update: #10259] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/ Pharo Trusted Dir /foobar/tooBar/forSqueak/bogus Untrusted Dir /Users/ducasse/Library/Preferences/Squeak/Internet/My Squeak UndefinedObject(Object)>>doesNotUnderstand: #terminate Receiver: nil Arguments and temporary variables: aMessage: terminate exception: MessageNotUnderstood: UndefinedObject>>terminate resumeValue: nil Receiver's instance variables: nil [] in MessageTally>>spyEvery:on: {[SmalltalkImage current getVMParameters keysAndValuesDo: [:idx :gcVal | gc...]} Arguments and temporary variables: millisecs: 1 aBlock: [] in TestRunner>>runProfiled {[self runAll]} myDelay: a Delay startTime: 311391 time0: 307811 idx: 40 gcVal: 4 BlockContext>>ensure: Receiver: [] in TestRunner>>runProfiled {[self runAll]} Arguments and temporary variables: aBlock: nil returnValue: a TestRunner b: [] in MessageTally>>spyEvery:on: {[SmalltalkImage current getVMParameters ...etc... Receiver's instance variables: sender: nil pc: nil stackp: 0 nargs: 0 startpc: 31 home: TestRunner>>runProfiled MessageTally>>spyEvery:on: Receiver: TestRunner >> runProfiled Arguments and temporary variables: millisecs: 1 aBlock: [] in TestRunner>>runProfiled {[self runAll]} myDelay: a Delay startTime: 311391 time0: 307811 idx: 40 gcVal: 4 Receiver's instance variables: class: TestRunner method: a CompiledMethod (1657) tally: 3568 receivers: an Array(TestRunner >> runAll SystemProgressMorph >> label:min:max: ...etc... senders: nil time: nil gcStats: #(3672228 3627200 4333372 -1629 0 0 0 0 2511 917 47 0 0 0 0 0 0 0 0 0 ...etc... maxClassNameSize: 30 maxClassPlusSelectorSize: 60 maxTabs: 60 --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #terminate [] in MessageTally>>spyEvery:on: {[SmalltalkImage current getVMParameters keysAndValuesDo: [:idx :gcVal | gc...]} BlockContext>>ensure: MessageTally>>spyEvery:on: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MessageTally class>>spyOn: TestRunner>>runProfiled PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: {[:m | (m containsPoint: evt cursorPoint) ifTrue: [m performAction]]} Array(SequenceableCollection)>>do: PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: PluggableButtonMorphPlus>>mouseUp: PluggableButtonMorphPlus(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorphPlus(Morph)>>handleEvent: PluggableButtonMorphPlus(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h processEvents. ActiveHand := nil]} Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor yield. false] whileFalse. nil]} [] in BlockContext>>newProcess {[self value. Processor terminateActive]}

March 31, 2009

Re: [Pharo-project] [ANN] #10262cl

by Michael Roberts

+1 adapt process to suit our needs +1 document on wiki if possible Cheers mike On 3/31/09, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I think we can do it manually, yes. > > But it would be good to have a detailed description of the manual > steps so that we (or someone else) is able to reproduce it at a later > point in time. > > Adrian > > On Mar 31, 2009, at 16:52 , Marcus Denker wrote: > >> Hi, >> >> So this is not done as an update... reason: much simpler. >> doing the closure conversation is a bit manual, e.g. closing all >> windows, >> doing some other stuff, then save, restart, cleanup changeset... then >> re-saving all the dirty packages. >> >> I would *a lot* of work to do that with the update-stream. >> >> The question is: can we live without? >> >> We could add a changeset that just pops up a window that says: end-of- >> line, please get the hand-build image. >> >> Marcus >> >> >> On 31.03.2009, at 16:15, Marcus Denker wrote: >> >>> Hi, >>> >>> I have merged the closure changed in the 1062 image (manually). >>> >>> We now can continue with this image to provide updates using the >>> update stream: >>> >>> http://gforge.inria.fr/frs/download.php/20098/ >>> Pharo0.1Core-10262cl.zip >>> >>> >>> Changes: >>> -> Closure changes merged. >>> -> BlockClosurePharo.1.cs >>> -> FixDebugger.1.cs >>> -> TraitDescription-closure support.st >>> -> BlockContextTestFix.1.cs >>> -> ArrayLiteralTestFix.1.cs >>> >>> >>> -- >>> Marcus Denker -- denker(a)acm.org >>> http://www.marcusdenker.de >>> >> >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >> >> >> _______________________________________________ >> 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 >

March 31, 2009

Re: [Pharo-project] Plugins overview

by Michael Rueger

Torsten Bergmann wrote: > it would be nice to have a page on the pharo-project website > with an overview and downloadable precompiled versions of all the > plugins available. > > > Name ! Win32 ! Mac ! Linux ! > ------------------------------------------------------- > OSProcess ! OSProcessPlugin.dll ! ... ! ... ! > SqueakFFIPrims ! SqueakFFIPrims.dll ! ! ! > ... Here is a start, although still largely incomplete and no download links yet: http://code.google.com/p/pharo/wiki/VMPluginOverview Input, links to pre-compiled and missing plugins welcome! Michael

March 31, 2009

[Pharo-project] Seaside hosting alternatives

by Mariano Martinez Peck

Hi folks, I was wondering which are the seaside hosting alternatives in the market. 1) free ? I only know seasidehosting.st but this, only support squeak 3.9.1. I would love to use pharo. Is any other free ? 2) pharo support ? any ? is on the plans of pharo getting a free pharo seaside hosting ? 3) For non commercial but with needs of several pictures o commercial application, any alternatives ? how much ? how can I contact them. I tried to google a bit but didn't get any real results. I think hosting is a very very important think for most of us. Is one on the think I put into account when deciding the technology to use. Thanks a lot in advance. Mariano

March 31, 2009

Re: [Pharo-project] [ANN] #10262cl

by Adrian Lienhard

I think we can do it manually, yes. But it would be good to have a detailed description of the manual steps so that we (or someone else) is able to reproduce it at a later point in time. Adrian On Mar 31, 2009, at 16:52 , Marcus Denker wrote: > Hi, > > So this is not done as an update... reason: much simpler. > doing the closure conversation is a bit manual, e.g. closing all > windows, > doing some other stuff, then save, restart, cleanup changeset... then > re-saving all the dirty packages. > > I would *a lot* of work to do that with the update-stream. > > The question is: can we live without? > > We could add a changeset that just pops up a window that says: end-of- > line, please get the hand-build image. > > Marcus > > > On 31.03.2009, at 16:15, Marcus Denker wrote: > >> Hi, >> >> I have merged the closure changed in the 1062 image (manually). >> >> We now can continue with this image to provide updates using the >> update stream: >> >> http://gforge.inria.fr/frs/download.php/20098/ >> Pharo0.1Core-10262cl.zip >> >> >> Changes: >> -> Closure changes merged. >> -> BlockClosurePharo.1.cs >> -> FixDebugger.1.cs >> -> TraitDescription-closure support.st >> -> BlockContextTestFix.1.cs >> -> ArrayLiteralTestFix.1.cs >> >> >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >> > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 31, 2009

Re: [Pharo-project] [ANN] #10262cl

by StÃ©phane Ducasse

great! I will read lukas tests in the train. Closure closure closure closure....finally thanks qwak, andreas and eliot! On Mar 31, 2009, at 4:15 PM, Marcus Denker wrote: > Hi, > > I have merged the closure changed in the 1062 image (manually). > > We now can continue with this image to provide updates using the > update stream: > > http://gforge.inria.fr/frs/download.php/20098/ > Pharo0.1Core-10262cl.zip > > > Changes: > -> Closure changes merged. > -> BlockClosurePharo.1.cs > -> FixDebugger.1.cs > -> TraitDescription-closure support.st > -> BlockContextTestFix.1.cs > -> ArrayLiteralTestFix.1.cs > > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 31, 2009

Re: [Pharo-project] Fwd: problem with unicode 10262

by StÃ©phane Ducasse

I'm running to catch my train and will have internet only late tomorrow. Stef On Mar 31, 2009, at 4:39 PM, Michael Rueger wrote: > > fix attached > > Michael > <UTF8DecomposedTextConverter class- > encodingNames.st.gz>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 31, 2009

Re: [Pharo-project] [ANN] #10262cl

by Michael Rueger

Marcus Denker wrote: > The question is: can we live without? > > We could add a changeset that just pops up a window that says: end-of- > line, please get the hand-build image. Yes, I think at this point in the pre-release process it is allowed to do that. People should be rebuilding there developer images on a regular basis anyways ;-) Michael

March 31, 2009

Re: [Pharo-project] [ANN] #10262cl

by Marcus Denker

Hi, So this is not done as an update... reason: much simpler. doing the closure conversation is a bit manual, e.g. closing all windows, doing some other stuff, then save, restart, cleanup changeset... then re-saving all the dirty packages. I would *a lot* of work to do that with the update-stream. The question is: can we live without? We could add a changeset that just pops up a window that says: end-of- line, please get the hand-build image. Marcus On 31.03.2009, at 16:15, Marcus Denker wrote: > Hi, > > I have merged the closure changed in the 1062 image (manually). > > We now can continue with this image to provide updates using the > update stream: > > http://gforge.inria.fr/frs/download.php/20098/ > Pharo0.1Core-10262cl.zip > > > Changes: > -> Closure changes merged. > -> BlockClosurePharo.1.cs > -> FixDebugger.1.cs > -> TraitDescription-closure support.st > -> BlockContextTestFix.1.cs > -> ArrayLiteralTestFix.1.cs > > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

March 31, 2009