- Pharo-users - lists.pharo.org

Re: [Ann] New deprecations API

by Richard O'Keefe

Nice. What happens when there are uses of a deprecated method in files held in a repository but not currently loaded into the image? How does one get rewrite rules applied to a bunch of files? On Tue, 3 Feb 2026 at 11:22, Denis Kudriashov via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Following the release of *BPatterns > <https://github.com/dionisiydk/BPatterns>*, I am happy to share another > idea that naturally grows out of it: *simplifying deprecations in Pharo*. > > Todayâs deprecations are powerful but verboseâstring-based rewrite rules, > duplicated selectors, and boilerplate that most of us copy from examples. > > With BPatterns, all of this can be eliminated: > > Object>>confirm: queryString > ^ self *deprecatedBy: * [ ConfirmationRequest signal: queryString > ] > > Deprecation is now expressed in the same language as the code itself, not > in a separate, string-based mini-language. There is no need to think about > transformation rulesâthey are part of the system and enabled by default. > > Zero boilerplate. > No duplicated code > For more details and comparison with current API see the blog post: > > > - > https://dionisiydk.blogspot.com/2026/02/deprecations-as-they-should-be.html > >

Feb. 3, 2026

Re: [Ann] BPatterns: The rewrite engine at your fingertips

by Richard O'Keefe

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 > > > - > >

Feb. 3, 2026

[Ann] New deprecations API

by Denis Kudriashov

Following the release of *BPatterns <https://github.com/dionisiydk/BPatterns>*, I am happy to share another idea that naturally grows out of it: *simplifying deprecations in Pharo*. Todayâs deprecations are powerful but verboseâstring-based rewrite rules, duplicated selectors, and boilerplate that most of us copy from examples. With BPatterns, all of this can be eliminated: Object>>confirm: queryString ^ self *deprecatedBy: * [ ConfirmationRequest signal: queryString ] Deprecation is now expressed in the same language as the code itself, not in a separate, string-based mini-language. There is no need to think about transformation rulesâthey are part of the system and enabled by default. Zero boilerplate. No duplicated code For more details and comparison with current API see the blog post: - https://dionisiydk.blogspot.com/2026/02/deprecations-as-they-should-be.html

Feb. 2, 2026

Re: [Ann] BPatterns: The rewrite engine at your fingertips

by Richard Sargent

Excellent! That is so welcome!! On Mon, Feb 2, 2026, 04: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 > > > - > >

Feb. 2, 2026

[Ann] BPatterns: The rewrite engine at your fingertips

by Denis Kudriashov

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 -

Feb. 2, 2026

"Spec Window Management in Hera" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I started a series of posts about describing Spec application behaviour with Hera. The first post explains how Hera manages open Spec windows and describes the Gherkin steps involved with windows. https://all-objects-all-the-time.st/#/blog/posts/19 As always, all feedback is welcome. Happy reading! Ciao, Koen

Jan. 30, 2026

Re: [Pharo-dev] How to improve sharpiness of fonts

by Eliot Miranda

Jan. 28, 2026

How to improve sharpiness of fonts

by stephane ducasse

Hi guys Happy new year! I would like to share with you a need. I have different screens of different DPI and my view is not getting better. Now on retina the fonts are either too small (zoom 100) or too large (150) so I end up having blurry fonts. I would like to know if the situation could be improved with font that have a larger spectrum of sizes. May be using the fonts of the OS could help too. Any idea and help is welcome. S

Jan. 28, 2026

UKSTUG Meeting: Kasper Ãsterbye - AI Inside Pharo - 28 January 2026

by UK Smalltalk

This talk explores what it means to work with AI from inside a live Pharo system rather than treating AI as an external chatbot. I will demonstrate experiments where AI models are invoked directly from the Playground, including a concrete implementation of conversation history (AIAHistory) and experiments across multiple models and providers. Rather than focusing on code generation, the emphasis is on workflows: how different conversation structures affect results, how styles and constraints can be imposed on generated comments, and how AI systems can be inspected for systematic errors and limitations. Examples include documentation support, UML generation (via PlantUML), and experiments in automated paper review. The talk is experimental in nature and rooted in Smalltalkâs strengths: reflection, live objects, and tools that are part of the system rather than bolted on. The goal is not to present a finished framework, but to share concrete insights, failures, and possibilities for AI as a native Pharo tool. Kasper Ãsterbye ( https://github.com/kasperosterbye ) is a retired computer science researcher with a long background in programming languages and live systems, including decades of work with Smalltalk and Pharo. He now explores how AI models can be integrated as native tools inside a running Pharo system, focusing on conversation structure, systematic failures, and tool design rather than automation alone. 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/311265921/ ) to receive the meeting details.

Jan. 15, 2026

Master Internship sponsorship

by Noury Bouraqadi

Hi, My lab has funding for several Master's degree internship positions. These are likely to be the first step to PhD positions. - Topics are related to Software Engineering with applications to Robotics, IoT, Digital Twins, and AI - Duration: 5 months - Funding: about 630 euros / month - Location: Douai, Lille area (30km), France Application: send me a CV with a short email introducing yourself and your background. Best, Noury Bouraqadi IMT Nord Europe France

Jan. 15, 2026