September 2020 - Pharo-users

Updating lists.pharo.org: New server, Mailman3 and more

by Marcus Denker

Hi, We are updating the mailinglists (everything https://lists.pharo.org/ <https://lists.pharo.org/>) -> New server, thus: new IPâ¦ -> the server will run Mailman3 (we used Mailman2) -> There will be a better Archive I will do the change of the IP address today. The only thing that could happen is that mails send still via the old server will not be in the new archive, everything else should be transparent. I will send another mail when it is done. Marcus

Sept. 14, 2020

Re: [Pharo-users] How can I make this more OOP

by Roelof Wobben

Sept. 14, 2020

Re: [Pharo-users] How can I make this more OOP

by Richard O'Keefe

"OOP is not asking an object what it is"? You've lost me. I'm reminded of a joke exam question that goes something like this: Some things have ping nature and other things have pong nature. Discuss, with examples. Whatever else it is, OOP is a means to an end, not an end in itself. It's not a religion. Allah will not cast you into the Fire for using something which is not ritually pure. The whole point of the Design Patterns movement was not to present canned solutions but to describe common *situations* characterised by (metaphorical) *forces* pushing you in incompatible directions. Question 1: Why do you even have a stream there? flattenArray: aCollection |buffer| buffer := OrderedCollection new: aCollection size. self flattenArray: aCollection into: buffer. ^buffer asArray flattenArray: anObject into: buffer (anObject respondsTo: #do:) ifTrue: [anObject do: [:each | self flattenArray: each into: buffer] ifFalse: [anObject ifNotNil: [buffer addLast: anObject]. (CAUTION: untested code.) Question 2: is there any point in *trying* to make this more ping and less pong? I have to say that in 40 years of programming, I have *never* wanted to flatten a completely arbitrary structure. When I have wanted to flatten something, it has always been an instance of the Composite design pattern, so that a specific and quite small set of classes has been involved. I am well aware that some Smalltalk systems have some sort of 'flatten' lying around like a rake in the grass, but I have found no two which agree on the specification. Question 3: Let's consider an if-less alternative. Stream flattenInto: buffer self do: [:each| each flattenInto: buffer]. Collection flattenInto: buffer self do:[:each | each flattenInto: buffer]. Object flattenInto: buffer buffer addLast: self. UndefinedObject flattenInto: buffer "Do nothing." This is Smalltalk, where we *can* add methods to system classes like these. When the payoff is worth it, I have no qualms whatever in doing so. But putting methods of little or no utility into the interface of EVERY object just feels so wrong. Here we have opposing forces: - The first approach adds two methods to your worker class, and no methods to any system class. Instead, it uses "does this object know how to iterate over its elements?" and "is this object nil?". This does minimal damage to system structure at the price of a little ritual impurity. - The second approach adds a method to four system classes, enlarging the interface of every object in the system, creating a level of coupling we'd be better without, and making it harder for someone reading your code to figure out what's going on. In the context of a Composite, with a limited number of application classes involved, the second approach is better; the method is/methods are not defined anywhere they should not be. In the context of *this* problem, the first approach is better. MUCH better. Why? Because *encapsulation* is much more important to OOP than absence-of-IFs. On Sun, 13 Sep 2020 at 21:26, Roelof Wobben via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello, > > I know that OOP is not asking a object what it is but I have to flatten a > array so I did this : > > flattenArray: aCollection > ^ (OrderedCollection > streamContents: [ :stream | self flatten: aCollection into: stream > ]) > asArray > > flatten: anObject into: result > ^ anObject isCollection > ifTrue: [ anObject do: [ :item | self flatten: item into: result ] ] > ifFalse: [ anObject ifNotNil: [ result nextPut: anObject ] ] > > The name flattenArray is given bij exercism. > > Now I wonder how I can make this more a OOP solution. > > Can someone give me some hints or some examples ? > > Roelof > > >

Sept. 14, 2020

Re: [Pharo-users] How can I make this more OOP

by Noury Bouraqadi

Your own methods can be added to any class. Just ensure they are introduced as class extensions attached to your project's package. Use the checkbox at the bottom of the system browser. > On 13 Sep 2020, at 16:44, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > > -------- Doorgestuurd bericht -------- > Onderwerp: Re: [Pharo-users] How can I make this more OOP > Datum: Sun, 13 Sep 2020 16:43:59 +0200 > Van: Roelof Wobben <r.wobben(a)home.nl> <mailto:r.wobben@home.nl> > Aan: Noury Bouraqadi <bouraqadi(a)gmail.com> <mailto:bouraqadi@gmail.com> > > Hello, Noury, > > Thanks for letting me see this but I wonder if it is good practice to place my own methods on the Object and UndefinedObject ? > > Roelof > > > Op 13-9-2020 om 14:51 schreef Noury Bouraqadi: >> Hi Roelof, >> >> Polymorphism is the answer. >> >> Object >> flattenInto: result >> result nextPut: anObject >> >> UndefinedObject >> flattenInto: result >> ^self >> >> Collection >> flattenInto: result >> self do: [ :item | item flattenInto: result ] >> >> flatten: anObject >> ^ (OrderedCollection streamContents: [ :stream | anObject flattenInto: stream ]) asArray >> >> Noury >> >> >

Sept. 14, 2020

metacolli and magritte-bootstrap

by Roelof Wobben

Hello, Does anyone know how to install magritte-bootstrap web with metacolli, I tried this : Metacello new Â Â Â repository: 'github://magritte-metamodel/bootstrap-magritte/source'; Â Â Â baseline: 'Magritte'; Â Â Â load. but I get a message that the baseline could not be found. Regards, Roelof

Sept. 13, 2020

Fwd: Re: How can I make this more OOP

by Roelof Wobben

Sept. 13, 2020

Re: [Pharo-users] How can I make this more OOP

by Noury Bouraqadi

Hi Roelof, Polymorphism is the answer. Object >> flattenInto: result result nextPut: anObject UndefinedObject >> flattenInto: result ^self Collection >> flattenInto: result self do: [ :item | item flattenInto: result ] flatten: anObject ^ (OrderedCollection streamContents: [ :stream | anObject flattenInto: stream ]) asArray Noury > On 13 Sep 2020, at 11:26, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > I know that OOP is not asking a object what it is but I have to flatten a array so I did this : > > flattenArray: aCollection > ^ (OrderedCollection > streamContents: [ :stream | self flatten: aCollection into: stream ]) > asArray > > flatten: anObject into: result > ^ anObject isCollection > ifTrue: [ anObject do: [ :item | self flatten: item into: result ] ] > ifFalse: [ anObject ifNotNil: [ result nextPut: anObject ] ] > > The name flattenArray is given bij exercism. > > Now I wonder how I can make this more a OOP solution. > > Can someone give me some hints or some examples ? > > Roelof >

Sept. 13, 2020

How can I make this more OOP

by Roelof Wobben

Sept. 13, 2020

Re: [Pharo-users] Rewrite Tool set in Spec2 changes

by StÃ©phane Ducasse

Ah I did not know that we have action bar and button bar. I should ask esteban S. > On 10 Sep 2020, at 23:41, Sebastian Jordan <sebastianjmt(a)hotmail.com> wrote: > > could you use a menuButtonbar for the buttons? Like that we can style it later. > Ok, I changed the ActionBar for a ButtonBar. Also I added a refresh items button, in case you saved a new rule you can see it without closing the current window. All is on the master branch. > Now what would be great is to see if we can use the same logic than the playground so that the tool keeps a list of previous expression. > I will start to work on this in a time. > > Thanks, > Sebastian > De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org>> en nombre de StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> > Enviado: jueves, 10 de septiembre de 2020 15:35 > Para: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Asunto: Re: [Pharo-users] Rewrite Tool set in Spec2 changes > > > >> On 9 Sep 2020, at 19:28, Sebastian Jordan <sebastianjmt(a)hotmail.com <mailto:sebastianjmt@hotmail.com>> wrote: >> >> Hi to all, >> >> Thanks to the received feedback, I made some changes on RewriteTool-Spec2. >> First, when loading a rule a more detailed description of the rules is displayed on the RewriteRulesLoaderPresenter. > Yes this is much better. > - could you use a menuButtonbar for the buttons? Like that we can style it later. >> Also, I added several examples of Rewrite Rules. These rules are examples of common refactors that are made in Pharo. > Yes this is good. >> Finally, when you open Match Tool from the Basic Rewrite Editor, the searchFor part of the rule is set to MatchTool pattern code. > Yes you see having a default value is much better. > > Now what would be great is to see if we can use the same logic than the playground > so that the tool keeps a list of previous expression. > > S > >> Screenshot of the new way to load a rule: https://imgur.com/gallery/Rp6Jfw2 <https://imgur.com/gallery/Rp6Jfw2> >> The repo of the tool: https://github.com/jordanmontt/RewriteTool-Spec2 <https://github.com/jordanmontt/RewriteTool-Spec2> >> >> Thanks! >> Sebastian >> >> <https://imgur.com/gallery/Rp6Jfw2> >> Rewrite Rule Loader <https://imgur.com/gallery/Rp6Jfw2> >> Imgur: The magic of the Internet >> imgur.com <http://imgur.com/> > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 11, 2020

Re: [Pharo-users] Rewrite Tool set in Spec2 changes

by Sebastian Jordan

* could you use a menuButtonbar for the buttons? Like that we can style it later. Ok, I changed the ActionBar for a ButtonBar. Also I added a refresh items button, in case you saved a new rule you can see it without closing the current window. All is on the master branch. * Now what would be great is to see if we can use the same logic than the playground so that the tool keeps a list of previous expression. I will start to work on this in a time. Thanks, Sebastian ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Enviado: jueves, 10 de septiembre de 2020 15:35 Para: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Asunto: Re: [Pharo-users] Rewrite Tool set in Spec2 changes On 9 Sep 2020, at 19:28, Sebastian Jordan <sebastianjmt(a)hotmail.com<mailto:sebastianjmt@hotmail.com>> wrote: Hi to all, Thanks to the received feedback, I made some changes on RewriteTool-Spec2. * First, when loading a rule a more detailed description of the rules is displayed on the RewriteRulesLoaderPresenter. Yes this is much better. - could you use a menuButtonbar for the buttons? Like that we can style it later. * Also, I added several examples of Rewrite Rules. These rules are examples of common refactors that are made in Pharo. Yes this is good. * Finally, when you open Match Tool from the Basic Rewrite Editor, the searchFor part of the rule is set to MatchTool pattern code. Yes you see having a default value is much better. Now what would be great is to see if we can use the same logic than the playground so that the tool keeps a list of previous expression. S Screenshot of the new way to load a rule: https://imgur.com/gallery/Rp6Jfw2 The repo of the tool: https://github.com/jordanmontt/RewriteTool-Spec2 Thanks! Sebastian [https://i.imgur.com/X0TvS99.png?fb]<https://imgur.com/gallery/Rp6Jfw2> Rewrite Rule Loader<https://imgur.com/gallery/Rp6Jfw2> Imgur: The magic of the Internet imgur.com<http://imgur.com/> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 10, 2020