June 2020 - Pharo-users - lists.pharo.org

HOPL-4 papers

by Rafael Luque

Hi all, Not strictly related with Pharo, but I think it could be interesting to any Smalltalker. ACM has just published the History of Programming Languages 4. The papers cover the following languages: APL, C++, Closure, Fortran parallelism, D, Emacs Lisp, F#, Groovy, Hygienic Macros (Scheme), JavaScript, LabVIEW, Logo. MATLAB, Objective-C, Oz, R, ML, Verilog and Smalltalk. The paper dedicated to Smalltalk is "The evolution of Smalltalk: from Smalltalk-72 through Squeak" by Dan Ingalls. All the papers are available to download here: https://dl.acm.org/toc/pacmpl/2020/4/HOPL Rafael Luque

June 12, 2020

Re: [Pharo-users] Monticello Bug introduced in Pharo 8

by Peter Newton

Thanks Markus, I will check there and post an bug report. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 11, 2020

Re: [Pharo-users] Monticello Bug introduced in Pharo 8

by StÃ©phane Ducasse

Welcome on board Peter and thanks for your time and willingness to improve Pharo. > On 10 Jun 2020, at 04:01, Peter Newton <peter(a)courriel.net.au> wrote: > > Hi. I'm a Smalltalk newcomer, slowly exploring Pharo to understand its > potential and in the process I've found and fixed what seems to be a bug in > Metacello (although it could be more widespread). So what now, how to best > report the bug and my fix? > > To reproduce the bug, in Pharo 8 or 9, simply chose 'Save' from the > Monticello browser when a repository is selected and edit either the version > name or the log message, you should see the error "/MCSaveVersionDialog > doesn't understand #selectedClassOrMetaClass/". > > As far as I can tell, Pharo 8 introduced the idea of a CompletionEngine for > Smalltalk text areas that sends /#selectedClassOrMetaClass/ to the text > area. This method is implemented in descendants of MCCodeTool but doesn't > exist in the parent MCTool - which is what MCSaveVersionDialog derives from. > > My fix reworks /MCTool>>textMorph:/ to allow the version dialog text areas > to be constructed with the message #beForSmalltalkComment rather than > #beForSmalltalkScripting. This works, but I have no idea if this is the best > way, how to share my fix, or how to raise this as a bug with the Pharo > maintainers to make Pharo a more stable platform. All advice is most > welcome. I do not know in fact. What is the kind of text that is displayed in MCTool? S

June 10, 2020

Re: [Pharo-users] Primitive is not executed

by StÃ©phane Ducasse

Thanks a lot Guille and Pablo :) https://github.com/pharo-project/pharo/issues/6549 <https://github.com/pharo-project/pharo/issues/6549> > On 10 Jun 2020, at 10:45, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Jesus, > > We have looked at it with Pablo. We were wondering too if you could give us a reproducible case for what is not working with you, because we have tested it and it seems to be working (details below). > > The array replace primitive is a generic primitive that handles the replace of arrays of objects and arrays of native values (8, 16, 32, 64bit values). > Now, for the primitive to work, both arrays should be of the same type/format. > > âAll these examples do use the primitive" > a := WordArray withAll: #( 1 2 3 4 ). > b := WordArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := DoubleWordArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > âAll these examples do not use the primitive" > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := ByteArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := Array withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > If you tell us a bit more we could probably be of more help. > Also, we were looking for you in discord to ask you questions, are you there? > Guille > >> El 9 jun 2020, a las 21:31, Jesus Mari Aguirre <jmariaguirre(a)gmail.com <mailto:jmariaguirre@gmail.com>> escribiÃ³: >> >> Thanks for your response >> I've tried in WordArray and ByteArray and same behaviour, primitive 105 fails and executes the code after the primitive call. >> It is Pharo 8.0 64 on Mac Os X...I will try on Ubuntu 19.4...as soon as I can. >> the same problem in all of the Collection-Native all of them use primitive 105 >> >> <Captura de pantalla 2020-06-09 a las 21.20.43.png> >> >> El mar., 9 jun. 2020 a las 18:34, StÃ©phane Ducasse (<stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>>) escribiÃ³: >> Hello >> >>> I am developing a "numpy arrays" like framework on pharo, >> >> Cool >> >>> I decided to use an Array type depending on the class of its elements (I thought it would be more efficient) i.e if the array contains floats it will be stored in a floatArray but if contains integers, a IntegerArray will be used. >> >> Did you check the WordArray class and friend? >> >> >>> I make an extensive use of use of the method replaceFrom: start to: stop with: replacement startingAt: repStart when I do concat and other methods that imply copying but I've realize that primitive 105 is not executes when I call this method from these kind of arrays but it works if I use a normal Array. >>> What do you suggest me to do? is it better to use the normal Array for every type of content or is it a bugg? Is FloatArray/IntegerArray more efficient in any way? If not...what is their purpose? >> >> I read the code and I do not understand why this primitives have all the same number. >> May be this is normal. I will ask around. >> >>> >>> replaceFrom: start to: stop with: replacement startingAt: repStart >>> "Primitive. This destructively replaces elements from start to stop in the receiver starting at index, repStart, in the collection, replacement. Answer the receiver. Range checks are performed in the primitive only. Optional. See Object documentation whatIsAPrimitive." >>> <primitive: 105> >>> super replaceFrom: start to: stop with: replacement startingAt: repStart >> >> >> S. >> -------------------------------------------- >> 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

June 10, 2020

Re: [Pharo-users] PharoExtras group on smalltalkhub -> github ?

by StÃ©phane Ducasse

Hi paul > Are there any projects in PharoExtras (or other public groups) that have not been ported to github? I do not know. > If they've been ported where are they now? usually they are ported to Pharo contributions. > Is there any map between smalltalkhub projects and their new locations or is it all on a project by project basis right now? For now we have Pharo contributions for the Pharo core and orphan and after we have several organisations I would like to push https://github.com/pharo-project/PharoMap <https://github.com/pharo-project/PharoMap> For example I plan to migrate all the containers projects to https://github.com/pharo-containers <https://github.com/pharo-containers> Like that if someone looks for a data structure there is a single entry point. > > > Seems like there's individual mailing list messages and some notes on project sites and thats about it. IS that accurate? > > > Thanks -------------------------------------------- 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

June 10, 2020

PharoExtras group on smalltalkhub -> github ?

by PAUL DEBRUICKER

Are there any projects in PharoExtras (or other public groups) that have not been ported to github? If they've been ported where are they now? Is there any map between smalltalkhub projects and their new locations or is it all on a project by project basis right now? Seems like there's individual mailing list messages and some notes on project sites and thats about it. IS that accurate? Thanks

June 10, 2020

Re: [Pharo-users] Roassal and Seaside/Willow

by Cyril Ferlicot

On Wed, Jun 10, 2020 at 4:46 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Hello, > Hi, > Is it possible to integrate Roassal with Seaside/Willow? > > I found a project in smalltalkhub, but I don't know if it is outdated and I know smalltalkhub is being discontinued, so I am not sure if I should use it. > I don't know for Roassal, but there is a project to build and display graph visualisations in Seaside called TelescopeCytoscape: https://github.com/TelescopeSt/TelescopeCytoscape In case it interests you :) Have a nice day > Regards, > Vitor -- Cyril Ferlicot https://ferlicot.fr

June 10, 2020

Roassal and Seaside/Willow

by Vitor Medina Cruz

Hello, Is it possible to integrate Roassal with Seaside/Willow? I found a project in smalltalkhub, but I don't know if it is outdated and I know smalltalkhub is being discontinued, so I am not sure if I should use it. Regards, Vitor

June 10, 2020

Re: [Pharo-users] Primitive is not executed

by Jesus Mari Aguirre

Eso es, Guille!! that was the problem, both arrays should be of the same type/format, I tried the method calling a replaceFrom: 1 to: 2 with: #(1 2 3) startingAt: 1. so I was passing an Array object instead, so I'm doing the right thing but wrong testing! Thanks a lot! I'm not on Discord but I could activate an account if it is more comfortable to you... El miÃ©., 10 jun. 2020 a las 10:46, Guillermo Polito (< guillermopolito(a)gmail.com>) escribiÃ³: > Hi Jesus, > > We have looked at it with Pablo. We were wondering too if you could give > us a reproducible case for what is not working with you, because we have > tested it and it seems to be working (details below). > > The array replace primitive is a generic primitive that handles the > replace of arrays of objects and arrays of native values (8, 16, 32, 64bit > values). > Now, for the primitive to work, both arrays should be of the same > type/format. > > âAll these examples do use the primitive" > a := WordArray withAll: #( 1 2 3 4 ). > b := WordArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := DoubleWordArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > âAll these examples do not use the primitive" > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := ByteArray withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > a := DoubleWordArray withAll: #( 1 2 3 4 ). > b := Array withAll: #( 5 6 ). > > a replaceFrom: 1 to: 2 with: b startingAt: 1. > > If you tell us a bit more we could probably be of more help. > Also, we were looking for you in discord to ask you questions, are you > there? > Guille > > El 9 jun 2020, a las 21:31, Jesus Mari Aguirre <jmariaguirre(a)gmail.com> > escribiÃ³: > > Thanks for your response > I've tried in WordArray and ByteArray and same behaviour, primitive 105 > fails and executes the code after the primitive call. > It is Pharo 8.0 64 on Mac Os X...I will try on Ubuntu 19.4...as soon as I > can. > the same problem in all of the Collection-Native all of them use primitive > 105 > > <Captura de pantalla 2020-06-09 a las 21.20.43.png> > > El mar., 9 jun. 2020 a las 18:34, StÃ©phane Ducasse (< > stephane.ducasse(a)inria.fr>) escribiÃ³: > >> Hello >> >> I am developing a "numpy arrays" like framework on pharo, >> >> >> Cool >> >> I decided to use an Array type depending on the class of its elements (I >> thought it would be more efficient) i.e if the array contains floats it >> will be stored in a floatArray but if contains integers, a IntegerArray >> will be used. >> >> >> Did you check the WordArray class and friend? >> >> >> I make an extensive use of use of the method replaceFrom: start to: stop >> with: replacement startingAt: repStart when I do concat and other >> methods that imply copying but I've realize that primitive 105 is not >> executes when I call this method from these kind of arrays but it works if >> I use a normal Array. >> What do you suggest me to do? is it better to use the normal Array for >> every type of content or is it a bugg? Is FloatArray/IntegerArray more >> efficient in any way? If not...what is their purpose? >> >> >> I read the code and I do not understand why this primitives have all the >> same number. >> May be this is normal. I will ask around. >> >> >> replaceFrom: start to: stop with: replacement startingAt: repStart >> "Primitive. This destructively replaces elements from start to stop in >> the receiver starting at index, repStart, in the collection, replacement. >> Answer the receiver. Range checks are performed in the primitive only. >> Optional. See Object documentation whatIsAPrimitive." >> <primitive: 105> >> super replaceFrom: start to: stop with: replacement startingAt: repStart >> >> >> S. >> -------------------------------------------- >> 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 >> >> >

June 10, 2020

Re: [Pharo-users] Willow vs Seaside

by Vitor Medina Cruz

Thanks! Willow on top of Seaside really is the best of the world :) On Tue, Jun 9, 2020 at 1:36 PM gettimothy via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > That sounds really cool! > > Bookmarked, for my next Seaside project. > > thx! > > ---- On Mon, 08 Jun 2020 18:00:14 -0400 *Gabriel Cotelli > <g.cotelli(a)gmail.com <g.cotelli(a)gmail.com>>* wrote ---- > > Hi Vitor, > > Willow is built on top of Seaside and it aims to ease the creation of > interactive AJAX-based web applications. So if you're planning to do a lot > of partial page rendering via AJAX updates it's worth a try. > > We're using it for several applications and the only full page refresh is > done on the first request reception, all the other interactions in the > application are handled by AJAX. One of its main features is to abstract > away a lot of the complexity of hand made AJAX calls. > > You can take a look at the slides and videos of the last talk we do in the > subject to get an idea of when it's useful: > https://www.slideshare.net/FASTPresentations/willow-the-interaction-tour-by… > > > https://youtu.be/U6-JoPRcXHc > > Feel free to ask any more questions here or on the discord channel. > > Regards, > Gabriel > > On Mon, Jun 8, 2020 at 12:42 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > Hello, > > What's is the difference? Why should I use one or another? > > Regards, > Vitor > > >

June 10, 2020