March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: Issue 668: should clean the option-World click menu

by StÃ©phane Ducasse

we should remove first the obsolete items (related to etoy and project). stef On Mar 22, 2009, at 9:24 PM, Rob Rothwell wrote: > Ok...it seems to be build in: > > Morph>>buildMetaMenu: > and > PasteUpMorph>>addCustomMenuItems:hand: > > So...any thoughts on what should be in this menu? > > Take care, > > Rob > > 2009/3/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > probably > I see > > > > > On Mar 21, 2009, at 8:23 PM, Rob Rothwell wrote: > > Is this what you are talking about? What would you like instead? > What was the intent of the option-World click menu? > > Rob > > 2009/3/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Begin forwarded message: > > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: March 19, 2009 3:13:47 PM CEST > To: ducasse(a)iam.unibe.ch > Subject: Issue 668: should clean the option-World click menu > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > > From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> > Date: March 19, 2009 3:13:40 PM CEST > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: Issue 668: should clean the option-World click menu > > > <star_on.gif> Issue 668: > should clean the option-World click menu > http://code.google.com/p/pharo/issues/detail?id=668 > Apparently option-click on the world brings a new menu (which points > to crappy stuff) and to the new pharo menu. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > <OldWorldMenu.jpg>_______________________________________________ > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by bryce＠kampjes.demon.co.uk

Rob Rothwell writes: > Well, I don't have any "tough, real world examples," but the example Bert > gave me: > > multiply := Array new: 4. > 1 to: 4 do: [:i | > multiply at: i put: [:x | x * i]. > ]. > > (multiply at: 3) value: 5. > > Resulted in the appropriate answer 15!!! I tried this on Linux, and it works. Poking around a bit more brought up the emergency evaluator because BlockClosure doesn't understand #isValid:. Bryce P.S I'm not going to have much time in April as we have family staying and our second son is due.

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by Schwab,Wilhelm K

Stef, Adding #isValid got me a little further along. I was able to select the new theme and can at least open a debugger, though _using_ it stirs up trouble over #asMinimalRepresentation (or similar method). In trying to evaluate 'hello' at:200, I was faced with some message boxes claiming there was no such method; that seemed to happen w/ vistary and not watery2??? I too had problems closing windows. Bill --- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Sunday, March 22, 2009 1:35 PM To: Pharo-project(a)lists.gforge.inria.fr Cc: Eliot Miranda Subject: Re: [Pharo-project] [ANN] Closures for beta testers > UIThemeVistary beCurrent. what is nice is that the VM does not crash. I cannot open any browser. So in another image I checked a bit. BlockContext defined isValid (a polymoprph-EventEnhancements) sent by BlockContext>>isValid "Answer true so we can be used in event dispatching." ^true WeakActionSequence>>asMinimalRepresentation | valid | valid := self select: [:e | e isValid ]. valid size = 0 ifTrue: [^nil]. valid size = 1 ifTrue: [^valid first]. ^valid I do not really know the code of gary. As a pure hack I added isValid to blockClosure to return true and I did not get the problem of course this is a shitty way to answer the problem. Now when I close using the cross on the right (and not the button on the left) the vistaryStyle I get similar problems [closure] in UIThemeVistary>>createCloseBoxFor: DNU asMinimalRepresentation BlockContext>>asMinimalRepresentation "Answer the receiver." ^self I defined the same in BlockClosure and it worked but I would prefer to understand what I was doing. stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by bryce＠kampjes.demon.co.uk

StÃ©phane Ducasse writes: > I guess not. > Normally if Bryce support closure the rest should flow. :) The VMs I supplied both support closures, or should. I'll have a quick test here. Bryce

March 22, 2009

Re: [Pharo-project] Fwd: Issue 668: should clean the option-World click menu

by Rob Rothwell

Ok...it seems to be build in: Morph>>buildMetaMenu: and PasteUpMorph>>addCustomMenuItems:hand: So...any thoughts on what should be in this menu? Take care, Rob 2009/3/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > probably > I see > > > > > On Mar 21, 2009, at 8:23 PM, Rob Rothwell wrote: > > Is this what you are talking about? What would you like instead? What >> was the intent of the option-World click menu? >> >> Rob >> >> 2009/3/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> >> Begin forwarded message: >> >> From: pharo-project-owner(a)lists.gforge.inria.fr >>> Date: March 19, 2009 3:13:47 PM CEST >>> To: ducasse(a)iam.unibe.ch >>> Subject: Issue 668: should clean the option-World click menu >>> >>> You are not allowed to post to this mailing list, and your message has >>> been automatically rejected. If you think that your messages are >>> being rejected in error, contact the mailing list owner at >>> pharo-project-owner(a)lists.gforge.inria.fr. >>> >>> >>> >>> From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> >>> Date: March 19, 2009 3:13:40 PM CEST >>> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >>> Subject: Issue 668: should clean the option-World click menu >>> >>> >>> <star_on.gif> Issue 668: >>> should clean the option-World click menu >>> http://code.google.com/p/pharo/issues/detail?id=668 >>> Apparently option-click on the world brings a new menu (which points to >>> crappy stuff) and to the new pharo menu. >>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> <OldWorldMenu.jpg>_______________________________________________ >> 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 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by StÃ©phane Ducasse

Apparently Traits do not understand variablesAndOffsetsDo: invoked indirectly from parse: sourceStream class: class category: aCategory noPattern: noPattern context: ctxt notifying: req ifFail: aBlock EncoderForV3PlusClosure>>init: aClass context: aContext notifying: req requestor := req. class := aClass. nTemps := 0. supered := false. self initScopeAndLiteralTables. class variablesAndOffsetsDo: [:variable "<String|CFieldDefinition>" :offset "<Integer|nil>" | offset isNil ifTrue: [scopeTable at: variable name put: ((Smalltalk at: #FieldNode ifAbsent: [self error: 'FiledNode is missing']) new fieldDefinition: variable)] ifFalse: [scopeTable at: variable put: (offset >= 0 ifTrue: [InstanceVariableNode new name: variable index: offset] ifFalse: [MaybeContextInstanceVariableNode new name: variable index: offset negated])]]. aContext ~~ nil ifTrue: [| homeNode | homeNode := self bindTemp: self doItInContextName. "0th temp = aContext passed as arg" aContext tempNames withIndexDo: [:variable :index| scopeTable at: variable put: (MessageAsTempNode new receiver: homeNode selector: #namedTempAt: arguments: (Array with: (self encodeLiteral: index)) precedence: 3 from: self)]]. sourceRanges := Dictionary new: 32. globalSourceRanges := OrderedCollection new: 32

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by StÃ©phane Ducasse

Excellent I created an issue. what I will do is to run the tests before and after. http://code.google.com/p/pharo/issues/detail?id=685 Stef On Mar 22, 2009, at 8:01 PM, Lukas Renggli wrote: > Another thing that is missing in ContextPart is #methodSelector, used > by the debugger. > > Fix attached. > > On Sun, Mar 22, 2009 at 7:44 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> probably doing a difference between the interface of BlockContext and >> BlockClosure will help. >> >> Stef >> On Mar 22, 2009, at 7:34 PM, StÃ©phane Ducasse wrote: >> >>>> UIThemeVistary beCurrent. >>> >>> what is nice is that the VM does not crash. >>> I cannot open any browser. >>> So in another image I checked a bit. >>> >>> BlockContext defined isValid (a polymoprph-EventEnhancements) >>> >>> sent by >>> >>> BlockContext>>isValid >>> "Answer true so we can be used in event dispatching." >>> >>> ^true >>> >>> WeakActionSequence>>asMinimalRepresentation >>> >>> | valid | >>> valid := self select: [:e | e isValid ]. >>> valid size = 0 >>> ifTrue: [^nil]. >>> valid size = 1 >>> ifTrue: [^valid first]. >>> ^valid >>> >>> I do not really know the code of gary. >>> As a pure hack I added isValid to blockClosure to return true >>> and I did not get the problem >>> >>> of course this is a shitty way to answer the problem. >>> >>> >>> Now when I close using the cross on the right (and not the button on >>> the left) >>> the vistaryStyle I get similar problems >>> >>> [closure] in UIThemeVistary>>createCloseBoxFor: DNU >>> asMinimalRepresentation >>> >>> >>> BlockContext>>asMinimalRepresentation >>> "Answer the receiver." >>> >>> ^self >>> >>> I defined the same in BlockClosure and it worked but I would >>> prefer to >>> understand what I was doing. >>> >>> >>> >>> >>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > <FixDebugger.1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by StÃ©phane Ducasse

did it work in the nonclosure version? Stef On Mar 22, 2009, at 8:06 PM, Marco Schmidt wrote: > There is a DNU after trying to open the SqueakMap Package Loader- > Tool... > > > VM: Squeak 3.11.1 (alpha) - (The above "multiply" test ^^ succeded) > IMG: 10259-ClosureBootstrap > OS: Windows Vista x64 > > > > > > > 2009/3/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > probably doing a difference between the interface of BlockContext and > BlockClosure will help. > > Stef > On Mar 22, 2009, at 7:34 PM, StÃ©phane Ducasse wrote: > > >> UIThemeVistary beCurrent. > > > > what is nice is that the VM does not crash. > > I cannot open any browser. > > So in another image I checked a bit. > > > > BlockContext defined isValid (a polymoprph-EventEnhancements) > > > > sent by > > > > BlockContext>>isValid > > "Answer true so we can be used in event dispatching." > > > > ^true > > > > WeakActionSequence>>asMinimalRepresentation > > > > | valid | > > valid := self select: [:e | e isValid ]. > > valid size = 0 > > ifTrue: [^nil]. > > valid size = 1 > > ifTrue: [^valid first]. > > ^valid > > > > I do not really know the code of gary. > > As a pure hack I added isValid to blockClosure to return true > > and I did not get the problem > > > > of course this is a shitty way to answer the problem. > > > > > > Now when I close using the cross on the right (and not the button on > > the left) > > the vistaryStyle I get similar problems > > > > [closure] in UIThemeVistary>>createCloseBoxFor: DNU > > asMinimalRepresentation > > > > > > BlockContext>>asMinimalRepresentation > > "Answer the receiver." > > > > ^self > > > > I defined the same in BlockClosure and it worked but I would > prefer to > > understand what I was doing. > > > > > > > > > > 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 > > <SqueakDebug - > Kopie.log>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by Marco Schmidt

There is a DNU after trying to open the SqueakMap Package Loader- Tool... VM: Squeak 3.11.1 (alpha) - (The above "multiply" test ^^ succeded) IMG: 10259-ClosureBootstrap OS: Windows Vista x64 2009/3/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > probably doing a difference between the interface of BlockContext and > BlockClosure will help. > > Stef > On Mar 22, 2009, at 7:34 PM, StÃ©phane Ducasse wrote: > > >> UIThemeVistary beCurrent. > > > > what is nice is that the VM does not crash. > > I cannot open any browser. > > So in another image I checked a bit. > > > > BlockContext defined isValid (a polymoprph-EventEnhancements) > > > > sent by > > > > BlockContext>>isValid > > "Answer true so we can be used in event dispatching." > > > > ^true > > > > WeakActionSequence>>asMinimalRepresentation > > > > | valid | > > valid := self select: [:e | e isValid ]. > > valid size = 0 > > ifTrue: [^nil]. > > valid size = 1 > > ifTrue: [^valid first]. > > ^valid > > > > I do not really know the code of gary. > > As a pure hack I added isValid to blockClosure to return true > > and I did not get the problem > > > > of course this is a shitty way to answer the problem. > > > > > > Now when I close using the cross on the right (and not the button on > > the left) > > the vistaryStyle I get similar problems > > > > [closure] in UIThemeVistary>>createCloseBoxFor: DNU > > asMinimalRepresentation > > > > > > BlockContext>>asMinimalRepresentation > > "Answer the receiver." > > > > ^self > > > > I defined the same in BlockClosure and it worked but I would prefer to > > understand what I was doing. > > > > > > > > > > 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 >

March 22, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by Lukas Renggli

Another thing that is missing in ContextPart is #methodSelector, used by the debugger. Fix attached. On Sun, Mar 22, 2009 at 7:44 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > probably doing a difference between the interface of BlockContext and > BlockClosure will help. > > Stef > On Mar 22, 2009, at 7:34 PM, StÃ©phane Ducasse wrote: > >>> Â UIThemeVistary beCurrent. >> >> what is nice is that the VM does not crash. >> I cannot open any browser. >> So in another image I checked a bit. >> >> BlockContext defined isValid (a polymoprph-EventEnhancements) >> >> sent by >> >> BlockContext>>isValid >> Â Â Â "Answer true so we can be used in event dispatching." >> >> Â Â Â ^true >> >> WeakActionSequence>>asMinimalRepresentation >> >> Â Â Â | valid | >> Â Â Â valid := self select: [:e | e isValid ]. >> Â Â Â valid size = 0 >> Â Â Â Â Â Â Â ifTrue: [^nil]. >> Â Â Â valid size = 1 >> Â Â Â Â Â Â Â ifTrue: [^valid first]. >> Â Â Â ^valid >> >> I do not really know the code of gary. >> As a pure hack I added isValid to blockClosure to return true >> and I did not get the problem >> >> of course this is a shitty way to answer the problem. >> >> >> Now when I close using the cross on the right (and not the button on >> the left) >> the vistaryStyle I get similar problems >> >> [closure] in UIThemeVistary>>createCloseBoxFor: DNU >> asMinimalRepresentation >> >> >> BlockContext>>asMinimalRepresentation >> Â Â Â "Answer the receiver." >> >> Â Â Â ^self >> >> I defined the same in BlockClosure and it worked but I would prefer to >> understand what I was doing. >> >> >> >> >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

March 22, 2009