- Pharo-dev - lists.pharo.org

[Pharo-project] DNU with beMethodArg?

by StÃ©phane Ducasse

Hi guys I was debugging some bug and I got the following DoItIn: ThisContext ^ self do: [:each | ((ThisContext namedTempAt: 1) includes: each) ifFalse: [^ false]] I selected (ThisContext namedTempAt: 1 and I got MessageAsTempNode does not understand beMethodArg method: doit context: ctxt " pattern [ | temporaries ] block => MethodNode." | sap blk prim temps messageComment methodNode | properties := AdditionalMethodState new. sap := self pattern: doit inContext: ctxt. "sap={selector, arguments, precedence}" properties selector: (sap at: 1). encoder selector: (sap at: 1). (sap at: 2) do: [:argNode | argNode beMethodArg]. ^^^^ doit ifFalse: [self pragmaSequence]. temps := self temporaries. messageComment := currentComment. currentComment := nil. doit ifFalse: [self pragmaSequence]. prim := self pragmaPrimitives. self statements: #() innerBlock: doit. blk := parseNode. doit ifTrue: [blk returnLast] ifFalse: [blk returnSelfIfNoOther: encoder]. hereType == #doIt ifFalse: [^self expected: 'Nothing more']. self interactive ifTrue: [self removeUnusedTemps]. methodNode := self newMethodNode comment: messageComment. ^methodNode selector: (sap at: 1) arguments: (sap at: 2) precedence: (sap at: 3) temporaries: temps block: blk encoder: encoder primitive: prim properties: properties argNode is a MessageAsTempNode and beMethodArg is only defined on TempVariableNode http://code.google.com/p/pharo/issues/detail?id=4551 Stef

July 26, 2011

Re: [Pharo-project] problem with text editor when editing code and get a proposal to change it

by Igor Stasenko

On 26 July 2011 15:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > In 1.4 I get an annoying regression, when the system propose me a change my text gets mangled or not updated. > Am I the only one to get that? > It would be good to fix that. > We only accept a good bug reports (with video coverage!) :) > Stef -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

[Pharo-project] problem with text editor when editing code and get a proposal to change it

by StÃ©phane Ducasse

Hi guys In 1.4 I get an annoying regression, when the system propose me a change my text gets mangled or not updated. Am I the only one to get that? It would be good to fix that. Stef

July 26, 2011

Re: [Pharo-project] [update 1.4] #14060

by Damien Cassou

Is it now possible to browse Smalltalk class/packages/methods/categories using Ring? Said differently, how can I instanciate Ring on the image? On Tue, Jul 26, 2011 at 3:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 14060 > ----- > > - enhancing Ring and fixing some API for better tools integration. SystemNavigation is now using Ring objects. > todo: should fix some tests on unsentMessages > > Stef and Veronica > -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 26, 2011

[Pharo-project] [update 1.4] #14060

by StÃ©phane Ducasse

14060 ----- - enhancing Ring and fixing some API for better tools integration. SystemNavigation is now using Ring objects. todo: should fix some tests on unsentMessages Stef and Veronica

July 26, 2011

Re: [Pharo-project] Pharo 1.3 Seaside 'client' build ?

by Marcus Denker

On Jul 25, 2011, at 4:31 PM, Sven Van Caekenberghe wrote: > Hi (Marcus), > > I was looking for a Pharo 1.3 Seaside 'client' build on the CI server(s) but couldn't find it. > > It used to be available for 1.2.x (this seems to be gone as well). > > I think that for good reciprocal relations with Seaside, it would be very good to have a tested build of the current main Pharo images. It make a good testcase as well. And it saves quite some work, loading the Seaside config is pretty slow. > > I remember reading something about some clients being removed from the CI's, but I didn't register it fully. > Yes, I will add that to the new Jenkis setup asap. (some of the next days). > Thx, > > Sven > > PS: Another questions is: is 1.3 'released', if so where are the links on the website, where is the 'noise' ? We should fix the last open reports, create a new one-click and do the releaseâ¦ http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 -- Marcus Denker Do it together: http://taskfor.us

July 26, 2011

Re: [Pharo-project] pharo on lion

by Alexandre Bergel

+1 Alexandre On 26 Jul 2011, at 13:02, Sven Van Caekenberghe wrote: > Yes please! > > That would be so cool. > > On 21 Jul 2011, at 08:40, Lukas Renggli wrote: > >> Something for Esteban: it would be super cool if the VM had the >> full-screen button in the title bar :-) >> >> On Thursday, 21 July 2011, Lukas Renggli <renggli(a)gmail.com> wrote: >>> It worked for me on the GM. >>> >>> On Thursday, 21 July 2011, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> Hi, >>>> >>>> Is Pharo working Ok on the new OS X Lion? I am asking because I am considering to upgrade. >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Not knowing how to do something is not an argument for how it cannot be done." >>>> >>>> >>>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2011

Re: [Pharo-project] pharo on lion

by Sven Van Caekenberghe

Yes please! That would be so cool. On 21 Jul 2011, at 08:40, Lukas Renggli wrote: > Something for Esteban: it would be super cool if the VM had the > full-screen button in the title bar :-) > > On Thursday, 21 July 2011, Lukas Renggli <renggli(a)gmail.com> wrote: >> It worked for me on the GM. >> >> On Thursday, 21 July 2011, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> Is Pharo working Ok on the new OS X Lion? I am asking because I am considering to upgrade. >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Not knowing how to do something is not an argument for how it cannot be done." >>> >>> >>> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >

July 26, 2011

Re: [Pharo-project] [update 1.4] #14057

by StÃ©phane Ducasse

On Jul 26, 2011, at 10:18 AM, Gary Chambers wrote: > I understand. I remember when I first saw that stuff! lol :) this is a filter. People that faint should not continue coding in the UI ;) After all the *Plus and the rest we are making progress not as fast as I would like. Now I'm having as side project to clean the event loop with a nice double dispatch and really event and not buffer. Stef

July 26, 2011

Re: [Pharo-project] [update 1.4] #14057

by Gary Chambers

I understand. I remember when I first saw that stuff! Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, July 25, 2011 8:17 PM Subject: Re: [Pharo-project] [update 1.4] #14057 On Jul 25, 2011, at 6:08 PM, Gary Chambers wrote: > I did check. Having a single accessor (with mutation) does not cover all > the cases. Some users require *no* getter, for instance, so would be > erroneous to update in response to a change. Ok I finally got it :) we are open to change :) our goal was to clean the ugly "ok let us compile a method on the fly" Stef > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" > <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some >> problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed >> and UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "StÃ©phane Ducasse" >> <stephane.ducasse(a)inria.fr> >> To: "pharo-project open-source Smalltalk" >> <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor >> killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a >> perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > >

July 26, 2011