- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo 7.0-dev] Build #510: 21246-Store-main-window-title

by Henrik-Nergaard

Hi Marcus, You can add -p for this error to be ignored: man mkdir | grep -A 2 parents -p, --parents no error if existing, make parent directories as needed Best regards, Henrik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 8, 2018

Re: [Pharo-dev] [OpenSmalltalk/opensmalltalk-vm] Crashes while typing on macOS Sierra (#141)

by Eliot Miranda

On Tue, Feb 6, 2018 at 1:02 PM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hi Eliot, > > > On 06.02.2018, at 21:40, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi Tobias, > > > > On Feb 6, 2018, at 4:43 AM, Tobias Pape <notifications(a)github.com> > wrote: > > > >> Closed #141 via ecd41af. > >> > > > > thank you very much for this fix! Lots of people have been hurting from > this. > > No problem, it was mostly Marcel Weiher's guidance tho :) > A huge thank you to Marcel then! It's not what you know, it's who you know ;-) Best regards > -Tobias > _,,,^..^,,,_ best, Eliot

Feb. 8, 2018

Re: [Pharo-dev] Calypso wishlist

by Nicolas Cellier

Then you might have used kind of named block params like MyClass >> [foo: aFoo bar: aBar | self foo: aFoo; bar: aBar] Le 8 fÃ©vr. 2018 20:11, "Stephane Ducasse" <stepharo.self(a)gmail.com> a Ã©crit : > Hi ben > > This is not what I asked for :). In nautilus you do not have to switch > mode to define a method. > > Now about your proposal. I would like to be able the type tonel method > definition > > SomeClass >> echo: anObject [ > ^ 42 > ] > > Tonel represents what I want for methods. > This way students could just type nearly as in the books and I would > change the book to reflect this. > And people can decide either to type all the time the class or now. > > Stef > > > > > On Thu, Feb 8, 2018 at 6:28 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > > > > On 9 February 2018 at 00:45, Ben Coman <btc(a)openinworld.com> wrote: > >> On 8 February 2018 at 16:22, Stephane Ducasse <stepharo.self(a)gmail.com> > >> wrote: > >>> Hi denis > >>> > >>> - I would like to be able to define a method even in the class pane > >>> and that the system detects it automatically. > >> > >> It would be nice to do it from anywhere including Playground with > >> something like... > >> Classname >> #methodname >> [ method source here ] > >> > >> So I just tired a quick experiment... > >> > >> Object subclass: #SomeClass > >> instanceVariableNames: '' > >> classVariableNames: '' > >> package: 'MethodBuilderExperiment' > >> > >> On SomeClass defined method... > >> existingMethod > >> ^1 > >> > >> On CompiledMethod defined method... > >> >> blockClosure > >> | newSource | > >> newSource := self methodNode selector, String crlf, > >> blockClosure sourceNode newSource allButFirst allButLast. > >> self methodClass compile: newSource > >> > >> > >> Now each of the following lines can be evaluated... > >> > >> SomeClass existingMethod "==> 1" > >> SomeClass >> #existingMethod >> [ ^42]. > >> SomeClass existingMethod "==> 42" > > > > That should have been. > > > > SomeClass new existingMethod "==> 1" > > SomeClass >> #existingMethod >> [ ^42]. > > SomeClass new existingMethod "==> 42" > > > >> > >> > >> > >> And another experiment... > >> > >> Object subclass: #MethodBuilder > >> instanceVariableNames: 'methodClass methodSelector' > >> classVariableNames: '' > >> package: 'MethodBuilderExperiment' > >> > >> On MethodBuilder defined method... > >> class: aClass selector: aSelector > >> methodClass := aClass. > >> methodSelector := aSelector. > >> > >> On MethodBuilder defined method... > >> >> blockClosure > >> |newSource| > >> newSource := methodSelector, String crlf, > >> blockClosure sourceNode newSource allButFirst allButLast. > >> methodClass compile: newSource > >> > >> On Behaviour re-defined method... > >> compiledMethodAt: selector > >> ^ self methodDict at: selector ifAbsent: > >> [ MethodBuilder new class: self selector: selector > ] > >> > >> > >> Now each of the following lines can be evaluated... > >> > >> Someclass noMethod "==> error... Instance of SomeClass class did not > >> understand #noMethod" > >> SomeClass >> #noMethod >> [ ^42 ]. > >> Someclass noMethod "==> 42" > > > > And should have been... > > Someclass new noMethod "==> error... Instance of SomeClass class did not > > understand #noMethod" > > SomeClass >> #noMethod >> [ ^42 ]. > > Someclass new noMethod "==> 42" > > > > > > I see that is a bit problematic for keyword messages, but with a tweak... > > > > On MethodBuilder defined... > > >> blockClosure > > |newSource| > > methodSelector isArray > > ifFalse: [ newSource := methodSelector ] > > ifTrue: [ > > newSource := ''. > > methodSelector do: [ :token | newSource := newSource , token asString, ' > ' ] > > ]. > > newSource := newSource, String crlf, > > blockClosure sourceNode newSource allButFirst allButLast. > > methodClass compile: newSource > > > > > > now the following can be evaluated... > > > > SomeClass >>#(echo: anObject) >> [ ^anObject ]. > > SomeClass new echo: 'doyoulike'. "==> doyoulike" > > > > > > Another form to define a method might be... > > SomeClass >> [ echo: anObject > > ^anObject ] > > > > I think that looks better, but would require a loosening of block syntax. > > > > cheers -ben > > > >>> - Then we are starting to reverse engineering the ecompletion system > >>> and I'm learning it. > >>> I would like to know if Calypso can communicate with ecompletion the > >>> fact that we are defining a method. Then I have to check how the > >>> system can know that we are typing method argument when defining the > >>> signature but I think that this is not related to calypso. > >>> > >>> Stef > >>> > > > >

Feb. 8, 2018

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

by Sean P. DeNigris

Pharo Smalltalk Developers mailing list wrote > I have no idea why this is happening I had a similar situation due to a deprecation warning generated by my startup script. I aborted from the debugger, and the image worked normally, but when I saved, quit and tried to restart the image, it wouldn't open (VM icon in list of active apps, but window never appeared macOS high Sierra). ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 8, 2018

Re: [Pharo-dev] Calypso wishlist

by Stephane Ducasse

Hi ben This is not what I asked for :). In nautilus you do not have to switch mode to define a method. Now about your proposal. I would like to be able the type tonel method definition SomeClass >> echo: anObject [ ^ 42 ] Tonel represents what I want for methods. This way students could just type nearly as in the books and I would change the book to reflect this. And people can decide either to type all the time the class or now. Stef On Thu, Feb 8, 2018 at 6:28 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On 9 February 2018 at 00:45, Ben Coman <btc(a)openinworld.com> wrote: >> On 8 February 2018 at 16:22, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >>> Hi denis >>> >>> - I would like to be able to define a method even in the class pane >>> and that the system detects it automatically. >> >> It would be nice to do it from anywhere including Playground with >> something like... >> Classname >> #methodname >> [ method source here ] >> >> So I just tired a quick experiment... >> >> Object subclass: #SomeClass >> instanceVariableNames: '' >> classVariableNames: '' >> package: 'MethodBuilderExperiment' >> >> On SomeClass defined method... >> existingMethod >> ^1 >> >> On CompiledMethod defined method... >> >> blockClosure >> | newSource | >> newSource := self methodNode selector, String crlf, >> blockClosure sourceNode newSource allButFirst allButLast. >> self methodClass compile: newSource >> >> >> Now each of the following lines can be evaluated... >> >> SomeClass existingMethod "==> 1" >> SomeClass >> #existingMethod >> [ ^42]. >> SomeClass existingMethod "==> 42" > > That should have been. > > SomeClass new existingMethod "==> 1" > SomeClass >> #existingMethod >> [ ^42]. > SomeClass new existingMethod "==> 42" > >> >> >> >> And another experiment... >> >> Object subclass: #MethodBuilder >> instanceVariableNames: 'methodClass methodSelector' >> classVariableNames: '' >> package: 'MethodBuilderExperiment' >> >> On MethodBuilder defined method... >> class: aClass selector: aSelector >> methodClass := aClass. >> methodSelector := aSelector. >> >> On MethodBuilder defined method... >> >> blockClosure >> |newSource| >> newSource := methodSelector, String crlf, >> blockClosure sourceNode newSource allButFirst allButLast. >> methodClass compile: newSource >> >> On Behaviour re-defined method... >> compiledMethodAt: selector >> ^ self methodDict at: selector ifAbsent: >> [ MethodBuilder new class: self selector: selector ] >> >> >> Now each of the following lines can be evaluated... >> >> Someclass noMethod "==> error... Instance of SomeClass class did not >> understand #noMethod" >> SomeClass >> #noMethod >> [ ^42 ]. >> Someclass noMethod "==> 42" > > And should have been... > Someclass new noMethod "==> error... Instance of SomeClass class did not > understand #noMethod" > SomeClass >> #noMethod >> [ ^42 ]. > Someclass new noMethod "==> 42" > > > I see that is a bit problematic for keyword messages, but with a tweak... > > On MethodBuilder defined... > >> blockClosure > |newSource| > methodSelector isArray > ifFalse: [ newSource := methodSelector ] > ifTrue: [ > newSource := ''. > methodSelector do: [ :token | newSource := newSource , token asString, ' ' ] > ]. > newSource := newSource, String crlf, > blockClosure sourceNode newSource allButFirst allButLast. > methodClass compile: newSource > > > now the following can be evaluated... > > SomeClass >>#(echo: anObject) >> [ ^anObject ]. > SomeClass new echo: 'doyoulike'. "==> doyoulike" > > > Another form to define a method might be... > SomeClass >> [ echo: anObject > ^anObject ] > > I think that looks better, but would require a loosening of block syntax. > > cheers -ben > >>> - Then we are starting to reverse engineering the ecompletion system >>> and I'm learning it. >>> I would like to know if Calypso can communicate with ecompletion the >>> fact that we are defining a method. Then I have to check how the >>> system can know that we are typing method argument when defining the >>> signature but I think that this is not related to calypso. >>> >>> Stef >>> >

Feb. 8, 2018

Re: [Pharo-dev] Calypso wishlist

by Ben Coman

On 9 February 2018 at 00:45, Ben Coman <btc(a)openinworld.com> wrote: > On 8 February 2018 at 16:22, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Hi denis >> >> - I would like to be able to define a method even in the class pane >> and that the system detects it automatically. > > It would be nice to do it from anywhere including Playground with > something like... > Classname >> #methodname >> [ method source here ] > > So I just tired a quick experiment... > > Object subclass: #SomeClass > instanceVariableNames: '' > classVariableNames: '' > package: 'MethodBuilderExperiment' > > On SomeClass defined method... > existingMethod > ^1 > > On CompiledMethod defined method... > >> blockClosure > | newSource | > newSource := self methodNode selector, String crlf, > blockClosure sourceNode newSource allButFirst allButLast. > self methodClass compile: newSource > > > Now each of the following lines can be evaluated... > > SomeClass existingMethod "==> 1" > SomeClass >> #existingMethod >> [ ^42]. > SomeClass existingMethod "==> 42" That should have been. SomeClass new existingMethod "==> 1" SomeClass >> #existingMethod >> [ ^42]. SomeClass new existingMethod "==> 42" > > > > And another experiment... > > Object subclass: #MethodBuilder > instanceVariableNames: 'methodClass methodSelector' > classVariableNames: '' > package: 'MethodBuilderExperiment' > > On MethodBuilder defined method... > class: aClass selector: aSelector > methodClass := aClass. > methodSelector := aSelector. > > On MethodBuilder defined method... > >> blockClosure > |newSource| > newSource := methodSelector, String crlf, > blockClosure sourceNode newSource allButFirst allButLast. > methodClass compile: newSource > > On Behaviour re-defined method... > compiledMethodAt: selector > ^ self methodDict at: selector ifAbsent: > [ MethodBuilder new class: self selector: selector ] > > > Now each of the following lines can be evaluated... > > Someclass noMethod "==> error... Instance of SomeClass class did not > understand #noMethod" > SomeClass >> #noMethod >> [ ^42 ]. > Someclass noMethod "==> 42" And should have been... Someclass new noMethod "==> error... Instance of SomeClass class did not understand #noMethod" SomeClass >> #noMethod >> [ ^42 ]. Someclass new noMethod "==> 42" I see that is a bit problematic for keyword messages, but with a tweak... On MethodBuilder defined... >> blockClosure |newSource| methodSelector isArray ifFalse: [ newSource := methodSelector ] ifTrue: [ newSource := ''. methodSelector do: [ :token | newSource := newSource , token asString, ' ' ] ]. newSource := newSource, String crlf, blockClosure sourceNode newSource allButFirst allButLast. methodClass compile: newSource now the following can be evaluated... SomeClass >>#(echo: anObject) >> [ ^anObject ]. SomeClass new echo: 'doyoulike'. "==> doyoulike" Another form to define a method might be... SomeClass >> [ echo: anObject ^anObject ] I think that looks better, but would require a loosening of block syntax. cheers -ben >> - Then we are starting to reverse engineering the ecompletion system >> and I'm learning it. >> I would like to know if Calypso can communicate with ecompletion the >> fact that we are defining a method. Then I have to check how the >> system can know that we are typing method argument when defining the >> signature but I think that this is not related to calypso. >> >> Stef >>

Feb. 8, 2018

Re: [Pharo-dev] Calypso wishlist

by Ben Coman

On 8 February 2018 at 16:22, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi denis > > - I would like to be able to define a method even in the class pane > and that the system detects it automatically. It would be nice to do it from anywhere including Playground with something like... Classname >> #methodname >> [ method source here ] So I just tired a quick experiment... Object subclass: #SomeClass instanceVariableNames: '' classVariableNames: '' package: 'MethodBuilderExperiment' On SomeClass defined method... existingMethod ^1 On CompiledMethod defined method... >> blockClosure | newSource | newSource := self methodNode selector, String crlf, blockClosure sourceNode newSource allButFirst allButLast. self methodClass compile: newSource Now each of the following lines can be evaluated... SomeClass existingMethod "==> 1" SomeClass >> #existingMethod >> [ ^42]. SomeClass existingMethod "==> 42" And another experiment... Object subclass: #MethodBuilder instanceVariableNames: 'methodClass methodSelector' classVariableNames: '' package: 'MethodBuilderExperiment' On MethodBuilder defined method... class: aClass selector: aSelector methodClass := aClass. methodSelector := aSelector. On MethodBuilder defined method... >> blockClosure |newSource| newSource := methodSelector, String crlf, blockClosure sourceNode newSource allButFirst allButLast. methodClass compile: newSource On Behaviour re-defined method... compiledMethodAt: selector ^ self methodDict at: selector ifAbsent: [ MethodBuilder new class: self selector: selector ] Now each of the following lines can be evaluated... Someclass noMethod "==> error... Instance of SomeClass class did not understand #noMethod" SomeClass >> #noMethod >> [ ^42 ]. Someclass noMethod "==> 42" cheers -ben > > - Then we are starting to reverse engineering the ecompletion system > and I'm learning it. > I would like to know if Calypso can communicate with ecompletion the > fact that we are defining a method. Then I have to check how the > system can know that we are typing method argument when defining the > signature but I think that this is not related to calypso. > > Stef >

Feb. 8, 2018

[Pharo 7.0-dev] Build #511: 21246-Store-main-window-title

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #511 was: SUCCESS. The Pull Request #809 was integrated: "21246-Store-main-window-title" Pull request url: https://github.com/pharo-project/pharo/pull/809 Issue Url: https://pharo.fogbugz.com/f/cases/21246 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 8, 2018

Re: [Pharo-dev] VMs build process restored

by Cyril Ferlicot

On Thu, Feb 8, 2018 at 4:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Cyril, > Hi :) > > Why do you need to back port? Why can't you use the 7.x VM with 6.x images? The VM is intended to be backwards compatible. > For each Pharo release, Pharo defines stable vms. For example, in a Jenkins bash script if we execute this: wget -O- https://get.pharo.org/64/61+vm | bash It will download a fresh Pharo 6.1 image, a source file and a vm of the right OS marked as stable for Pharo 6.1. With this, we ensure that a certain Pharo release will not have a different vm too often because if changes are intended to be backwards compatible, there is always the possibility a problem get through (for example one time OSProcess stopped to work on OSX because of a problem with the system version). So, I *can* use the vm for Pharo 7 if I get it myself but through hacks in our scripts instead of using official distribution ways of Pharo. I would prefer to only use official distribution ways in order to reduce the complexity of our scripts. In conclusion what I mean by "backport" is that Pharo officially marks the current vm as stable for Pharo 6.1 to get it via zeroconf. -- Cyril Ferlicot https://ferlicot.fr

Feb. 8, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Sven Van Caekenberghe

> On 8 Feb 2018, at 13:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 7 Feb 2018, at 11:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> I made notes and will add a page with all the infos later today. (for http://pharo.org/contribute ) >> > > I added a simple page as a first step: > > http://pharo.org/review-fix > > > Marcus Already quite good, thank you.

Feb. 8, 2018