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

Re: [Pharo-users] Pharo TechTalk Oct 24

by tesonep＠gmail.com

Friendly reminder: Today at 17:00 (GMT+2, Paris Time) we have the techtalk about the headless VM Calendar entry: https://association.pharo.org/event-3419545 On Thu, Oct 17, 2019 at 1:02 PM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Next techtalk will be *next* week (Oct 24): > > Topic: Headless VM > > Calendar entry: https://association.pharo.org/event-3419545 > > > (it was originally dated to today, we will try to be better in pre-planning from the next one on) -- Pablo Tesone. tesonep(a)gmail.com

Oct. 24, 2019

Re: [Pharo-users] [Pharo-dev] The Lands Platform at SLE 2019: Pharo magic inside

by tesonep＠gmail.com

Really nice!!! On Thu, Oct 24, 2019 at 8:44 AM Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > I loved it. great job nick! > > El miÃ©., 23 oct. 2019 a las 9:16, Nick Papoylias (<npapoylias(a)gmail.com>) escribiÃ³: >> >> The Lands Platform: Lan.guages and D.omain S.yntax, >> @sleconf 2019, co-located with @splashcon >> >> https://youtu.be/HMgJK8mVPYw >> >> Showcasing live magic tricks powered by the @pharoproject >> >> Best, >> >> Nick -- Pablo Tesone. tesonep(a)gmail.com

Oct. 24, 2019

Re: [Pharo-users] [Pharo-dev] The Lands Platform at SLE 2019: Pharo magic inside

by Santiago Bragagnolo

I loved it. great job nick! El miÃ©., 23 oct. 2019 a las 9:16, Nick Papoylias (<npapoylias(a)gmail.com>) escribiÃ³: > The Lands Platform: Lan.guages and D.omain S.yntax, > @sleconf 2019, co-located with @splashcon > > https://youtu.be/HMgJK8mVPYw > > Showcasing live magic tricks powered by the @pharoproject > > Best, > > Nick >

Oct. 24, 2019

Re: [Pharo-users] Rocking Smalltalk

by askoh

Very nice. Thanks. Where can I get more info on Thales work and the Unreal work? Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 23, 2019

Re: [Pharo-users] BlockClosure

by Richard Sargent

On October 23, 2019 5:46:50 AM PDT, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >On Wed, 23 Oct 2019, 14:25 Kasper Osterbye, <kasper.osterbye(a)gmail.com> >wrote: > >> On Wed, Oct 23, 2019 at 2:21 PM phil(a)highoctane.be ><phil(a)highoctane.be> >> wrote: >> >>> It is like Object>>in: aBlock no? >>> >> Yes. >> >> But because it is an operator, you can write "obj => block => block >=> >> block". >> You can not write "obj in: block in: block in: block", because >smalltalk >> will think it is a selector named "in:in:in:". >> > >Indeed. > >I would still use in: with parentheses instead of introducing a new >(albeit >cool) operator. Especially when that particular selector has often been implemented as a shorthand for creating associations! > >Phil > > >> Best, >> >> Kasper >>

Oct. 23, 2019

Re: [Pharo-users] [ANN] BitmapCharacterSet moved to GitHub

by Sven Van Caekenberghe

> On 23 Oct 2019, at 17:17, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > the STHub -> PharoExtras project "BitmapCharacterSet" > > 1. was now moved from http://smalltalkhub.com/#!/~PharoExtras/BitmapCharacterSet to > https://github.com/pharo-contributions/BitmapCharacterSet including the FULL HISTORY > > The old STHub repo was marked as obsolete - but is linking to the new one > > 2. the test package "Collections-Tests-BitmapCharacterSet" was renamed into "Collections-BitmapCharacterSet-Tests" > > 3. Travis CI job was setup (https://travis-ci.org/pharo-contributions/BitmapCharacterSet) for P7 which is green > > 4. the new version is tagged in git as version 1.2.7. > > 5. the Config was adopted with 1.2.7 and uploaded into MetaRepoForPharo70 so it works in catalog > > > You can load "BitmapCharacterSet" in Pharo 7 and 8 from Catalog or via load instructions > > Metacello new > baseline: 'BitmapCharacterSet'; > repository: 'github://pharo-contributions/BitmapCharacterSet/src'; > load. > > > Side note: > ========== > This is one of the prerequisites for XML support (which is planned to be moved to github too) > More to come... Thanks a lot, Torsten, this is (a) really important (first step). Looking forward to the full XML Support move. > Bye > T. >

Oct. 23, 2019

[ANN] BitmapCharacterSet moved to GitHub

by Torsten Bergmann

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

Oct. 23, 2019

Re: [Pharo-users] BlockClosure

by Richard O'Keefe

No kind of object does what you want. You cannot do 3 3 or #x #y As for [:x | x + 1] 3, what would be the *point* of doing this? What is the block suppose to *do* with the 3? Do you want to extend this to [:x :y | x + y] 3 4 ? If not, why not? What about [3+4] "what to put here?" As for composition, my own library has ( [:x | x + 1] before: [:y | y * 2] ) value: 10 => 22 ( [:y | y * 2] after: [:x | x + 1] ) value: 10 => 22 with no magic syntax needed. The |> operator in F# has been imitated in several other languages. I've implemented it in my Smalltalk, and tested it, but never bothered to use it. Object methods for: 'combinators' |> unary ^(unary isMemberOf: NiladicSelector) "isKindOf: Symbol" ifTrue: [unary send_to: self] "self perform: unary" ifFalse: [unary value: self] MonadicBlock methods for: 'invoking' collect ^[:collection | collection collect: self] do ^[:collection | collection do: self] reject ^[:collection | collection reject: self] select ^[:collection | collection select: self] NiladicSelector methods for: 'invoking' collect ^[:collection | collection collect: [:each | each perform: self]] do ^[:collection | collection do: [:each | each perform: self]] reject ^[:collection | collection reject: [:each | each perform: self]] select ^[:collection | collection select: [:each | each perform: self]] 10 |> [:x | x+1] |> [:y | y*2] ==> 22 #(1 2 3) |> [:x | x * 10] collect => #(10 20 30)

Oct. 23, 2019

Re: [Pharo-users] Import a pharo 6 image in pharo 7

by Oswall Verny Arguedas C.

Thank you for your answers I will try STON first. After passing the data from pharo 6 image to pharo 7, I also want to move it to Document Database. This process is not vital at the moment, I can do it in steps. For this reason, I asked about Mongo and CouchDB. Oswall El sÃ¡b., 19 de oct. de 2019 a la(s) 19:02, Sean P. DeNigris ( sean(a)clipperadams.com) escribiÃ³: > Alejandro Infante wrote > > I agree with the previous suggestions and use Fuel or STON. > > +1. Either of these methods is pretty much a one-liner. The main hiccup > with > Fuel is installing the same Fuel version in both the source and target > images. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Oct. 23, 2019

Re: [Pharo-users] BlockClosure

by Sven Van Caekenberghe

Hi Johan, That is nice indeed. It is good to see that you have fun learning Pharo Smalltalk. Can you do it ? Of course, you can do what you want, Pharo Smalltalk is a highly flexible environment. Key to its simplicity are its ultra simple syntax which hits a magical optimum between simplicity and capability (full syntax on a postcard). With just messages and block, you can express almost anything (one limitation is that there are no macros). Part of that is (for me at least), left to right evaluation/reading - trying to change that 'hurts'. Binary operators are useful and even necessary, but the problem with totally new uses is that readers won't understand them. Being a bit more verbose helps, in my opinion. You might also be interested in the following: Lambda Calculus in Pharo Yes, the Y Combinator is useful in normal programs https://medium.com/concerning-pharo/lambda-calculus-in-pharo-a4a571869594 Regards, Sven > On 23 Oct 2019, at 15:12, main <johan_forsberg_86(a)hotmail.com> wrote: > > Hi again! > > Just putting it out there for anyone interested. > > What I did was define the following in Object: > > |> aBlock > ^ [ :x | x => self => aBlock ] > > and also: > > => msg > ^ msg value: self > > > This enabled me to compose like this (I know I probably violate every rule > in the book, whatever ): > > f := [ :x | x + 100 ]. > g := [ :x | x + 20 ]. > h := [ :x | x + 3 ]. > > 0 => (f |> g |> h). 123 > > Also tried using ~: > > 0 => (f ~ g ~ h). 123 > > It's just a matter of taste I guess, but for me it warms my heart > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Oct. 23, 2019