October 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.

by Roelof Wobben

Oct. 30, 2019

Re: [Pharo-users] We Are Smalltalk

by Trygve Reenskaug

Here's a video that demonstrates something that has been done with Squeak: http://folk.uio.no/trygver/2017/Ellen-video-2.6(copy22)-%20AVCHD.H264.1440x… --Trygve On 28.10.2019 21:32, Richard Kenneth Eng wrote: > https://youtu.be/pB0iI6ksW30 > -- /The essence of object orientation is that objects collaborateto achieve a goal. / Trygve Reenskaug mailto: trygver(a)ifi.uio.no <mailto:%20trygver@ifi.uio.no> Morgedalsvn. 5A http://folk.uio.no/trygver/ N-0378 Oslo http://fullOO.info NorwayÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Tel: (+47) 468 58 625

Oct. 30, 2019

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.

by Roelof Wobben

Hello, I solved that part but I wonder ifÂ some one can give me a hint how I can read the package send from the server consume seems to return a node and not a package. Roelof Op 30-10-2019 om 06:56 schreef Roelof Wobben: > Thanks, > > That part I understandÂ but what I tryÂ to say is that if I understand > the code right the string BALLÂ is send back to the node that send the > orginal messsgae #ball.Â But as I said that one do not seem to recieve > any packages and my question is still why ? > > I debugged it several times but I do not see the reason. > > Roelof > > > > Op 30-10-2019 om 01:38 schreef Richard O'Keefe: >> The first question you should ask is "What do I expect #ball >> asUppercase to be?" >> The ANSI Smalltalk standard says >> 5.7.10.9 Message:Â asUppercase >> Synopsis >> Â Â Answer a new string which contains all of the elements of the >> receiver converted to their upper >> case equivalents. >> Definition: <readableString> >> Â Â Answer a new string which contains all of the elements of the >> receiver converted to their upper >> case equivalents. Individual element of the string are converted as if >> they were receivers of the >> message #asUppercase. >> Return Values >> Â Â <readableString> new >> Errors >> Â Â none >> >> Notice the word "string", the protocol "<readableString>", and the >> entire absence of anything >> suggesting that the receiver and result belong to the same class. >> >> In my Smalltalk library, the receiver and result DO belong to the >> same class, >> so #ball asUppercase ==> #BALL. >> But the ANSI standard does not require that. >> And I may change my library, because >> GNU Smalltalk, Dolphin Smalltalk, Smalltalk/X, Squeak, and Pharo >> all return a String.Â (On the other hand, one reason I wrote my >> Smalltalk >> was to press the edges of the ANSI standard, so maybe I'll leave it.) >> >> So I think where you have #BALL you should have 'BALL'. >> There may be other issues. >> >> On Wed, 30 Oct 2019 at 11:00, Roelof Wobben via Pharo-users >> <pharo-users(a)lists.pharo.org> wrote: >>> Hello, >>> >>> I have toÂ made this challenge as last on of the OOP book >>> >>> Servers answering requests >>> >>> When a server node consumes a packet, it converts the payload to >>> uppercase, >>> then sends that back to the sender of the request. >>> >>> This is yet another subclass which redefines the consume: method, >>> but this >>> time the node is stateless, so we have no initialization or accessor >>> methods to >>> write: >>> >>> KANetworkNode subclass: #KANetworkServer >>> instanceVariableNames: '' >>> classVariableNames: '' >>> category: 'NetworkSimulator-Nodes' >>> >>> KANetworkServer >> consume: aPacket >>> | response | >>> response := aPacket payload asUppercase. >>> self send: (KANetworkPacket >>> from: self address >>> to: aPacket sourceAddress >>> payload: response) >>> >>> >>> Define a test for the behavior of server nodes. >>> >>> >>> I tried but I miss something >>> >>> so far as I have this : >>> >>> testSendToServer >>> Â Â Â Â | packet ping pong link | >>> Â Â Â Â packet := KANetworkPacket from: #ping to: #pong payload: #ball. >>> Â Â Â Â ping := net nodeAt: #ping. >>> Â Â Â Â pong := net nodeAt: #pong. >>> Â Â Â Â link := net linkFrom: #ping to: #pong. >>> Â Â Â Â ping send: packet. >>> Â Â Â Â pong consume: packet. >>> >>> but whatever I tried I cannot think of a test that works. >>> >>> I tried >>> >>> assert:Â ping payload equals: #BALL >>> assert: ping arrievedpackages equals; 1 >>> >>> but they all fail >>> >>> It looks like ping does not recieve the package back. >>> >>> What do I do wrong or what can I test better ? >>> >>> my code so far : https://github.com/RoelofWobben/network >>> >>> and the problem is the testToServerTest that I cannot make work >>> >>> Regards, >>> >>> Roelof >>> >

Oct. 30, 2019

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.

by Roelof Wobben

Thanks, That part I understandÂ but what I tryÂ to say is that if I understand the code right the string BALLÂ is send back to the node that send the orginal messsgae #ball.Â But as I said that one do not seem to recieve any packages and my question is still why ? I debugged it several times but I do not see the reason. Roelof Op 30-10-2019 om 01:38 schreef Richard O'Keefe: > The first question you should ask is "What do I expect #ball asUppercase to be?" > The ANSI Smalltalk standard says > 5.7.10.9 Message: asUppercase > Synopsis > Answer a new string which contains all of the elements of the > receiver converted to their upper > case equivalents. > Definition: <readableString> > Answer a new string which contains all of the elements of the > receiver converted to their upper > case equivalents. Individual element of the string are converted as if > they were receivers of the > message #asUppercase. > Return Values > <readableString> new > Errors > none > > Notice the word "string", the protocol "<readableString>", and the > entire absence of anything > suggesting that the receiver and result belong to the same class. > > In my Smalltalk library, the receiver and result DO belong to the same class, > so #ball asUppercase ==> #BALL. > But the ANSI standard does not require that. > And I may change my library, because > GNU Smalltalk, Dolphin Smalltalk, Smalltalk/X, Squeak, and Pharo > all return a String. (On the other hand, one reason I wrote my Smalltalk > was to press the edges of the ANSI standard, so maybe I'll leave it.) > > So I think where you have #BALL you should have 'BALL'. > There may be other issues. > > On Wed, 30 Oct 2019 at 11:00, Roelof Wobben via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> Hello, >> >> I have to made this challenge as last on of the OOP book >> >> Servers answering requests >> >> When a server node consumes a packet, it converts the payload to uppercase, >> then sends that back to the sender of the request. >> >> This is yet another subclass which redefines the consume: method, but this >> time the node is stateless, so we have no initialization or accessor methods to >> write: >> >> KANetworkNode subclass: #KANetworkServer >> instanceVariableNames: '' >> classVariableNames: '' >> category: 'NetworkSimulator-Nodes' >> >> KANetworkServer >> consume: aPacket >> | response | >> response := aPacket payload asUppercase. >> self send: (KANetworkPacket >> from: self address >> to: aPacket sourceAddress >> payload: response) >> >> >> Define a test for the behavior of server nodes. >> >> >> I tried but I miss something >> >> so far as I have this : >> >> testSendToServer >> | packet ping pong link | >> packet := KANetworkPacket from: #ping to: #pong payload: #ball. >> ping := net nodeAt: #ping. >> pong := net nodeAt: #pong. >> link := net linkFrom: #ping to: #pong. >> ping send: packet. >> pong consume: packet. >> >> but whatever I tried I cannot think of a test that works. >> >> I tried >> >> assert: ping payload equals: #BALL >> assert: ping arrievedpackages equals; 1 >> >> but they all fail >> >> It looks like ping does not recieve the package back. >> >> What do I do wrong or what can I test better ? >> >> my code so far : https://github.com/RoelofWobben/network >> >> and the problem is the testToServerTest that I cannot make work >> >> Regards, >> >> Roelof >>

Oct. 30, 2019

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.

by Richard O'Keefe

The first question you should ask is "What do I expect #ball asUppercase to be?" The ANSI Smalltalk standard says 5.7.10.9 Message: asUppercase Synopsis Answer a new string which contains all of the elements of the receiver converted to their upper case equivalents. Definition: <readableString> Answer a new string which contains all of the elements of the receiver converted to their upper case equivalents. Individual element of the string are converted as if they were receivers of the message #asUppercase. Return Values <readableString> new Errors none Notice the word "string", the protocol "<readableString>", and the entire absence of anything suggesting that the receiver and result belong to the same class. In my Smalltalk library, the receiver and result DO belong to the same class, so #ball asUppercase ==> #BALL. But the ANSI standard does not require that. And I may change my library, because GNU Smalltalk, Dolphin Smalltalk, Smalltalk/X, Squeak, and Pharo all return a String. (On the other hand, one reason I wrote my Smalltalk was to press the edges of the ANSI standard, so maybe I'll leave it.) So I think where you have #BALL you should have 'BALL'. There may be other issues. On Wed, 30 Oct 2019 at 11:00, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > I have to made this challenge as last on of the OOP book > > Servers answering requests > > When a server node consumes a packet, it converts the payload to uppercase, > then sends that back to the sender of the request. > > This is yet another subclass which redefines the consume: method, but this > time the node is stateless, so we have no initialization or accessor methods to > write: > > KANetworkNode subclass: #KANetworkServer > instanceVariableNames: '' > classVariableNames: '' > category: 'NetworkSimulator-Nodes' > > KANetworkServer >> consume: aPacket > | response | > response := aPacket payload asUppercase. > self send: (KANetworkPacket > from: self address > to: aPacket sourceAddress > payload: response) > > > Define a test for the behavior of server nodes. > > > I tried but I miss something > > so far as I have this : > > testSendToServer > | packet ping pong link | > packet := KANetworkPacket from: #ping to: #pong payload: #ball. > ping := net nodeAt: #ping. > pong := net nodeAt: #pong. > link := net linkFrom: #ping to: #pong. > ping send: packet. > pong consume: packet. > > but whatever I tried I cannot think of a test that works. > > I tried > > assert: ping payload equals: #BALL > assert: ping arrievedpackages equals; 1 > > but they all fail > > It looks like ping does not recieve the package back. > > What do I do wrong or what can I test better ? > > my code so far : https://github.com/RoelofWobben/network > > and the problem is the testToServerTest that I cannot make work > > Regards, > > Roelof >

Oct. 30, 2019

help bij one of the last challenges of the chapterof network simulation of the oop book.

by Roelof Wobben

Oct. 29, 2019

Re: [Pharo-users] We Are Smalltalk

by Davorin Rusevljan

very nice. I have noticed that linked youtube videos have less likes than positive responses here. Liking them on youtube could help a bit for youtube algorithm to appreciate them slightly more. davorin rusevljan On Tue, Oct 29, 2019 at 5:25 PM Christopher Fuhrman < christopher.fuhrman(a)etsmtl.ca> wrote: > On Tue, 29 Oct 2019 at 10:50, tbrunz <wild.ideas(a)gmail.com> wrote: > >> Thank you Serge! And thank you, Richard for your efforts over the years >> in >> providing good material on Medium, Hackernoon, et al. >> >> We need more videos like these... I just started a Slack channel where I >> work (for promoting and discussing Pharo/Smalltalk), and I plan to start >> posting things like these videos and Richard's material on a regular >> basis. >> Both will help to grab attention & interest. >> >> -t >> >> > Very nice! > > I'm surely not the only person expecting to find a link to a tutorial so > anyone can do this in Pharo (or whatever environment it was done in...). > Can someone add that please? > > -- > Christopher Fuhrman, P.Eng., PhD > > *Professeur au DÃ©partement de gÃ©nie logiciel et des technologies de > l'informationÃTS (Ãcole de technologie supÃ©rieure)* >

Oct. 29, 2019

Re: [Pharo-users] We Are Smalltalk

by Christopher Fuhrman

On Tue, 29 Oct 2019 at 10:50, tbrunz <wild.ideas(a)gmail.com> wrote: > Thank you Serge! And thank you, Richard for your efforts over the years in > providing good material on Medium, Hackernoon, et al. > > We need more videos like these... I just started a Slack channel where I > work (for promoting and discussing Pharo/Smalltalk), and I plan to start > posting things like these videos and Richard's material on a regular > basis. > Both will help to grab attention & interest. > > -t > > Very nice! I'm surely not the only person expecting to find a link to a tutorial so anyone can do this in Pharo (or whatever environment it was done in...). Can someone add that please? -- Christopher Fuhrman, P.Eng., PhD *Professeur au DÃ©partement de gÃ©nie logiciel et des technologies de l'informationÃTS (Ãcole de technologie supÃ©rieure)*

Oct. 29, 2019

Re: [Pharo-users] We Are Smalltalk

by tbrunz

Thank you Serge! And thank you, Richard for your efforts over the years in providing good material on Medium, Hackernoon, et al. We need more videos like these... I just started a Slack channel where I work (for promoting and discussing Pharo/Smalltalk), and I plan to start posting things like these videos and Richard's material on a regular basis. Both will help to grab attention & interest. -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 29, 2019

Re: [Pharo-users] We Are Smalltalk

by horrido

Thank Serge Stinckwich. Without his video, this wouldn't have been possible. horrido wrote > Very cool! Thanks!!! > > > > tbrunz wrote >> Nice! >> >> Here's another video, one that focuses on Roassal 3, but is still very >> visual and does a nice job of showing what (Pharo) Smalltalk can do: >> >> https://youtu.be/R2rLr7Z1b8Y >> >> -t >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 29, 2019