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

Script to download specific Pharo version
by BrunoBB Nov. 4, 2019

Nov. 4, 2019

Hi, We have a Linux script to build our image and was working well until recently. It seems that the failure is related (not confirmed yet) to https://github.com/pharo-project/pharo/issues/4764 Becuase it fail to load Seaside into the Pharo image. Is there any way to download a specific build or version like ? wget -q -O- https://get.pharo.org/64/703 | bash In this case to download Pharo 7.03 We want to try our script with different Pharo versions, because "wget -O- https://get.pharo.org/64 | bash" it download the latest. regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 2

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.
by Richard O'Keefe Oct. 31, 2019

Oct. 31, 2019

We don't know what you are actually trying to do. WHICH book has the problem you are trying to solve? I spent some time looking at the code in your repository, and the KA* classes look very "passive". I don't really see any simulation going on anywhere but in the test cases, and that just feels wrong. I would expect a network simulator to model network nodes as Processes with SharedQueues of messages coming in and responding by sending messages through other SharedQueues. On Wed, 30 Oct 2019 at 19:34, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > 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 > >> > >

1 0

[ANN] XMLWriter moved to GitHub
by Torsten Bergmann Oct. 31, 2019

Oct. 31, 2019

Hi, the STHub -> PharoExtras project "XMLWriter" 1. was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLWriter to https://github.com/pharo-contributions/XML-XMLWriter including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one 2. Travis CI job was setup (https://travis-ci.org/pharo-contributions/XML-XMLWriter) for P7 which is green 4. the new version is tagged in git as version 2.8.5 5. the Config was adopted with 2.8.5 and uploaded into MetaRepoForPharo70 so it works in catalog You can load "XMLWriter" in Pharo 7 and 8 from Catalog or via load instructions Metacello new baseline: 'XMLWriter'; repository: 'github://pharo-contributions/XML-XMLWriter/src'; load. More to come... Bye T.

3 3

We Are Smalltalk
by Richard Kenneth Eng Oct. 30, 2019

Oct. 30, 2019

https://youtu.be/pB0iI6ksW30

9 12

Status of Encryption / Keys / Etc
by Eric Gade Oct. 30, 2019

Oct. 30, 2019

Hi all, I'm try to get an idea of the status of keys and key signing (cross platform if possible) in Pharo. Do we have general mechanisms for signing pieces of data, and for encrypting/decrypting based on public/private key pairs, including those set as the default for a given user on a given system? Thanks. -- Eric

1 0

Html5 inputs examples for seaside
by Oswall Verny Arguedas C. Oct. 30, 2019

Oct. 30, 2019

I would like to know if you have examples of use for html5 inputs in Seaside 3.3. I am with the Seaside book on the website. I have examples of textInput and others, however I am interested in inputs of numbers, dates, months, html5 colors, apply calculations and get results. I have errors in syntax. I need to establish memory variables that should not persist and then perform calculations on methods and only totals persist. Thanks in advance. Oswall

1 0

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

Oct. 30, 2019

1 1

Re: [Pharo-users] help bij one of the last challenges of the chapterof network simulation of the oop book.
by Richard O'Keefe Oct. 30, 2019

Oct. 30, 2019

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 >

2 2

help bij one of the last challenges of the chapterof network simulation of the oop book.
by Roelof Wobben Oct. 29, 2019

Oct. 29, 2019

1 0

[ANN] Material Design Lite for Seaside v2.2.0
by Cyril Ferlicot Oct. 29, 2019

Oct. 29, 2019

Hi everyone! I am happy to announce the version 2.2.0 of Material Design Lite for seaside. https://github.com/DuneSt/MaterialDesignLite/releases/tag/v2.2.0 This version brings 3 new features: - Expansion panel in the form of brushes or widget - A table component that allows one to describe the columns content instead of providing a collection of rows - Predefined alerts as an extension of MDL Thanks to Julien Delplanque who helped a lot to release this version. You can find a demo of the MDL version at: https://mdl.ferlicot.fr/ Have a nice day -- Cyril Ferlicot https://ferlicot.fr

1 0