December 2025 - Pharo-dev - lists.pharo.org

"Hera 1.1 â A Shipload of New Functionality" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I presented Hera, a BDD tool for Pharo, at ESUGâ25. That was version 1.0. I am happy to announce that version 1.1 is available. You can read about all new and improved functionality on https://all-objects-all-the-time.st/#/blog/posts/18. As always, all feedback is welcome. Happy reading! Ciao, Koen

Dec. 31, 2025

Looking for Metacello beta testers

by stephane ducasse

Hello Under the radar, we are actively continiously cleaning Pharo deep core so that we can work on new features. For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), and other loading features to support module experimentations. It will make Pharo code more robust in the long term. Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. Now the unit test coverage of metacello is quite low and we do not use/know all the features that are available and that you may rely on. So we would love to have beta testers that can just try to load their code in Pharo 14 alpha and report potential bugs or features drop we would have introduced. So do not hesitate and this is a nice way to help pharo S.

Dec. 29, 2025

Re: [DEBT 2026] Future Debugging Techniques Call for Papers, submission 7th of March 2026

by Kasper Osterbye

Go for it, Go for it. One of the many wonders of Pharo is how well the IDE is in all aspects, including debugging. â Kasper > On 24 Dec 2025, at 18.54, Steven Costiou <steven.costiou(a)inria.fr> wrote: > > > DEBT 2026: Call for Papers > > ================================================================================ > DEBT 2026, Workshop co-located with ECOOP 2026, Brussels, Belgium > Fourth Workshop on Future Debugging Techniques > (https://2026.ecoop.org/home/debt-2026#Call-for-Papers) > ================================================================================ > > Important Dates > ----------------------- > * Abstract submission deadline: Sat 28 Feb 2026 > * Paper submission deadline: Sat 7 Mar 2026 > * Author notification: Wed 15 Apr 2026 > * Workshop: Monday 29 June 2026 > > ================================================================================ > > DEBTâ26 is looking to advance state-of-the-art to debug modern software. We welcome researchers from all related areas aimed at helping with the hard task of diagnosing the root cause of bugs, including dynamic and static debugging techniques, online and postmortem debuggers, delta debugging, automatic bug finding, novel visualization techniques for debugging programs, etc. > > The workshop aims to gather the community and foster discussion from different perspectives. That is why we seek submissions in the form of papers as well as talks and tool demonstrations. > > The workshop is a venue for all approaches to debugging. A non-exclusive list of topics of interest is: > > Debugging techniques, from static to dynamic techniques. > Innovative visualisation techniques. > Techniques targeted specific programming models and execution models (e.g., concurrent and parallel programming, microservices, distributed ledgers, web, etc. ) or hardware (e.g., debugging micro-controllers, mobile devices, Big Data applications, etc.). > Case studies and evaluation of such techniques, e.g., user studies on visualisation tools, debuggers, etc. > Surveys, taxonomies of bugs and bug patterns, and current practices/uses of debugging approaches. > > > Papers must be formatted according to the guidelines for ACM sigplan papers (\documentclass[sigplan,screen]{acmart}), see https://www.sigplan.org/Resources/Author/ <https://www.sigplan.org/Resources/Author/> for details. > > Submissions should be made via Easychair using the following link: > https://easychair.org/conferences/?conf=debt2026 <https://easychair.org/conferences/?conf=debt2026> > The accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register for the workshop and attend the event to present the work, and participate in the discussions. > > > AUTHORS TAKE NOTE: > The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. > > Workshop Organizers > --------------------------- > > * Burcu Kulahcioglu Ozkan, Delft University of Technology, Netherlands > * Steven Costiou, Centre Inria de lâUniversitÃ© de Lille, France > > For more information see: https://2026.ecoop.org/home/debt-2026 > > > > > >

Dec. 27, 2025

(no subject)

by Prachi

unsubscribe

Dec. 25, 2025

[DEBT 2026] Future Debugging Techniques Call for Papers, submission 7th of March 2026

by Steven Costiou

DEBT 2026: Call for Papers ================================================================================ DEBT 2026, Workshop co-located with ECOOP 2026, Brussels, Belgium Fourth Workshop on Future Debugging Techniques (https://2026.ecoop.org/home/debt-2026#Call-for-Papers) ================================================================================ Important Dates ----------------------- * Abstract submission deadline: Sat 28 Feb 2026 * Paper submission deadline: Sat 7 Mar 2026 * Author notification: Wed 15 Apr 2026 * Workshop: Monday 29 June 2026 ================================================================================ DEBTâ26 is looking to advance state-of-the-art to debug modern software. We welcome researchers from all related areas aimed at helping with the hard task of diagnosing the root cause of bugs, including dynamic and static debugging techniques, online and postmortem debuggers, delta debugging, automatic bug finding, novel visualization techniques for debugging programs, etc. The workshop aims to gather the community and foster discussion from different perspectives. That is why we seek submissions in the form of papers as well as talks and tool demonstrations. The workshop is a venue for all approaches to debugging. A non-exclusive list of topics of interest is: * Debugging techniques, from static to dynamic techniques. * Innovative visualisation techniques. * Techniques targeted specific programming models and execution models (e.g., concurrent and parallel programming, microservices, distributed ledgers, web, etc. ) or hardware (e.g., debugging micro-controllers, mobile devices, Big Data applications, etc.). * Case studies and evaluation of such techniques, e.g., user studies on visualisation tools, debuggers, etc. * Surveys, taxonomies of bugs and bug patterns, and current practices/uses of debugging approaches. Papers must be formatted according to the guidelines for ACM sigplanpapers (\documentclass[sigplan,screen]{acmart}), seehttps://www.sigplan.org/Resources/Author/ <https://www.sigplan.org/Resources/Author/>for details. Submissions should be made via Easychair using the following link:https://easychair.org/conferences/?conf=debt2026 <https://easychair.org/conferences/?conf=debt2026> The accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register for the workshop and attend the event to present the work, and participate in the discussions. AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. Workshop Organizers --------------------------- * Burcu Kulahcioglu Ozkan, Delft University of Technology, Netherlands * Steven Costiou, Centre Inria de lâUniversitÃ© de Lille, France For more information see: https://2026.ecoop.org/home/debt-2026

Dec. 24, 2025

Re: 2026 Prize open science for Pharo

by serge.stinckwich＠gmail.com

Congratulations to the team and the community for such an achievement! Regards Sent from my iPhone > On 20 Dec 2025, at 15:05, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > ï»¿ > > > https://www.enseignementsup-recherche.gouv.fr/fr/remise-des-prix-science-ou… > > > > <IMG_4200.jpeg> > > S

Dec. 21, 2025

Fwd: New releases to end 2025

by stephane ducasse

> Begin forwarded message: > > From: MartÃn Dias <tinchodias(a)gmail.com> > Subject: New releases to end 2025 > Date: 20 December 2025 at 22:24:40 CET > To: lse-openbloc <lse-openbloc(a)inria.fr> > Reply-To: MartÃn Dias <tinchodias(a)gmail.com> > > Hello, > > After 2 months we have new releases, and this time I copy-pasted the list of merged PRs to be more informative: > > Spec-Toplo: > â¢ Several improvements by @tinchodias in #35 > â¢ RoassalPresenter Toplo Adapter by @badetitou in #36 > â¢ Add SpToploScrollableAdapter by @badetitou in #39 > â¢ Toplo Notebook Adapter by @badetitou in #40 > â¢ Component list Adapter by @badetitou in #41 > â¢ SpecToploTableAdapter by @badetitou in #43 > â¢ Add tests for selection of item in table by @badetitou in #44 > â¢ Add many components and fixes by @badetitou in #45 > (https://github.com/pharo-graphics/Spec-Toplo/releases/tag/v0.8.0) > > Toplo: > â¢ WIP ToTable by @badetitou in #333 > â¢ First version of sorting table by @badetitou in #334 > â¢ Divider refactoring by @plantec in #335 > â¢ Move allowFormColorChange setting to ToImage by @tinchodias in #338 > â¢ Generic list refactoring by @plantec in #339 > â¢ TreeTableElement by @plantec in #340 > â¢ Tab pane refactoring by @plantec in #341 > â¢ Large change that change the ListElements structure: the inner collecâ¦ by @plantec in #342 > â¢ Fix size users by @Ducasse in #343 > â¢ Toplo Menu builder by @Ducasse in #345 > â¢ Select refactoring multi select refactoring by @plantec in #348 > â¢ To style store removal by @plantec in #351 > â¢ ToTable and co refactoring by @plantec in #352 > â¢ Using instance variables instead of dataUser by @Ducasse in #354 > â¢ Clean up ToProgressCircle and ToProgessBar by @LouisePla in #355 > â¢ Use token to manage ToProgressCircle color by @LouisePla in #357 > â¢ add ToResizeGrip class >>initializeToRawTheme: to setup a skin by @plantec in #356 > (https://github.com/pharo-graphics/Toplo/releases/tag/v0.8.0) > > Album: > â¢ Starting to migrate examples to tests by @Ducasse in #50 > â¢ Optimization: reorder the conditions by @tinchodias in #45 > â¢ Update GitHub Actions workflow for Smalltalk tests by @tinchodias in #53 > (https://github.com/pharo-graphics/Album/releases/tag/v0.8.0) > > Bloc: > â¢ Switch 1st and 2nd BlElement's inspector tabs by @tinchodias in #826 > â¢ Master by @Ducasse in #828 > â¢ Clean up on element id by @tinchodias in #830 > â¢ Clean up on scroll flinger by @tinchodias in #831 > â¢ Depend on XML-Parser:v3.6.3 > (https://github.com/pharo-graphics/Bloc/releases/tag/v2.7.0) > > Alexandrie: > â¢ Use #asPremultipliedARGB32Integer in 2 cairo tests by @tinchodias in #111 > â¢ Reorganize packages by @tinchodias in #114 > â¢ Cairo: Toy font and fontFaceAdoptingType by @tinchodias in #115 > â¢ Read png from memory by @tinchodias in #117 > (https://github.com/pharo-graphics/Alexandrie/releases/tag/v2.7.0) > > > ... AND MORE WORK (without releases for now): > > â¢ Roassal-Bloc host improvements: https://github.com/pharo-graphics/Roassal/ > â¢ Boids demo improvements: https://github.com/pharo-graphics/Tutorials > â¢ Benchmarks: https://github.com/pharo-graphics/BlocBenchs > â¢ Better profiler visualization: https://github.com/tinchodias/Sauco > â¢ Baseline helper that automatically writes inter-package dependencies: https://github.com/tinchodias/BaselineBuilder > â¢ Experiments: https://github.com/pharo-graphics/pharo-sdl-experiments > â¢ Another rendering optimizations we don't show yet! > â¢ Shaders on SDL_Texture and polish SDL3 bindings API: https://github.com/pharo-graphics/PharoSDL3 > > > Cheers! Thanks > Martin

Dec. 21, 2025

2026 Prize open science for Pharo

by stephane ducasse

https://www.enseignementsup-recherche.gouv.fr/fr/remise-des-prix-science-ou… ï¿¼ S

Dec. 20, 2025

Re: Fw: Pharo CIG Crash Issue

by Aik-Siong Koh

Esteban: My student Morgan Lee has posted the issue at https://github.com/pharo-cig/pharo-cig/issues/41 We are eager to interface Pharo to OpenCascade. Thanks, Aik-Siong Koh On Sat, 29 Nov 2025 09:31:31 +0100, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: Â Hello,Â Â pharo-cig has never been tested on windows, I no wonder is crashing :) until now, generation always happened in linux-side (generatedlibraries however have been tested on windows, time to time... when generation has nothing to do with the platform :P). Â I have to say that pharo-cig is not a "pharo team" project (in the sense any member of the pharo team can take it). While we can have this conversation here, I would very much prefer if we have it at https://github.com/pharo-cig/pharo-cigÂ :) Â Esteban Â On 11/29/25 03:09, MORGAN LEE GUAN HAN via Pharo-dev wrote: P {margin-top:0;margin-bottom:0;} Forwarding the original email. Â From:Â MORGAN LEE GUAN HAN <1211107272(a)student.mmu.edu.my> Sent:Â Saturday, November 29, 2025 12:08 AM To:Â Aik-Siong Koh <askoh(a)askoh.com> Subject:Â Pharo CIG Crash Issue Â Dear Pharo Team, Â I am currently attempting to replicate what Esteban Lorenzano did for this Youtube VideoÂ (Esteban Lorenzano - Pharo-CIG: C++ Interface Generator - 23 April 2025), which is toÂ generate C Bindings for Pharo uFFI to call,Â in Windows 11. Unfortunately, I am unable to replicate the results of the video. The results of my attempts leads to Pharo's Virtual Machine crashing and exiting abruptly to the launcher. I am unable to find any logs for this, and would appreciate your support for this matter. Â OS:Â Windows 11 Clang: https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8Â (LLVM-18.1.8-win64.exe) Pharo Template:Â Pharo 14.0 - 64bit (development version, latest) Pharo CIG Github:Â https://github.com/pharo-cig/pharo-cig Raylib: https://github.com/raysan5/raylib Â Steps to Reproduce Step 1: Create Image Step 2: Installing Pharo CIG Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). Copy and paste the Installation Code from the Pharo CIG Github. Click the "Do it All" green triangle button on the top left of the Playground Window. Step 3: Installing Clang Download and run the Pre-built binaries from this Github pageÂ according to your platform. The folder named LLVM should be in your "C:\Program Files" directory after installation for Windows 11. Other installation methods may be used according to your preference. Step 4: Installing raylib Download or clone the raylib Github repository. Extract the folder ('raylib-master') if you are downloading the repository. Place the folder in a directory of your preference. E.g "C:\Users\morgan\raylib-master" Step 5: Setting Pharo CIG Requirements CIG needs to be able to find the clang library. If it cannot find it automatically, set the location in LibClang>>unix64LibraryName, e.g. - Pharo CIG Github Open System Browser with 'Ctrl + O + B' (or 'Cmd + O + B'). Create a "win32LibraryName" method in the LibClang class under the CIG-LibClang package to set your "libclang.dll" location. This method is missing from the default installation. Paste in this code (There may be whitespace character issues): Â win32LibraryName Â Â ^ FFIWindowsLibraryFinder new Â Â Â Â userPaths: #('C:\Program Files\LLVM\bin'); Â Â Â Â findAnyLibrary: #('libclang.dll') Save and create the method with 'Ctrl + S' (or 'Cmd + S'). Â Step 6: The Example Recipe from Github Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). Copy andÂ paste the example recipe from Github into the Playground. Configure the example recipe from Github. Change "import:" and "cIncludedPath:" directories according to your file structure. E.g '/home/esteban/dev/vm/raylib/src/raylib.h' âÂ 'C:\Users\morgan\raylib-master\src\raylib.h' Click the "DoÂ it All" green triangle button on the top left of the Playground Window. This should cause the Virtual Machine to abruptly exit or crash. Code Snippet (There may be whitespace character issues): Â Â (lib := CigCLibraryGenerator new) Â "Prefix to be added to the generated classes (structures, enums, etc.)" Â prefix: 'Ray'; Â "name of the generated package (by default, is the same as the libraryName, capitalized)" Â packageName: 'Raylib'; Â "Library name. If not unixLibraryName, macLibraryName and winLibraryName Â Â are specified, it will be taken as base name for the existing libraries Â Â (e.g. in this case raylib.so, raylib.dylib and raylib.dll)"Â Â libraryName: 'raylib'; Â "headers to import (there can be as many of them as is needed)." Â import: 'C:\Users\morgan\raylib-master\src\raylib.h'; Â import: 'C:\Users\morgan\raylib-master\src\rcamera.h'; Â "include path (-I of c compiler), to allow libclang to find other Â Â includedÂ headers." Â cIncludePath: 'C:\Users\morgan\raylib-master\src'; Â "Since thisÂ is a graphical library, instruct the library to run in mainthread Â Â (otherwise, default is 'same thread' which is the same thread the pharo is Â Â running)" Â Â useMainThread. Â "generate the library" lib generate. Â Â End of email. Â Â Â Â

Dec. 5, 2025