September 2025 - Pharo-users

Smalltalk Meetup in Zurich, 31 October 2025

by Peter Ursprung

Hi all, We are organizing the next Smalltalk Meetup in Zurich, Switzerland. It will be on Friday, 31 October 2025, starting at 18:00. We will meet in a meeting room where we will have short Smalltalk talks, then we will go to a nearby restaurant. If you are interested, please register on this website by Friday, 24 October 2025: https://zurich.smalltalk.world <https://zurich.smalltalk.world> Would you like to show something interesting? Please indicate the topic of your desired presentation when registering. Regards, Peter

Sept. 29, 2025

Pharo News of the Week 39/2025

by Marcus Denker

# Pharo News of the Week 39/2025 - [ANN] RediStick v3.1.0 is now available! The Redis client for Pharo Smalltalk now supports RedisJSON APIs, enabling proper JSON data type handling instead of just strings. This makes Redis a powerful document store option for Smalltalk developers. https://github.com/mumez/RediStick/blob/master/doc/Json.md If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 12 - Backport addition of #isValid on SDL2Handle to Pharo 12 #18596 https://github.com/pharo-project/pharo/pull/18596 - Backport changes making #tagNames: on MCOrganizationDefinition ensure the tag names are symbols to Pharo 12 #18590 https://github.com/pharo-project/pharo/pull/18590 # Pharo 13 - Backport changes making #tagNames: on MCOrganizationDefinition ensure the tag names are symbols #18589 https://github.com/pharo-project/pharo/pull/18589 # Fixes - OSWindow-SDL2: setCursor if window is focused and when focus is gained #18304 https://github.com/pharo-project/pharo/pull/18304 - Handle short-form #rgb[a] colors in Color #18575 https://github.com/pharo-project/pharo/pull/18575 - Add back methods needed for SmalltalkCI #18594 https://github.com/pharo-project/pharo/pull/18594 - Worker thread should be unique, fix random failing tests #18591 https://github.com/pharo-project/pharo/pull/18591 - workers identified by name should be uniqu #18548 https://github.com/pharo-project/pharo/pull/18548 # Compiler - Improve UndeclaredVariable error #18500 https://github.com/pharo-project/pharo/pull/18500 - OpalCompiler should not depend on Roassal #18576 https://github.com/pharo-project/pharo/pull/18576 # Iceberg / Git - Enable / disbale commit button while commiting something #1973 https://github.com/pharo-vcs/iceberg/pull/1973 - Fix inspector #1970 https://github.com/pharo-vcs/iceberg/pull/1970 # Launcher - Fix typo laucher into launcher #723 https://github.com/pharo-project/pharo-launcher/pull/723 # Command Line - allow clap command line handler to activate itself or not #18544 https://github.com/pharo-project/pharo/pull/18544 # Tools - Fix typo in ProfSteph #1244 https://github.com/pharo-spec/NewTools/pull/1244 - Update Graph Algorithms version #1249 https://github.com/pharo-spec/NewTools/pull/1249 - Fix release tests of Pharo #1248 https://github.com/pharo-spec/NewTools/pull/1248 - Update version of graph algorithms #1247 https://github.com/pharo-spec/NewTools/pull/1247 - Remove NewTools-ObjectCentricBreakpoints #1246 https://github.com/pharo-spec/NewTools/pull/1246 - Adding a new fetcher and fixing the transitive one #18580 https://github.com/pharo-project/pharo/pull/18580 - Fix #18557: Unexpected behavior when storing and loading code quality rule settings from files #18566 https://github.com/pharo-project/pharo/pull/18566 - Find and replace not stuck with old string anymore #18565 https://github.com/pharo-project/pharo/pull/18565 # Monticello / Metacello - Make #tagNames: on MCOrganizationDefinition ensure the tag names are symbols #18588 https://github.com/pharo-project/pharo/pull/18588 - Introduced MetacelloAbstractSpecGenerator #18593 https://github.com/pharo-project/pharo/pull/18593 - Remove Metacello dead code #18586 https://github.com/pharo-project/pharo/pull/18586 - Clean Metacello tests #18585 https://github.com/pharo-project/pharo/pull/18585 - Metacello cleanup #18569 https://github.com/pharo-project/pharo/pull/18569 - Small cleanup of Metacello/Monticello #18568 https://github.com/pharo-project/pharo/pull/18568 # Refactoring Engine - Fixed the duplicate class refactoring wrong message #17941 https://github.com/pharo-project/pharo/pull/17941 - [Refactorings] ReExtractMethodDriver complies with the architecture of drivers #18561 https://github.com/pharo-project/pharo/pull/18561 - Remove rb xxx #17970 https://github.com/pharo-project/pharo/pull/17970 # Cleanup - repackage tools needed for bootsrap #18567 https://github.com/pharo-project/pharo/pull/18567 - Fix a failing test #18581 https://github.com/pharo-project/pharo/pull/18581 - Remove tests of deprecated methods #18584 https://github.com/pharo-project/pharo/pull/18584 - Remove methods overriding the same methods in Pharo #1821 https://github.com/pharo-spec/Spec/pull/1821 - Remove duplicated ProfStef #18579 https://github.com/pharo-project/pharo/pull/18579

Sept. 26, 2025

UKSTUG Meeting: Esteban Lorenzano - Pharo 13 - 24 September 2025

by UK Smalltalk

Earlier this year, the Pharo development team announced the availability of Pharo 13 ( https://pharo.org/news/2025-05-21-pharo13-released.html ). For our September 2025 meeting, Pharo's release manager Esteban Lorenzano will give us a tour of the new version - what's changed, and what remains the same. Esteban Lorenzano ( https://github.com/estebanlm ) studied Computer Sciences at Universidad de Buenos Aires, and worked since 1994 in several object-oriented and low-level technologies, in different software companies, serving in various positions from programmer to senior architect. In 2007 he co-founded Smallworks to offer Pharo-based agile development projects. Since 2012 he dedicated full time to developing the Pharo code and community. He works with the INRIA-EVREF team in Lille, France, as core developer for Pharo, being responsible with the coordination of new releases and the implementation and maintenance of several Pharo libraries. This will be an online meeting. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/310635970/) to receive the meeting details.

Sept. 23, 2025

Pharo News of the Week 38/2025

by Marcus Denker

# Pharo News of the Week 38/2025 - [ANN] Ukrainian translation of "Application Building with Spec 2.0" https://pharo.org/news/2025-09-13-Spec-Ukr.html - [Blog Post] Cooperative Pharo server shutdown https://github.com/svenvc/blog/blob/main/2025-09-12-cooperative-server-shut… - AIActions â AI-based Comment Generator for Pharo https://github.com/kasperosterbye/PharoAIActions If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker - uFFI valueholder multiple arity (external objects) #18531 https://github.com/pharo-project/pharo/pull/18531 - Make #printOn: on Character not print surrogates as a literal #18540 https://github.com/pharo-project/pharo/pull/18540 # Comand Line - move spec run cli command to clap #18535 https://github.com/pharo-project/pharo/pull/18535 - Replace Fuel command line handler by clap command #18534 https://github.com/pharo-project/pharo/pull/18534 - move back perform as a root command #18542 https://github.com/pharo-project/pharo/pull/18542 - move to Clap #1819 https://github.com/pharo-spec/Spec/pull/1819 # Tools - Add inspector tab âFormSetâ showing a FormSet as an ImageMorph #1240 https://github.com/pharo-spec/NewTools/pull/1240 - Adding a setting to change default stack selection in debugger to show TestAsserter contexts when step Into #1242 https://github.com/pharo-spec/NewTools/pull/1242 # Icerberg / Git - Changing tabs when editing metadata project #1967 https://github.com/pharo-vcs/iceberg/pull/1967 - Use new Iceberg merge browser in more places instead of the morphic one #1941 https://github.com/pharo-vcs/iceberg/pull/1941 # Cleanup - Deprecate asSocketAddress extension #18556 https://github.com/pharo-project/pharo/pull/18556 - Cleaning of SystemVersion #18551 https://github.com/pharo-project/pharo/pull/18551 - Removing support for parsing styledsource code ]style[ #18541 https://github.com/pharo-project/pharo/pull/18541 - Removed duplicate classes in new DrTest #18536 https://github.com/pharo-project/pharo/pull/18536 - Move Fuel code to Fuel package #1243 https://github.com/pharo-spec/NewTools/pull/1243 # Website - add news fondation uni lille #108 https://github.com/pharo-project/pharo-website/pull/108 - news spec ukr #107 https://github.com/pharo-project/pharo-website/pull/107 - news Coypu Concert #106 https://github.com/pharo-project/pharo-website/pull/106

Sept. 22, 2025

Re: Explanation of do: separatedBy: keyword message

by RenePaulMages

Le 22/09/2025 Ã 10:42, Tim Mackinnon via Pharo-users a Ã©critÂ : > Hi Rene Paul -I hope my reply wasnât condescending. That wasnât the intent, but we sometimes find that students are asking you to do their homework and rather than a directly answering, itâs more instructive to try and help them reason on the code - particularly as Smalltalk is a language where you can reason on the code. Thank you Tim for your message. > > Anyway, I hope the concept of how a BlockClosure works has got you hooked (it was the light bulb moment for me, many years ago - and I still marvel at it today - itâs so elegant). > Pharo is effectively a _very_elegant_ language . -- All the best Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://wiki.linux-azur.org/?PagePHARO https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 22, 2025

Re: Explanation of do: separatedBy: keyword message

by Tim Mackinnon

Hi Rene Paul -I hope my reply wasnât condescending. That wasnât the intent, but we sometimes find that students are asking you to do their homework and rather than a directly answering, itâs more instructive to try and help them reason on the code - particularly as Smalltalk is a language where you can reason on the code. Anyway, I hope the concept of how a BlockClosure works has got you hooked (it was the light bulb moment for me, many years ago - and I still marvel at it today - itâs so elegant). Tim > On 19 Sep 2025, at 19:43, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > ï»¿Hi tim > > Rene Paul is long time follower of Pharo. He is now a retired mathematician and this is nice to see > him coding in Pharo :) > > S > >> On 18 Sep 2025, at 09:49, Tim Mackinnon via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> Hi - is this a homework question? While anyone here can tell you what it does - its probably more helpful to you to work through it and properly understand it. >> >> You haven't shown what the output is when you try it - which will give you a clue. Equally - in Smalltalk, the names of selectors like: #do:separatedBy: convey meaning (which is why we like to use good names, that hint at what parameters do). Finally - have you looked at the implementation of the method? The nice thing about Smalltalk is that there is very little magic - you can see the code that runs for operations - including things like #ifTrue: . Why don't you position your cursor on #do: and press ctrl-m (or cmd-m - for show iMplementors - its also in the context menu). This will let you see the code and you should be able to work it out. For fun - try doing the same for: 3 = 3 ifTrue: [ 1 + 1]. Finally - its also worth understanding [1+1] + 1 (and why it gives an error) whereas: [1+1] value + 1 dosn't. >> >> Hope this helps. >> >> Tim >> >>> On Thu, 18 Sep 2025, at 12:35 AM, Rene Paul Mages (ramix) via Pharo-users wrote: >>> Hello, >>> >>> Please give me a hint to understand the "do: separatedBy:" keyword >>> message used in ProfStef tutorial : >>> >>> i) in Pharo version 12 : >>> >>> https://ramix.org/pharo/ProfStef/iterators23.png >>> >>> ii) in Pharo version 13 : >>> >>> https://ramix.org/pharo/ProfStef/iterators25.png >>> >>> -- >>> Thanks for your help. >>> Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 >>> https://sites.google.com/view/les-logiciels-libres/pharo >>> https://twitter.com/RenePaulMages > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > > > > >

Sept. 22, 2025

Re: Explanation of do: separatedBy: keyword message

by Rene Paul Mages (ramix)

Le 19/09/2025 Ã 20:47, stephane ducasse a Ã©critÂ : > Hello Rene Paul > > compare > > | res | > res := OrderedCollection new. > #($a $b $c) do: [:aChar | res add: aChar]. > res > > an OrderedCollection($a $b $c) > > | res | > res := OrderedCollection new. > #($a $b $c) do: [:aChar | res add: aChar; add: $,]. > res > > an OrderedCollection($a $, $b $, $c $,) > > > and > > | res | > res := OrderedCollection new. > #($a $b $c) do: [:aChar | res add: aChar] separatedBy: [res add: $,]. > res > > an OrderedCollection($a $, $b $, $c) These comparisons are very enlightening. Thank you very much Stephane. -- All the best Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 https://sites.google.com/view/les-logiciels-libres/pharo https://twitter.com/RenePaulMages

Sept. 19, 2025

Re: Explanation of do: separatedBy: keyword message

by stephane ducasse

Hello Rene Paul compare | res | res := OrderedCollection new. #($a $b $c) do: [:aChar | res add: aChar]. res an OrderedCollection($a $b $c) | res | res := OrderedCollection new. #($a $b $c) do: [:aChar | res add: aChar; add: $,]. res an OrderedCollection($a $, $b $, $c $,) and | res | res := OrderedCollection new. #($a $b $c) do: [:aChar | res add: aChar] separatedBy: [res add: $,]. res an OrderedCollection($a $, $b $, $c) > On 18 Sep 2025, at 02:59, Rene Paul Mages (ramix) via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > Le 18/09/2025 Ã 01:35, Rene Paul Mages (ramix) via Pharo-users a Ã©crit : >> Hello, >> Please give me a hint to understand the "do: separatedBy:" keyword message used in ProfStef tutorial : >> i) in Pharo version 12 : >> https://ramix.org/pharo/ProfStef/iterators23.png >> ii) in Pharo version 13 : >> https://ramix.org/pharo/ProfStef/iterators25.png > > I am using the FINDER to search do:separatedBy: > > and also the BROWSER ( Method: Collection>>do:separatedBy: ) > > https://ramix.org/pharo/ProfStef/MethodCollection.png > > but I don't understand the explanations. > > Nota Bene : > > I am rereading the chapter 9 (Collections) of Pharo_By_Example : > > https://scg.unibe.ch/download/pharobyexample/PBE1-2010-02-01.pdf > > -- > Thanks for your help. > Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 > https://sites.google.com/view/les-logiciels-libres/pharo > https://twitter.com/RenePaulMages StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Sept. 19, 2025

Re: Explanation of do: separatedBy: keyword message

by stephane ducasse

Hi tim Rene Paul is long time follower of Pharo. He is now a retired mathematician and this is nice to see him coding in Pharo :) S > On 18 Sep 2025, at 09:49, Tim Mackinnon via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi - is this a homework question? While anyone here can tell you what it does - its probably more helpful to you to work through it and properly understand it. > > You haven't shown what the output is when you try it - which will give you a clue. Equally - in Smalltalk, the names of selectors like: #do:separatedBy: convey meaning (which is why we like to use good names, that hint at what parameters do). Finally - have you looked at the implementation of the method? The nice thing about Smalltalk is that there is very little magic - you can see the code that runs for operations - including things like #ifTrue: . Why don't you position your cursor on #do: and press ctrl-m (or cmd-m - for show iMplementors - its also in the context menu). This will let you see the code and you should be able to work it out. For fun - try doing the same for: 3 = 3 ifTrue: [ 1 + 1]. Finally - its also worth understanding [1+1] + 1 (and why it gives an error) whereas: [1+1] value + 1 dosn't. > > Hope this helps. > > Tim > > On Thu, 18 Sep 2025, at 12:35 AM, Rene Paul Mages (ramix) via Pharo-users wrote: >> Hello, >> >> Please give me a hint to understand the "do: separatedBy:" keyword >> message used in ProfStef tutorial : >> >> i) in Pharo version 12 : >> >> https://ramix.org/pharo/ProfStef/iterators23.png >> >> ii) in Pharo version 13 : >> >> https://ramix.org/pharo/ProfStef/iterators25.png >> >> -- >> Thanks for your help. >> Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 >> https://sites.google.com/view/les-logiciels-libres/pharo >> https://twitter.com/RenePaulMages StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Sept. 19, 2025

Re: Creation of a class help

by Cyril FERLICOT-DELBECQUE

Hi, Object and ProtocObject are not packages but classes. You can find them in multiple ways: - Using the Spotter (CMD/Ctrl + space) - Using the Finder (Browse -> Finder) - Using the class finder (In the Code Browser you can right click on a package and select "Find class" - By typing the name of the class in a Playground and doing CMD/CTRL + b to browse the class Those classes are in the Kernel package -- Cyril Ferlicot-Delbecque https://ferlicot.fr On Friday, September 19th, 2025 at 3:36 PM, RenePaulMages via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > Hello, > > I am restuding the chapter 5 ( Developing a simple counter ) of > " Learning OOP " book : > > http://files.pharo.org/books-pdfs/learning-oop/2018-04-01-LearningOOP.pdf > > In the browser of Pharo version 13 I can't find neither the Object > package nor the ProtoObject package. > > -- > Thanks for your help > Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 > https://wiki.linux-azur.org/?PagePHARO > https://renemages.wordpress.com/smalltalk/pharo > https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 19, 2025

Creation of a class help

by RenePaulMages

Hello, I am restuding the chapter 5 ( Developing a simple counter ) of " Learning OOP " book : http://files.pharo.org/books-pdfs/learning-oop/2018-04-01-LearningOOP.pdf In the browser of Pharo version 13 I can't find neither the Object package nor the ProtoObject package. -- Thanks for your help Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://wiki.linux-azur.org/?PagePHARO https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 19, 2025

Re: Explanation of do: separatedBy: keyword message

by RenePaulMages

Le 18/09/2025 Ã 10:30, Richard O'Keefe via Pharo-users a Ã©critÂ : Thank you Richard and Tim for your help. > The ANSI Smalltalk standard has this to say: > do: operation separatedBy: separator > For each element of the receiver, operation is evaluated with the element > as the parameter. > Before evaluating operation the second and subsequent times, evaluate > separator. > Separator is not evaluated if there are no elements or after the last > element. I understand now. > We could implement this in Collection like so: > > do: doBlock separatedBy: separatorBlock > |started| > started := false. > self do: [:each | > started ifTrue: [separator value] ifFalse: [started := true]. > doBlock value: each]. > > You can look at the actual source code by typing > do:separatedBy: > in a Playground (Workspace) and then typing Ctrl-M (show iMplementors). Ok. > The idea is simple enough: aCollection do: aBlock separatedBy: > separatorBlock > invokes (aBlock value: x1) ... (aBlock value: xn) where x1 ... xn are the > elements of aCollection, but *between* each pair of calls to aBlock there is > an invocation of (separatorBlock value). Now I understand the idea. > A good thing to do after you have looked at the implementation(s) is to look > at how it's used. Type do:separatedBy: > into a Playground and type Ctrl-N (show seNders). It's almost always > printing or concatenating with a separator. > And that is EXACTLY what is happening in the ProfStef tutorial you show. Perfect. > Let's take a simple example. > Suppose you have a string 'abcd'. > If you want to write /a/b/c/d > string do: [:each | aStream nextPut: $/; nextPut: each]. > If you want to write a/b/c/d/ > string do: [:each | aStream nextPut: each; nextPut: $/]. > So far so good, there are exactly as many / writes as there are element > writes, > so they can go in the same block. But if you want to write a/b/c/d what do > you do? > Now you have one FEWER separator than elements. > > string do: [:each | aStream nextPut: each] separatedBy: [aStream nextPut:$/] > does the trick. You could of course bodge something together yourself, > BUT #do:separatedBy: is a well known idiom so it is much easier for people > to understand. It is clear now. > > Another approach would have been > > Collection >>doFirst: firstBlock thenDo: otherBLock > |started| > started := false. > self do: [:each | > started ifTrue: [otherBlock value: each] ifFalse: [firstBlock value: > each. started := true]]. > > and then we could write > > aString doFirst: [:first | aStream nextPut: first] thenDo: [:each | > aStream nextPut: $/; nextPut: each] > > but that would involve code duplication, so we use #do:separatedBy: instead. Your explanation is _very_ complete. -- Thanks for your help. Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo https://twitter.com/RenePaulMages

Sept. 18, 2025

Re: Explanation of do: separatedBy: keyword message

by Richard O'Keefe

The ANSI Smalltalk standard has this to say: do: operation separatedBy: separator For each element of the receiver, operation is evaluated with the element as the parameter. Before evaluating operation the second and subsequent times, evaluate separator. Separator is not evaluated if there are no elements or after the last element. We could implement this in Collection like so: do: doBlock separatedBy: separatorBlock |started| started := false. self do: [:each | started ifTrue: [separator value] ifFalse: [started := true]. doBlock value: each]. You can look at the actual source code by typing do:separatedBy: in a Playground (Workspace) and then typing Ctrl-M (show iMplementors). The idea is simple enough: aCollection do: aBlock separatedBy: separatorBlock invokes (aBlock value: x1) ... (aBlock value: xn) where x1 ... xn are the elements of aCollection, but *between* each pair of calls to aBlock there is an invocation of (separatorBlock value). A good thing to do after you have looked at the implementation(s) is to look at how it's used. Type do:separatedBy: into a Playground and type Ctrl-N (show seNders). It's almost always printing or concatenating with a separator. And that is EXACTLY what is happening in the ProfStef tutorial you show. Let's take a simple example. Suppose you have a string 'abcd'. If you want to write /a/b/c/d string do: [:each | aStream nextPut: $/; nextPut: each]. If you want to write a/b/c/d/ string do: [:each | aStream nextPut: each; nextPut: $/]. So far so good, there are exactly as many / writes as there are element writes, so they can go in the same block. But if you want to write a/b/c/d what do you do? Now you have one FEWER separator than elements. string do: [:each | aStream nextPut: each] separatedBy: [aStream nextPut: $/] does the trick. You could of course bodge something together yourself, BUT #do:separatedBy: is a well known idiom so it is much easier for people to understand. Another approach would have been Collection >> doFirst: firstBlock thenDo: otherBLock |started| started := false. self do: [:each | started ifTrue: [otherBlock value: each] ifFalse: [firstBlock value: each. started := true]]. and then we could write aString doFirst: [:first | aStream nextPut: first] thenDo: [:each | aStream nextPut: $/; nextPut: each] but that would involve code duplication, so we use #do:separatedBy: instead. On Thu, 18 Sep 2025 at 11:35â¯AM, Rene Paul Mages (ramix) via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello, > > Please give me a hint to understand the "do: separatedBy:" keyword > message used in ProfStef tutorial : > > i) in Pharo version 12 : > > https://ramix.org/pharo/ProfStef/iterators23.png > > ii) in Pharo version 13 : > > https://ramix.org/pharo/ProfStef/iterators25.png > > -- > Thanks for your help. > Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 > https://sites.google.com/view/les-logiciels-libres/pharo > https://twitter.com/RenePaulMages > > >

Sept. 18, 2025

Re: Explanation of do: separatedBy: keyword message

by Tim Mackinnon

Hi - is this a homework question? While anyone here can tell you what it does - its probably more helpful to you to work through it and properly understand it. You haven't shown what the output is when you try it - which will give you a clue. Equally - in Smalltalk, the names of selectors like: #do:separatedBy: convey meaning (which is why we like to use good names, that hint at what parameters do). Finally - have you looked at the implementation of the method? The nice thing about Smalltalk is that there is very little magic - you can see the code that runs for operations - including things like #ifTrue: . Why don't you position your cursor on #do: and press ctrl-m (or cmd-m - for show iMplementors - its also in the context menu). This will let you see the code and you should be able to work it out. For fun - try doing the same for: 3 = 3 ifTrue: [ 1 + 1]. Finally - its also worth understanding [1+1] + 1 (and why it gives an error) whereas: [1+1] value + 1 dosn't. Hope this helps. Tim On Thu, 18 Sep 2025, at 12:35 AM, Rene Paul Mages (ramix) via Pharo-users wrote: > Hello, > > Please give me a hint to understand the "do: separatedBy:" keyword > message used in ProfStef tutorial : > > i) in Pharo version 12 : > > https://ramix.org/pharo/ProfStef/iterators23.png > > ii) in Pharo version 13 : > > https://ramix.org/pharo/ProfStef/iterators25.png > > -- > Thanks for your help. > Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 > https://sites.google.com/view/les-logiciels-libres/pharo > https://twitter.com/RenePaulMages

Sept. 18, 2025

Re: Explanation of do: separatedBy: keyword message

by Rene Paul Mages (ramix)

Le 18/09/2025 Ã 01:35, Rene Paul Mages (ramix) via Pharo-users a Ã©critÂ : > Hello, > > Please give me a hint to understand the "do: separatedBy:" keyword > message used in ProfStef tutorial : > > Â i) in Pharo version 12 : > > Â Â https://ramix.org/pharo/ProfStef/iterators23.png > > ii) in Pharo version 13 : > > Â Â https://ramix.org/pharo/ProfStef/iterators25.png I am using the FINDER to search do:separatedBy: and also the BROWSER ( Method: Collection>>do:separatedBy: ) https://ramix.org/pharo/ProfStef/MethodCollection.png but I don't understand the explanations. Nota Bene : I am rereading the chapter 9 (Collections) of Pharo_By_Example : https://scg.unibe.ch/download/pharobyexample/PBE1-2010-02-01.pdf -- Thanks for your help. Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 https://sites.google.com/view/les-logiciels-libres/pharo https://twitter.com/RenePaulMages

Sept. 18, 2025

Explanation of do: separatedBy: keyword message

by Rene Paul Mages (ramix)

Hello, Please give me a hint to understand the "do: separatedBy:" keyword message used in ProfStef tutorial : i) in Pharo version 12 : https://ramix.org/pharo/ProfStef/iterators23.png ii) in Pharo version 13 : https://ramix.org/pharo/ProfStef/iterators25.png -- Thanks for your help. Rene Paul Mages (ramix) GnuPG key : 0x9840A6F7 https://sites.google.com/view/les-logiciels-libres/pharo https://twitter.com/RenePaulMages

Sept. 18, 2025

Re: installation of Pharo on a Linux/ubuntu laptop

by RenePaulMages

Le 15/09/2025 Ã 14:50, Noury Bouraqadi a Ã©critÂ : > Salut RenÃ©, > > It's been a while since I installed Pharo on a Linux machine. > But, from what I understand, the last step is to unpack the tar > > tar vxf pharo-launcher-linux.tar A great thank you dear Noury : tar is effectively the ad hoc command to start the pharo-launcher. > Then, you'll be able to start the Pharo Launcher, that allows creating and > managing your images and VMs. > > May the Smalltalk force be with you ;-) > Noury -- All the best Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://wiki.linux-azur.org/?PagePHARO https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 15, 2025

Re: installation of Pharo on a Linux/ubuntu laptop

by Noury Bouraqadi

Salut RenÃ©, It's been a while since I installed Pharo on a Linux machine. But, from what I understand, the last step is to unpack the tar tar vxf pharo-launcher-linux.tar Then, you'll be able to start the Pharo Launcher, that allows creating and managing your images and VMs. May the Smalltalk force be with you ;-) Noury On Mon, Sep 15, 2025 at 1:27â¯PM RenePaulMages via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > Le 15/09/2025 Ã 11:16, RenePaulMages via Pharo-users a Ã©crit : > > Hello, > > > > My laptop is running Ubuntu 24.04 : > > > > https://doc.ubuntu-fr.org/noble > > > > After the download step : > > > > https://files.pharo.org/pharo-launcher/linux64 > > > > I am stuck with the following file : > > > > PharoLauncher-linux-3.4.1-x64.zip > > From this unzip point I am ~lost~ : > > rmages@lenovo:~/Pharo$ unzip ./PharoLauncher-linux-3.4.1-x64.zip > Archive: ./PharoLauncher-linux-3.4.1-x64.zip > creating: artifacts/PharoLauncher-linux-3.4.1-x64/ > inflating: > artifacts/PharoLauncher-linux-3.4.1-x64/pharo-launcher-linux.tar > > -- > All the best > Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 > https://wiki.linux-azur.org/?PagePHARO > https://renemages.wordpress.com/smalltalk/pharo > https://sites.google.com/view/les-logiciels-libres/pharo > > > -- Noury Bouraqadi

Sept. 15, 2025

Re: installation of Pharo on a Linux/ubuntu laptop

by RenePaulMages

Le 15/09/2025 Ã 11:16, RenePaulMages via Pharo-users a Ã©critÂ : > Hello, > > My laptop is running Ubuntu 24.04 : > > https://doc.ubuntu-fr.org/noble > > Â Â Â After the download step : > > https://files.pharo.org/pharo-launcher/linux64 > > Â Â Â I am stuck with the following file : > > PharoLauncher-linux-3.4.1-x64.zip From this unzip point I am ~lost~ : rmages@lenovo:~/Pharo$ unzip ./PharoLauncher-linux-3.4.1-x64.zip Archive: ./PharoLauncher-linux-3.4.1-x64.zip creating: artifacts/PharoLauncher-linux-3.4.1-x64/ inflating: artifacts/PharoLauncher-linux-3.4.1-x64/pharo-launcher-linux.tar -- All the best Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://wiki.linux-azur.org/?PagePHARO https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 15, 2025

installation of Pharo on a Linux/ubuntu laptop

by RenePaulMages

Hello, My laptop is running Ubuntu 24.04 : https://doc.ubuntu-fr.org/noble After the download step : https://files.pharo.org/pharo-launcher/linux64 I am stuck with the following file : PharoLauncher-linux-3.4.1-x64.zip -- Thanks for your help Rene Paul Mages (ramix) GnuPG : 0x9840A6F7 https://wiki.linux-azur.org/?PagePHARO https://renemages.wordpress.com/smalltalk/pharo https://sites.google.com/view/les-logiciels-libres/pharo

Sept. 15, 2025

Pharo News of the Week 37/2025

by Marcus Denker

# Pharo News of the Week 37/2025 - [ANN] Live Coding and Djselecta with Lucretio + Coypu 18/09/2025 https://pharo.org/news/2025-09-12-Concert-Coypu.html - [ANN] Pharo Consortium New Academic Member EMIT University of Fianarantsoa https://pharo.org/news/2025-09-11-Consortium-emit.html - [ANN] Fondation UniversitÃ© de Lille: Pharo selected as supported project for the Call 2024: https://fondation.univ-lille.fr/projets/les-projets-en-cours/soutenir-les-e… - SJsonPath is a Smalltalk library that provides a fluent API for creating JsonPath expression strings https://github.com/mumez/SJsonPath If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Fixes - Update POP3Client.class.st, use allButFirst #18523 https://github.com/pharo-project/pharo/pull/18523 # Command Line - Replace clean and save commands by their clap version #18525 https://github.com/pharo-project/pharo/pull/18525 - add test runner clap command #18521 https://github.com/pharo-project/pharo/pull/18521 - Replace metacello command line handler by clap command #18517 https://github.com/pharo-project/pharo/pull/18517 # FFI - FFI valueholder multiple arity: support returning array of structures #18479 https://github.com/pharo-project/pharo/pull/18479 # Tools - Fix syntax of "packages selected" for the finder #1238 https://github.com/pharo-spec/NewTools/pull/1238 - [Refactorings] Removing dependencies on NautilusRefactoring #18524 https://github.com/pharo-project/pharo/pull/18524 # Website - add consortium emit #105 https://github.com/pharo-project/pharo-website/pull/105

Sept. 12, 2025

[ANN] Pharo Consortium New Academic Member: EMIT University of Fianarantsoa

by Marcus Denker

The Pharo Consortium is very happy to announce that EMIT University of Fianarantsoa has joined the Consortium as an Academic Member. About - EMIT University of Fianarantsoa: https://www.emit.mg <https://www.emit.mg/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> Individuals can support Pharo via the Pharo Association https://association.pharo.org <https://association.pharo.org/>

Sept. 12, 2025

Re: A couple of newb questions

by Noury Bouraqadi

Hi Will, For changing the scale factor on Pharo 12, the simplest option is to evaluate the following in a Playground: World scaleFactor: 1.3. But, the fonts become ugly. On latest Pharo, the settings tools allow to change and the scaling with better results. Though I didn't test it. Noury On Mon, Sep 8, 2025 at 7:25â¯AM Will Senn via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hi all, > > I'm brand new to pharo. I'm hoping y'all can help with a couple of > beginner questions... > > 1) I'm running on debian 13 trixie. With Pharo 12, 13 or 14, the fonts > are very tiny on my 2560x1440 display. What's the best way to make menus > and text bigger. I tried a scale factor, but it looks ugly. If that's > the recommended solution, fine. I can live with it, but I want to do it > the right way. > > 2) The open url functions don't work. I get XPCOMGlueLoad errors: > > XPCOMGlueLoad error for file /usr/lib/firefox-esr/libmozgtk.so: > /lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: > hb_ot_color_has_paint > Couldn't load XPCOM > > It seems like this is an incompatible library issue. Is there a way to > set another browser (I'm using Firefox) as the one pharo uses? I have > several including opera and chrome. > > Thanks, > > Will > -- Noury Bouraqadi

Sept. 8, 2025

A couple of newb questions

by Will Senn

Hi all, I'm brand new to pharo. I'm hoping y'all can help with a couple of beginner questions... 1) I'm running on debian 13 trixie. With Pharo 12, 13 or 14, the fonts are very tiny on my 2560x1440 display. What's the best way to make menus and text bigger. I tried a scale factor, but it looks ugly. If that's the recommended solution, fine. I can live with it, but I want to do it the right way. 2) The open url functions don't work. I get XPCOMGlueLoad errors: XPCOMGlueLoad error for file /usr/lib/firefox-esr/libmozgtk.so: /lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: hb_ot_color_has_paint Couldn't load XPCOM It seems like this is an incompatible library issue. Is there a way to set another browser (I'm using Firefox) as the one pharo uses? I have several including opera and chrome. Thanks, Will

Sept. 8, 2025

Pharo News of the Week 36/2025

by Marcus Denker

# Pharo News of the Week 36/2025 [Wanted] Pharo News. If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 13 - [Backport] Improve folder selection in the File Browser #1232 https://github.com/pharo-spec/NewTools/pull/1232 # Fixes - Fixes #18482 Cannot push up a class var. #18504 https://github.com/pharo-project/pharo/pull/18504 - Allow to set tabs priority in Iceberg #18499 https://github.com/pharo-project/pharo/pull/18499 - Fixing ThemeIcons #18496 #18497 https://github.com/pharo-project/pharo/pull/18497 - Make path asFileReference for Roassal examples #18441 https://github.com/pharo-project/pharo/pull/18441 # Tools - Fix #1140: [Finder] Feature request: Allow saving edited method code #1215 https://github.com/pharo-spec/NewTools/pull/1215 - Fixing 18505: Pulse is not working #1236 https://github.com/pharo-spec/NewTools/pull/1236 - Do not use UIManager in ProtocolNameChooser #1235 https://github.com/pharo-spec/NewTools/pull/1235 - Fix bug in file presenter in case a folder is empty #1234 https://github.com/pharo-spec/NewTools/pull/1234 - Improve folder selection in the File Browser #1231 https://github.com/pharo-spec/NewTools/pull/1231 - [Finder] Feature request: Allow saving edited method code #1140 https://github.com/pharo-spec/NewTools/issues/1140 - Make sure that we could have the completion working on the local clasâ¦ #18516 https://github.com/pharo-project/pharo/pull/18516 - First version of a driver for InsertSubclassDriver #18495 https://github.com/pharo-project/pharo/pull/18495 # Spec - Add tests for gh-1735 #1817 https://github.com/pharo-spec/Spec/pull/1817 - Demo classes renamed to match better their purpose. #1816 https://github.com/pharo-spec/Spec/pull/1816 - Fix Active presenter of a Notebook is not available in the #whenSelectedTabChangedDo: #1815 https://github.com/pharo-spec/Spec/pull/1815 - latest changes #1814 https://github.com/pharo-spec/Spec/pull/1814 - A fixed-width or fixed-height SpBoxLayout should not grow or shrink when adding or removing presenters #1813 https://github.com/pharo-spec/Spec/pull/1813 # Command Lime - Add tests for Pharo command line #18473 https://github.com/pharo-project/pharo/pull/18473 - replace st and eval command line handlers by clap commands #18514 https://github.com/pharo-project/pharo/pull/18514 - add invalid code evaluation cli tests #18512 https://github.com/pharo-project/pharo/pull/18512 # Cleanup - Deprecate MailComposition that is in Morphic #18509 https://github.com/pharo-project/pharo/pull/18509 - Reduce the number of extensions in the system #18501 https://github.com/pharo-project/pharo/pull/18501

Sept. 5, 2025