- Pharo-dev - lists.pharo.org

"Steps for Interaction with Spec Presenters in Hera â New blog post on all: objects all: theTime
by Koen De Hondt March 14, 2026

March 14, 2026

Dear Pharo users and developers, I posted a third article in the series about describing Spec application behaviour with Hera. The first post explained how Hera manages open Spec windows. The second post explained how Hera identifies presenters so they can be referenced in Gherkin scenarios. This post explains how Hera expresses steps to interact with Spec presenters. https://all-objects-all-the-time.st/#/blog/posts/22 As always, all feedback is welcome. Happy reading! Ciao, Koen

1 0

[ANN] Soil version 4
by Norbert Hartl March 12, 2026

March 12, 2026

We are happy to announce the availability of Soil version 4. What is new? Indexes (both skip list and Btree+) now have forward and backward pointer (those have been added) so there is new possibilities to have indexes that are traversable in each direction. This needed to be done in a not backward-compatible way. All databases prior to v4 need to be migrated. A migration procedure is available at https://github.com/ApptiveGrid/Soil/blob/main/docs/versions/migration.md The indexes prior to v4 have been implemented closely to the interface and behavior of a Dictionary. We've added support for duplicated keys which is necessary when doing secondary indexes. A lot of the changes in v4 are regarding to that because it changed quite a bit how things work. NOTE: duplicate keys are considered a preview in v4. They should be usable but might need to settle a bit more. Until now there is no feature supported making use of duplicated keys. Indexes have unique keys as default. They resemble the old behavior and should just work as before journals are now used by a transaction right from the start and creates it while the code operates on it. This way we could remove all brittle intermediate dictionaries like newValues, removedValues in the handling which improved the code a lot There is a first version of read-only transactions where one can make sure every attempt to write to the database should end up in an error There is also a first version of a graph exporter and importer. This can export a graph on the database level which works even if the application code is not present. This is useful for copying or moving a sub-graph from one database to another in an efficient way. There are plenty of code cleanups and performance improvements. The more detailled view can be seen here: https://github.com/ApptiveGrid/Soil/blob/main/docs/versions/changelog-v4.md What is planned for v5? Multi-index collection. This resembles what most other database have. You have one list of objects but multiple indexes to the same data in order to speed up search for different use cases partial indexes. These is a special kind of view to a database index. It consists of a predicate and stores only the elements that pass the predicate. Searching is way faster and things like size are almost for free windows support. There has been a PR provided https://github.com/ApptiveGrid/Soil/pull/980 which needs to be fixed as the way soil handles streams is not compatible with windows If all goes well we will remove the need for the markDirty: calls completely. Cluster modification tracking will then be automatic and removes a huge annoyance when using soil Hope you like it. Give it a spin and then tell us! Norbert & Marcus

1 0

Fwd: New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more
by stephane ducasse March 12, 2026

March 12, 2026

> Begin forwarded message: > > From: LABORDE Pierre <pierre.laborde(a)fr.thalesgroup.com> > Subject: RE: New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more > Date: 12 March 2026 at 09:27:11 CET > To: MartÃn Dias <tinchodias(a)gmail.com>, lse-openbloc <lse-openbloc(a)inria.fr> > Reply-To: LABORDE Pierre <pierre.laborde(a)fr.thalesgroup.com> > > De : lse-openbloc-request(a)inria.fr <mailto:lse-openbloc-request@inria.fr> <lse-openbloc-request(a)inria.fr <mailto:lse-openbloc-request@inria.fr>> De la part de MartÃn Dias > EnvoyÃ© : jeudi 12 mars 2026 02:01 > Ã : lse-openbloc <lse-openbloc(a)inria.fr <mailto:lse-openbloc@inria.fr>> > Objet : New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more > > Hello! the following are the new releases in Bloc/Toplo projects: > > Bloc v2.8.0 <https://github.com/pharo-graphics/Bloc/releases/tag/v2.8.0> > â¢ Fix code styling error in Pharo 14 by @tinchodias in #839 > â¢ Move TBlLayoutResizable to Bloc-Layouts-Support package by @plantec in #834 > â¢ Fix deprecated message send by @tinchodias in #845 > â¢ Send #waitTimeoutMilliseconds: instead of #wait: to Semaphore by @tinchodias in #847 > â¢ Generate baseline with explicit requirements to avoid loading warnings by @tinchodias in #832 > > Toplo v0.9.0 <https://github.com/pharo-graphics/Toplo/releases/tag/v0.9.0> > â¢ Circular menu by @plantec in #368 > â¢ List hierarchy refactoring by @plantec in #360 > â¢ Move defaultNodeFactory to the root abtract class by @plantec in #358 > â¢ Finite data source manager ng by @plantec in #362 > â¢ Simplified node configuration by @plantec in #363 > â¢ List node configuration by @plantec in #365 > â¢ Checkbox selection refactoring by @plantec in #366 > â¢ Improved ToInfiniteListElementEventHandler to fixe selection update iâ¦ by @plantec in #367 > â¢ Make #class: and #iconImageFor: on ToExMiniBrowserClassNodeContent use the FormSet for each of the icons by @Rinzwind in #329 > â¢ Investigating list selection management by @plantec in #370 > â¢ Fix some circular dependencies by @tinchodias in #371 > > Spec-Toplo v0.9.0 <x-msg://28/Spec-Toplo/releases/tag/v0.9.0> > â¢ Diff adapter, begin miler layout, fix selection tree table by @badetitou in #46 > â¢ Improve Code Editor by @badetitou in #47 > â¢ Toplo file selector by @badetitou in #49 > â¢ Add keyshortcut to main window by @badetitou in #50 > â¢ Improve small aspect issue by @badetitou in #51 > â¢ Miller layout by @badetitou in #52 > â¢ Little cleanups by @tinchodias in #53 > â¢ Fix to do list demo by @tinchodias in #81 > â¢ Add a Spec adapter for SpBlocPresenter to the Morphic backend by @tinchodias in #83 > â¢ Load proper group of Roassal by @tinchodias in #86 > â¢ Load Roassal package not baseline by @tinchodias in #88 > > Alexandrie v2.8.0 <https://github.com/pharo-graphics/Alexandrie/releases/tag/v2.8.0> > â¢ Add binding for hb_version_atleast and use it by @tinchodias in #121 > â¢ Cairo context's #newContextDo: initialize the surface > > Album v0.9.0 <https://github.com/pharo-graphics/Albumv0.9.0> > â¢ Few changes needed by Toplo by @plantec in #54 > â¢ Add AlbEditorElement>>lineIndexAtTextIndex: by @plantec > â¢ fixes #infiniteDo: to return the result of the block > â¢ Remove TBlLayoutResizable uses since it is used by BlElement > â¢ The cursor was not blinking by default > > PharoSDL3 <https://github.com/pharo-graphics/PharoSDL3/releases/tag/v0.0.2> > 102 commits in 2026: https://github.com/pharo-graphics/PharoSDL3/compare/964543a2cd6ac278fd208c3… > > > Best regards, > MartÃn

1 0

[Job] Smalltalk job in Glasgow, UK
by Mike Roberts Feb. 26, 2026

Feb. 26, 2026

Here is a new job opportunity to work on the Kapital Smalltalk system in Glasgow, UK. https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001/… If you are interested, please apply through the website. Kind regards, Mike

2 1

"Presentation at ESUG'25" â New blog post on all: objects all: theTime
by Koen De Hondt Feb. 24, 2026

Feb. 24, 2026

Dear Pharo users and developers, The Pharo team has posted the recorded presentations of ESUG 2025 on YouTube <https://www.youtube.com/@esugboard/videos>. I collected links to the slides and the video of my presentation about Hera in a short blog post. https://all-objects-all-the-time.st/#/blog/posts/21 Best regards, Koen

1 0

Call for Presentation for ESUG 2026
by stephane ducasse Feb. 20, 2026

Feb. 20, 2026

Hello Happy Smalltalkers Here is the call for presentation for ESUG 2026. The ESUG board is pleased to announce Call for presentations at the 31th ESUG conference to be held in Plovdiv, Bulgaria 7 - 10 July 2026. We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hand-ons tutorial. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - Micro Services, Container, Cloud, Big Data, - XP practices, Development tools, Experience reports - Model driven development, Web development, Team management - Meta-Modeling, Security, New libraries and frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls - Show us Your Business - Show your business 10 min session (Get prepared!!) ## How to submit? - Submission deadline is 1st of May 2026 - Notification of acceptance will be on done on the fly. Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a Pull Request on *https://github.com/ESUG/esug.github.io/tree/source/2026-Conference/talks>https://github.com/ESUG/esug.github.io/tree/source/2026-Conference/talks* If you do not succeed to do a PR you can send an email to <omar.abedelkader(a)inria.fr> and <stephane.ducasse(a)inria.fr> with [ESUG2026] in the title = Title: Please follow the template below the email will be automatically processed! = Name: = Email: = Abstract: = Bio: Any presentation not respecting this form will be discarded automatically.

1 1

"Identifying Spec Presenters in Hera" â New blog post on all: objects all: theTime
by Koen De Hondt Feb. 19, 2026

Feb. 19, 2026

Dear Pharo users and developers, I posted a second article in the series about describing Spec application behaviour with Hera. The first post explained how Hera manages open Spec windows. The new post explains how Hera identifies presenters so they can be referenced in Gherkin scenarios. https://all-objects-all-the-time.st/#/blog/posts/20 As always, all feedback is welcome. Happy reading! Ciao, Koen

2 2

A Pharo-LLM organization
by omar abedelkader Feb. 13, 2026

Feb. 13, 2026

Hello All, I have created an organization specialized in all the tools, specialized in providing a set of tools for using Large Language Models (LLMs) inside the Pharo There are already multiple projects there, like an inference engine inside Pharo instead of working on external APIs like Ollama, LM Studio, in this way, you have all the model capability in your hand :) There is pharo-mcp server that implements the MCP server inside Pharo :) and many more. https://github.com/pharo-llmï¿¼ Pharo-LLM github.com â Omar AbedelKader https://github.com/pharo-llm

1 0

LLM which coder is best?
by John M McIntosh Feb. 13, 2026

Feb. 13, 2026

Updated our release of ClaudeSmalltalk today to better support the OpenAI codex models, and added xAI support. Any Pharo developer who would like to assist in altering the code base to support Pharo? In asking the various LLM models to explain for example the class 'FMSound' I found that xAI Grok 4.1 Fast gave the best answer as compared to OpenAI, Anthropic, and Qwen. It is significantly cheap too. https://github.com/CorporateSmalltalkConsultingLtd/ClaudeSmalltalk/releases… .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

3 2

Re: [Pharo-users] [Ann] BPatterns: The rewrite engine at your fingertips
by Denis Kudriashov Feb. 10, 2026

Feb. 10, 2026

Hi Richard. I checked the code and the double backticks are for the recursion mode. It forces the search to dive into the current matching node to find more cases inside it. For example: (instVar isNil ifTrue: [ 'inside recursion' ]) isNil ifTrue: [ 'outer node' ] The syntax with single backtick will not find the internal "instVar isNil" expression. In BPatterns the recursion mode is enabled by default for the pattern variables. So the default mode covers the maximum scope for a search. Currently you can't not disable the #recurseInto flag as there is not suitable accessor for this. But if it would be there the pattern would like: [ anyVar isNil ifTrue: anyBlock ] bpattern with: [ anyVar ] -> [:pattern | pattern recurseInto: false ] Anyway I adjusted my blog accordingly. Thanks for the attention. Ð²Ñ, 3 ÑÐµÐ²Ñ. 2026â¯Ð³. Ð² 10:47, Richard O'Keefe <raoknz(a)gmail.com>: > Thank you. One of the reasons given for introducing BPatterns is a subtle > difference between > single backticks and double backticks, which is mentioned but not > explained in the BPatterns > blog entry. The help screen you directed me to does not explain that. > > Is there any documentation which is *complete* and *proofread*? > > On Tue, 3 Feb 2026 at 23:16, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Yes. There is nice help presenter in the Pharo: >> >> StRewriterHelpBrowserPresenter new open >> >> >> [image: Screenshot 2026-02-03 at 10.15.45.png] >> >> >> Ð²Ñ, 3 ÑÐµÐ²Ñ. 2026â¯Ð³. Ð² 01:36, Richard O'Keefe <raoknz(a)gmail.com>: >> >>> Is the "classic" rewriting syntax documented anywhere? >>> >>> On Mon, 2 Feb 2026 at 22:52, Denis Kudriashov via Pharo-users < >>> pharo-users(a)lists.pharo.org> wrote: >>> >>>> Hi all. >>>> >>>> This is the release of *BPatterns* project, one of my old ideas on how >>>> to make the rewrite engine usable for scripting. >>>> >>>> As a quick reminder, here is an example of the classic rewrite-engine >>>> matching syntax: >>>> >>>> *``@receiver isNil ifTrue: ``@nilBlock* >>>> >>>> >>>> In practice, patterns like this usually live inside string >>>> literalsâhidden away in lint rules, deprecations, or refactorings. >>>> To use them for *manual* code search or rewriting, you typically need >>>> a dedicated tool. >>>> >>>> Now compare that with the same pattern expressed as a *BPattern*: >>>> >>>> *[ any isNil ifTrue: anyBlock ] bpattern* >>>> >>>> No special syntax. >>>> No magical tools. >>>> Just pure Smalltalk. >>>> >>>> You write a block. >>>> You send #bpattern. >>>> Youâre done. >>>> >>>> Every editor understands it. >>>> Every tool respects it. >>>> >>>> Want to see where this pattern appears? >>>> >>>> * [ any isNil ifTrue: anyBlock ] bpattern browseUsers* >>>> >>>> >>>> [image: Screenshot 2026-01-31 at 12.16.19.png] >>>> >>>> Want to rewrite all of them? >>>> >>>> *[[ any isNil ifTrue: anyBlock ] -> [ any ifNil: anyBlock ]] brewrite >>>> preview* >>>> >>>> >>>> [image: Screenshot 2026-01-31 at 12.17.57.png] >>>> >>>> Because *BPatterns are real Smalltalk code*, all development tools >>>> work out of the box: >>>> syntax highlighting, completion, navigation, refactorings. >>>> >>>> This is the rewrite engine treated as a *first-class citizen*. >>>> >>>> Not strings. >>>> Not tooling sidecars. >>>> Not just for advanced users. >>>> >>>> *A rewrite engine you can actually use.* >>>> * A rewrite engine at your fingertips.* >>>> More details are in the blog post: >>>> >>>> - >>>> https://dionisiydk.blogspot.com/2026/02/bpatterns-rewrite-engine-with-small… >>>> >>>> And follow the project on GitHub: >>>> >>>> - https://github.com/dionisiydk/BPatterns >>>> >>>> >>>> - >>>> >>>>

3 6