- Pharo-users - 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: EXIF / JPEG metadata

by Siemen Baader

Hi Alistair, old question, but still relevant.. Did you find a solution you want to share? I need to access EXIF data to get GPS coordinates from photos for a project where citizens register trees. cheers Siemen

Nov. 30, 2025

Fw: Pharo CIG Crash Issue

by MORGAN LEE GUAN HAN

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<https://www.youtube.com/watch?v=U9fpvZJaFx4> (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 [cid:1a4a23bb-52e6-47a5-b0a7-b251d6ddc8ea] 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<https://github.com/pharo-cig/pharo-cig>. Click the "Do it All" green triangle button on the top left of the Playground Window. [cid:2a667f99-b808-4950-a40a-798054e502e4] Step 3: Installing Clang Download and run the Pre-built binaries from this Github page<https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8> 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<https://github.com/raysan5/raylib>. 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<https://github.com/pharo-cig/pharo-cig> 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') [cid:3241b208-b515-4b7b-98fc-45312ec65c82] Save and create the method with 'Ctrl + S' (or 'Cmd + S'). [cid:7d0e72f0-4086-411a-8e27-c2b11c4df817] 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 <https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file> into the Playground. Configure the example recipe from Github<https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file>. 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. [cid:55b4605c-3b19-45f0-8ed8-ef9093b6fa89] End of email.

Nov. 29, 2025

ANN: More syntax highlights for Pharo code :)

by Esteban Lorenzano

Hi, Last week I was with insomnia and playing with IAs and I managed to create some nice styles (based on existing ones) you can use to improve how your Pharo code lookÂ :) Metacello new Â Â repository: 'gtithub://estebanlm/themes'; Â Â baseline: 'Themes'; Â Â load: 'HighlightStyles' ... then you can have some nice styles (other than the current ones), both for dark and light themes :) Enjoy, Esteban

Nov. 24, 2025

Re: Artifacts and Smalltalk code

by Noury Bouraqadi

Hi Siemen, I +1 the issue. I experience it with PharoJS and WebST. Although now with WebST, the HTML is generated along the JS. Noury On Thu, Nov 20, 2025 at 1:15â¯PM Siemen Baader via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > I am struggling with the same issue in a web apps context. I use many > external tools to edit HTML, JS and graphics, so they need to be stored on > disk. > > My current solution is to keep everything in Git and export Pharo packages > to the FileTree format. This works nicely with Git, but of course it is all > more complicated than keeping the data inside Pharo. > > What I'd really find helpful would be if we could mount part of a Pharo > image as a file system, so that external apps could just read and save > files to the image. > > Also, it would be nice to be able to use the image itself for (smaller) > production databases more reliably. I think we would need something that > can save deltas externally when state inside the image changes â like a > journaled file system â so that data is kept & restored after an occasional > image crash. I think this already works reasonably with code changes in > Epicea, but there we restore code manually. > > cheers > Siemen > -- Noury Bouraqadi

Nov. 20, 2025

Re: Artifacts and Smalltalk code

by Siemen Baader

I am struggling with the same issue in a web apps context. I use many external tools to edit HTML, JS and graphics, so they need to be stored on disk. My current solution is to keep everything in Git and export Pharo packages to the FileTree format. This works nicely with Git, but of course it is all more complicated than keeping the data inside Pharo. What I'd really find helpful would be if we could mount part of a Pharo image as a file system, so that external apps could just read and save files to the image. Also, it would be nice to be able to use the image itself for (smaller) production databases more reliably. I think we would need something that can save deltas externally when state inside the image changes â like a journaled file system â so that data is kept & restored after an occasional image crash. I think this already works reasonably with code changes in Epicea, but there we restore code manually. cheers Siemen

Nov. 20, 2025

Pharo News of the Week 46/2025

by Marcus Denker

# Pharo News of the Week 46/2025 - [Blog Post] What if Java had Symmetric Converter Methods on Collection? https://donraab.medium.com/what-if-java-had-symmetric-converter-methods-on-… - [Research] 221 research papers in the PHARO Collection: https://inria.hal.science/PHARO. You can add your papers: https://pharo.org/web/PharoPublications - [ANN][TALK] Wednesday, Nov 26: Norbert Hartl - Soil: a database for fun and profit https://www.meetup.com/ukstug/events/311265917/ News wanted! You can add your news to this list (that is, next week) using this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Fixes - fix: make OnlineSourceDebugInfo>>#readVariableNamed:fromContext: workâ¦ #18719 https://github.com/pharo-project/pharo/pull/18719 - Fix #testUndeclared #18893 https://github.com/pharo-project/pharo/pull/18893 - Fix large array compilation #18825 https://github.com/pharo-project/pharo/pull/18825 # Tools - Using DebugInfo #1259 https://github.com/pharo-spec/NewTools/pull/1259 - Migrate Epicea browsers to NewTools #1282 https://github.com/pharo-spec/NewTools/pull/1282 - Remove Epicea browsers from Pharo #18896 https://github.com/pharo-project/pharo/pull/18896 - Add back sha in about #1281 https://github.com/pharo-spec/NewTools/pull/1281 - Bring back Select package as right dependency feature #1279 https://github.com/pharo-spec/NewTools/pull/1279 - Add a defaultAction to InformativeNotification #1278 https://github.com/pharo-spec/NewTools/pull/1278 - Inspecting a string should display the ' ' (Fix #814) #1277 https://github.com/pharo-spec/NewTools/pull/1277 - Fixes: Message browser panes cannot be removed with Cmd x anymore #18872 https://github.com/pharo-project/pharo/pull/18872 # Refactoring - Better comment and names for refactoring #18891 https://github.com/pharo-project/pharo/pull/18891 - Fix issue #18507: Scope issue breaks refactoring (retry) + new hook instantiateRefactoring #18890 https://github.com/pharo-project/pharo/pull/18890 - Tests references #18871 https://github.com/pharo-project/pharo/pull/18871 - Adding tests and comments for references: OCNodes #18863 https://github.com/pharo-project/pharo/pull/18863 - Feat/exposing temp def move #18861 https://github.com/pharo-project/pharo/pull/18861 # Spec - Do not use StPharoApplication in Spec #1842 https://github.com/pharo-spec/Spec/pull/1842 - fixes on SpCodePresenter>>styleScheme and revert a rename #1841 https://github.com/pharo-spec/Spec/pull/1841 - add selectedRowPresenter to tables #1840 https://github.com/pharo-spec/Spec/pull/1840 # VM - A new file plugin #1024 https://github.com/pharo-project/pharo-vm/pull/1024 - Only scan the class table if become: was performed to an active class object #1023 https://github.com/pharo-project/pharo-vm/pull/1023 # Git / Iceberg - Introduce IceTipRepositoryStatusModel to avoid multiple commit lookups #1918 https://github.com/pharo-vcs/iceberg/pull/1918 - 1686-SSH-Key-pair-should-not-ask-user-it-should-use-the-user-from-the-URL #1687 https://github.com/pharo-vcs/iceberg/pull/1687 - MetacelloPharoPlatform>>#withMetacelloLoadSessionDo: is now in Pharo #1990 https://github.com/pharo-vcs/iceberg/pull/1990 - Fixing the fetchAllRemotes DNU #1989 https://github.com/pharo-vcs/iceberg/pull/1989 - Litlle fix for inform call #1986 https://github.com/pharo-vcs/iceberg/pull/1986 - Miss select a folder to clone user input validation #1985 https://github.com/pharo-vcs/iceberg/pull/1985 # inform: cleanup - Less meta prog for classes that are loaded. #18889 https://github.com/pharo-project/pharo/pull/18889 - Less inform: #18888 https://github.com/pharo-project/pharo/pull/18888 - Reduce dependencies to UIManager #18844 https://github.com/pharo-project/pharo/pull/18844 # Cleanup - 18813-Remove-Binary-representation-in-MCZ-files #18815 https://github.com/pharo-project/pharo/pull/18815 # Command Line - Allow to fetch flags and positionals not declared in the last subcommand #18875 https://github.com/pharo-project/pharo/pull/18875 # Packaging / Boostrap / Package loading - Fix multiple dependencies in DebugPoints #18892 https://github.com/pharo-project/pharo/pull/18892 - Clean Keymapping baseline #18887 https://github.com/pharo-project/pharo/pull/18887 - Fix kernel system dependency test #18886 https://github.com/pharo-project/pharo/pull/18886 - Fix minimal image tests #18885 https://github.com/pharo-project/pharo/pull/18885 - Clean a few dependencies of the kernel #18884 https://github.com/pharo-project/pharo/pull/18884 - Extract ParseTreeRewriter to its own package #18883 https://github.com/pharo-project/pharo/pull/18883 - Fix TFFI reset and fix load order #18882 https://github.com/pharo-project/pharo/pull/18882 - Revert loading order of TFFI #18880 https://github.com/pharo-project/pharo/pull/18880 - Start SessionManager with a session #18870 https://github.com/pharo-project/pharo/pull/18870 - Fix startup preferences loading #18867 https://github.com/pharo-project/pharo/pull/18867 - Clean traits in the bootstrap #18842 https://github.com/pharo-project/pharo/pull/18842

Nov. 20, 2025

CfP: SLE 2026 - 19th ACM SIGPLAN International Conference on Software Language Engineering

by Andrei Chis

19th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2026) 2 - 3 July 2026 Rennes, France https://conf.researchr.org/home/sle-2026 https://www.sleconf.org/2026/ ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 19th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2026 conference will be co-located with STAF 2026 and hosted in Rennes, France, on 2 - 3 July 2026. --------------------------- Important Dates --------------------------- * Abstract submission (all tracks): Friday 27 February 2026 * Paper submission (all tracks): Friday 6 March 2026 * Paper notification (all tracks): Monday 20 April 2026 * Conference: Thursday 2 - Friday 3 July 2026 (co-located with STAF) All dates are Anywhere on Earth. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: *Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - AI-assisted language design and optimisation * Software Language Quality - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Model-based testing - AI-assisted validation * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - (AI-assisted) Language refactorings * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and emerging/promising research areas - Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) - Language engineering for AI. AI and ML language engineering (e.g., ML compiler testing, code classification, DSLs for AI processes and tasksâ¦) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: * Research papers: These are âtraditionalâ papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. * New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. * SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. * Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool papers. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. **Workshops**: Workshops will be organised by STAF. Please inform us and contact STAF 2026 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2026 Website. --------------------------- Submission --------------------------- SLE 2026 has a single submission round for papers, including a mandatory abstract registration. Authors of accepted research papers will be invited to submit artefacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ ( https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is \documentclass[sigplan,anonymous,review]{acmart}. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. You can access the submission site from the conference website: https://conf.researchr.org/home/sle-2026 --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy ( https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACMâs general principles, as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects ( https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, validation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. --------------------------- Artefact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. --------------------------- Awards --------------------------- * Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. * Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. * Most Influential Paper: Award for the SLE 2016 paper with the greatest impact, as judged by the SLE Steering Committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **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 the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- * General chair: Arnaud Blouin, Univ Rennes, INSA Rennes, Inria, CNRS, IRISA * PC co-chair: Jordi Cabot, Luxembourg Institute of Science and Technology * PC co-chair: Shigeru Chiba, University of Tokyo, Japan --------------------------- Contact --------------------------- For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs (jordi.cabot(a)list.lu and chiba(a)g.ecc.u-tokyo.ac.jp)

Nov. 20, 2025

UKSTUG Meeting: Norbert Hartl - Soil: a database for fun and profit - 26 November 2025

by UK Smalltalk

Soil ( https://github.com/ApptiveGrid/Soil ) is an object oriented database implemented completely in smalltalk/pharo. It makes it easy to build a persistent solution without the burden of mapping everything to some external DSL/database. It supports storing arbitrary graphs and enables transparent access to them. It has binary search indexes to make lookups of huge collections quite efficient. It is the main database behind ApptiveGrid - low code tool to build business processes. ( https://www.apptivegrid.de/) Norbert Hartl ( https://github.com/noha ) is an experienced software engineer and entrepreneur with a strong track record of delivering business projects and developing key libraries and frameworks. As the co-founder of ApptiveGrid and PharoPro, he focuses on creating efficient, zero-dependency software solutions that drive business innovation and streamline operations. 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/311265917/ ) to receive the meeting details.

Nov. 19, 2025