- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by phil＠highoctane.be

A revival! Very nice. We should discuss database connection pools at one point as this is an important matter that isn't discussed much. There are things on Ramon Leon's blog but still. On a side note, we should be able to have tutorials like that were the user could copy/paste the code in a *workspace* and follow things up. I am looking into something, will show more if I succeed at materializing. Phil Le 2 sept. 2014 06:49, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > Nice! > > Doru > > > On Mon, Sep 1, 2014 at 11:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> Hi, >> >> I published another introduction/tutorial article >> >> Reddit.st - In 10 Cool Pharo Classes >> >> Implementing a Reddit style web application in Pharo using Seaside, >> Glorp and PostgreSQL >> >> >> https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 >> >> The focus is not so much on the smaller size or the higher developer >> productivity in Pharo, but more on the fact that we can cover so much >> ground using such powerful frameworks, as well as the natural development >> flow from model over tests and persistence to web GUI. This is a more >> intermediate level article that assumes basic knowledge about Pharo >> (language and IDE). >> >> https://ci.inria.fr/pharo-contribution/job/Reddit/ >> >> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit >> >> Enjoy! >> >> Sven >> >> PS: This article is actually an update of an article that I wrote in 2010 >> and that became unavailable/outdated. >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 2, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Yuriy Tymchuk

It i think just wonât load in Pharo4 because there is no configuration for PetitParser Uko On 02 Sep 2014, at 06:50, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Moose is not supported yet for Pharo 4. We are still in the process of releasing it for Pharo 3 and we will move afterwards. If you want to play with it, it is more advisable to play in Pharo 3. > > Doru > > > On Tue, Sep 2, 2014 at 6:49 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You can find the Moose project mailing list coordinates here: > http://www.moosetechnology.org/about/contact > > Doru > > > On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev(a)free.fr> wrote: > Le 01/09/2014 22:04, Nicolai Hess a Ã©crit : > > R3IcoSphereShape>>addVertex: p > > found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip > VERSION=stable PHARO=40) > and changing the CriticRule RBFindBlockArgumentAssignment to search for > methodArguments instead > of block arguments and run the critic browser. > > I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: > > GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers > |values| > values := numbers collect: #first. > > "Lets check if the first and the last has different has different sign" > ((values first * values last) negative and: [ (values includes: 0) not]) > ifTrue: [ *** here is the problem *** > Cannot store into -> numbers := self addZeroTo: numbers ]. > > (I didn't have time yet to find the moose mailing-list or group to report this bug) > HTH > > regards > > Alain > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 2, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Tudor Girba

Moose is not supported yet for Pharo 4. We are still in the process of releasing it for Pharo 3 and we will move afterwards. If you want to play with it, it is more advisable to play in Pharo 3. Doru On Tue, Sep 2, 2014 at 6:49 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You can find the Moose project mailing list coordinates here: > http://www.moosetechnology.org/about/contact > > Doru > > > On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev(a)free.fr> wrote: > >> Le 01/09/2014 22:04, Nicolai Hess a Ã©crit : >> >> R3IcoSphereShape>>addVertex: p >>> >>> found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip >>> VERSION=stable PHARO=40) >>> and changing the CriticRule RBFindBlockArgumentAssignment to search for >>> methodArguments instead >>> of block arguments and run the critic browser. >>> >> >> I had a similar error yesterday trying to load Moose in a Pharo4 image in >> GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: >> >> GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers >> |values| >> values := numbers collect: #first. >> >> "Lets check if the first and the last has different has different >> sign" >> ((values first * values last) negative and: [ (values includes: >> 0) not]) >> ifTrue: [ *** here is the problem *** >> Cannot store into -> numbers := self addZeroTo: numbers ]. >> >> (I didn't have time yet to find the moose mailing-list or group to report >> this bug) >> HTH >> >> regards >> >> Alain >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 2, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Tudor Girba

You can find the Moose project mailing list coordinates here: http://www.moosetechnology.org/about/contact Doru On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev(a)free.fr> wrote: > Le 01/09/2014 22:04, Nicolai Hess a Ã©crit : > > R3IcoSphereShape>>addVertex: p >> >> found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip >> VERSION=stable PHARO=40) >> and changing the CriticRule RBFindBlockArgumentAssignment to search for >> methodArguments instead >> of block arguments and run the critic browser. >> > > I had a similar error yesterday trying to load Moose in a Pharo4 image in > GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: > > GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers > |values| > values := numbers collect: #first. > > "Lets check if the first and the last has different has different > sign" > ((values first * values last) negative and: [ (values includes: 0) > not]) > ifTrue: [ *** here is the problem *** > Cannot store into -> numbers := self addZeroTo: numbers ]. > > (I didn't have time yet to find the moose mailing-list or group to report > this bug) > HTH > > regards > > Alain > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 2, 2014

Re: [Pharo-dev] [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by Tudor Girba

Nice! Doru On Mon, Sep 1, 2014 at 11:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I published another introduction/tutorial article > > Reddit.st - In 10 Cool Pharo Classes > > Implementing a Reddit style web application in Pharo using Seaside, Glorp > and PostgreSQL > > > https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 > > The focus is not so much on the smaller size or the higher developer > productivity in Pharo, but more on the fact that we can cover so much > ground using such powerful frameworks, as well as the natural development > flow from model over tests and persistence to web GUI. This is a more > intermediate level article that assumes basic knowledge about Pharo > (language and IDE). > > https://ci.inria.fr/pharo-contribution/job/Reddit/ > > http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit > > Enjoy! > > Sven > > PS: This article is actually an update of an article that I wrote in 2010 > and that became unavailable/outdated. > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 2, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Alain Rastoul

Le 01/09/2014 22:04, Nicolai Hess a Ã©crit : > R3IcoSphereShape>>addVertex: p > > found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip > VERSION=stable PHARO=40) > and changing the CriticRule RBFindBlockArgumentAssignment to search for > methodArguments instead > of block arguments and run the critic browser. I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers |values| values := numbers collect: #first. "Lets check if the first and the last has different has different sign" ((values first * values last) negative and: [ (values includes: 0) not]) ifTrue: [ *** here is the problem *** Cannot store into -> numbers := self addZeroTo: numbers ]. (I didn't have time yet to find the moose mailing-list or group to report this bug) HTH regards Alain

Sept. 1, 2014

Jenkins builds not properly preserving artifacts?

by Tim Mackinnon

Guys - Iâve noticed that when a build completed on the Inria infrastructure, for a short time the console output correctly shows all the artefacts that were used to create that build - e.g. the slices loaded etc. However after a short time - the output then reverts to something like below (which isnât as useful): Started by upstream project "[8mha:AAAAqh+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8â¦. originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on pharo-contribution-winxp in workspace C:\builds\workspace\PharoLauncher Deleting project workspaceâ¦ done --- Iâve looked at a few other jobs (I noticed this for Pharo Launcher) and they seem the same. I think the jobs arenât configured properly? - As normally (at least in other languages like Java), the intent is that the console output reflects what was on the console when the job was run. I have a hunch that something is overwriting these files before they are archived away. As we donât seem to have other details of what went into a build job (which is another issue - I would expect the changes page for a build to also show this info in a better format). Do you think this could be fixed? tim

Sept. 1, 2014

[Article] Reddit.st - In 10 Cool Pharo Classes

by Sven Van Caekenberghe

Hi, I published another introduction/tutorial article Reddit.st - In 10 Cool Pharo Classes Implementing a Reddit style web application in Pharo using Seaside, Glorp and PostgreSQL https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 The focus is not so much on the smaller size or the higher developer productivity in Pharo, but more on the fact that we can cover so much ground using such powerful frameworks, as well as the natural development flow from model over tests and persistence to web GUI. This is a more intermediate level article that assumes basic knowledge about Pharo (language and IDE). https://ci.inria.fr/pharo-contribution/job/Reddit/ http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit Enjoy! Sven PS: This article is actually an update of an article that I wrote in 2010 and that became unavailable/outdated. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Sept. 1, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Nicolai Hess

R3IcoSphereShape>>addVertex: p found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser. But yes, the OC exception could be a bit more verbose :) nicolai 2014-09-01 21:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Roassal 3D. Herâs the job: https://ci.inria.fr/moose/job/Roassal3d/ > > Uko > > On 01 Sep 2014, at 20:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > which configuration are you trying to load? > > > 2014-09-01 18:20 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> By the way, is there any way to check which is the problematic method? >> Because I failed to find it in log. >> >> Uko >> >> >> On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> This this started at 29th and crashes image while loading configuration. >> Any idea whatâs wrong? >> >> >> This means that you load code that assigns to arguments (method >> arguments). >> The new compiler allowed it (an oversight), the old one did notâ¦. now it >> is again not allowed. >> >> (for bock arguments, it is still allowed). >> >> ==== Startup Error: SyntaxErrorNotification: Cannot store intoOCSemanticError>>notify:at: >> OCSemanticError>>defaultAction >> [ :ex | >> ex defaultAction. >> ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... >> BlockClosure>>cull: >> [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] >> BlockClosure>>ensure: >> Context>>handleSignal: >> OCSemanticError(Exception)>>signal >> OCASTSemanticAnalyzer>>storeIntoSpecialVariable: >> OCASTSemanticAnalyzer>>lookupVariableForWrite: >> OCASTSemanticAnalyzer>>visitAssignmentNode: >> RBAssignmentNode>>acceptVisitor: >> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >> [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] >> OrderedCollection>>do: >> OCASTSemanticAnalyzer>>visitSequenceNode: >> RBSequenceNode>>acceptVisitor: >> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >> OCASTSemanticAnalyzer>>visitMethodNode: >> RBMethodNode>>acceptVisitor: >> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >> OCASTSemanticAnalyzer>>analyze: >> RBMethodNode>>doSemanticAnalysis >> RBMethodNode>>doSemanticAnalysisInContext: >> [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... >> BlockClosure>>on:do: >> OpalCompiler>>doSemanticAnalysis >> [ >> ast := self parse. >> self doSemanticAnalysis ] in [ >> [ >> ast := self parse. >> self doSemanticAnalysis ] >> on: OCSourceCodeChanged >> do: [ :notification | >> self source: notification newSourceCode. >> notification retry ]. >> cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... >> BlockClosure>>on:do: >> [ >> [ >> ast := self parse. >> self doSemanticAnalysis ] >> on: OCSourceCodeChanged >> do: [ :notification | >> self source: notification newSourceCode. >> notification retry ]. >> cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ...Got startup errors: SyntaxErrorNotification: Cannot store into >> >> >> >> Cheers >> Uko >> >> >> >> > >

Sept. 1, 2014

Re: [Pharo-dev] Startup Error: SyntaxErrorNotification: Cannot store into

by Yuriy Tymchuk

Roassal 3D. Herâs the job: https://ci.inria.fr/moose/job/Roassal3d/ Uko On 01 Sep 2014, at 20:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > which configuration are you trying to load? > > > 2014-09-01 18:20 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > By the way, is there any way to check which is the problematic method? Because I failed to find it in log. > > Uko > > > On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong? >>> >> >> This means that you load code that assigns to arguments (method arguments). >> The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed. >> >> (for bock arguments, it is still allowed). >> >>> ==== Startup Error: SyntaxErrorNotification: Cannot store into >>> OCSemanticError>>notify:at: >>> OCSemanticError>>defaultAction >>> [ :ex | >>> ex defaultAction. >>> ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... >>> BlockClosure>>cull: >>> [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] >>> BlockClosure>>ensure: >>> Context>>handleSignal: >>> OCSemanticError(Exception)>>signal >>> OCASTSemanticAnalyzer>>storeIntoSpecialVariable: >>> OCASTSemanticAnalyzer>>lookupVariableForWrite: >>> OCASTSemanticAnalyzer>>visitAssignmentNode: >>> RBAssignmentNode>>acceptVisitor: >>> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >>> [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] >>> OrderedCollection>>do: >>> OCASTSemanticAnalyzer>>visitSequenceNode: >>> RBSequenceNode>>acceptVisitor: >>> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >>> OCASTSemanticAnalyzer>>visitMethodNode: >>> RBMethodNode>>acceptVisitor: >>> OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: >>> OCASTSemanticAnalyzer>>analyze: >>> RBMethodNode>>doSemanticAnalysis >>> RBMethodNode>>doSemanticAnalysisInContext: >>> [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... >>> BlockClosure>>on:do: >>> OpalCompiler>>doSemanticAnalysis >>> [ >>> ast := self parse. >>> self doSemanticAnalysis ] in [ >>> [ >>> ast := self parse. >>> self doSemanticAnalysis ] >>> on: OCSourceCodeChanged >>> do: [ :notification | >>> self source: notification newSourceCode. >>> notification retry ]. >>> cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... >>> BlockClosure>>on:do: >>> [ >>> [ >>> ast := self parse. >>> self doSemanticAnalysis ] >>> on: OCSourceCodeChanged >>> do: [ :notification | >>> self source: notification newSourceCode. >>> notification retry ]. >>> cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... >>> Got startup errors: >>> SyntaxErrorNotification: Cannot store into >>> >>> >>> Cheers >>> Uko >> > >

Sept. 1, 2014