- Pharo-dev - lists.pharo.org

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

by Maximiliano Tabacman

I can only test it in Ubuntu and Windows for the moment. Steps to reproduce (in Windows)1) Download:http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-20180207…) Download:http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.512.sha.88… 3) Unzip everything to the same directory, then startÂ Pharo.exe4) Execute in WorkspaceMetacello newÂ baseline:'Seaside3';Â repository: 'github://SeasideSt/Seaside:master/repository';Â load5) Save and Quit6) Try toÂ startÂ Pharo.exe If I delete stderr, stdout and PharoDebug.log before restarting Pharo, I can see that stderr and PharoDebug.log are created at 0 bytes, there is no other log that I can find. As you can see, no startup scripts are involved. This is a clean Pharo installation. And this happens both in Windows and in Ubuntu, no matter in which OS I try to do the download+load. If it is of any help, this has been happening exactly since buildÂ 383. It worked perfectly up to buildÂ 382. On Thursday, February 8, 2018, 4:42:36 PM GMT-3, Sean P. DeNigris <sean(a)clipperadams.com> wrote: 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

[Pharo 7.0-dev] Build #512: 21254-Command-line-handlers-should-have-an-option-to-force-the-omission-of-preferences-for-applications-deployment

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

There is a new Pharo build available! The status of the build #512 was: SUCCESS. The Pull Request #811 was integrated: "21254-Command-line-handlers-should-have-an-option-to-force-the-omission-of-preferences-for-applications-deployment" Pull request url: https://github.com/pharo-project/pharo/pull/811 Issue Url: https://pharo.fogbugz.com/f/cases/21254 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 8, 2018

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