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

[ANN] Historia - an event sourcing framework for Pharo
by Masashi UMEZAWA April 29, 2025

April 29, 2025

Hi all, I'm pleased to announce Historia - an event sourcing framework for Pharo. https://github.com/mumez/Historia Historia provides a straightforward way to model your application's state changes as a sequence of immutable events. Key features include: - Model object mutations recorded as timestamped events - ModelSpace (aggregation) for managing named model objects - Automatic synchronization of remote ModelSpaces - Time travel capability to restore state at any point in history - Reliable persistent storage (Redis) for snapshots and events - Inter-ModelSpace communication via EventBridge - Included Bank Account example demonstrating framework usage The framework is designed to be lightweight yet useful for implementing event driven style apps in Pharo. Enjoy! -- [:masashi | ^umezawa]

1 0

Pharo13 freeze mode, Starting Pharo14 branch
by Guillermo Polito April 25, 2025

April 25, 2025

Hi Everybody, We are coming close to the Pharo13 release date (TBA). Thus, we are freezing the branch for new features, and we opened the Pharo14 branch for new developments. Do not hesitate to still propose bugfixes to the Pharo13 branch. Today, we also have a Pharo sprint at the Inria lab, we are probably going over the PRs and moving their base to Pharo14 if needed. Cheers, G

1 0

Survey: Identifying and Fixing Undesirable Behaviors Across Software Versions
by Remi Dufloer April 11, 2025

April 11, 2025

Hello, As part of my PhD at the University of Lille, I am currently conducting a study on how developers handle certain bug scenarios. The goal is to better understand current practices, the tools used, and developers' needs regarding debugging in a specific scenario. Link to the questionnaire: [ https://sondages.inria.fr/index.php/566958?lang=en | https://sondages.inria.fr/index.php/566958?lang=en ] Your participation in this short questionnaire (5 - 10 minutes) would greatly help us analyze existing methods and identify potential gaps in the available solutions. This survey will be open for 6 weeks (Until May 15th, 2025) . The responses will be analyzed and included in a scientific publication. The results will be available [ https://remidufloer.github.io/Dufloer.github.io/survey.html | here ] . If you can, please feel free to share this questionnaire with other developers who might be interested. Every response counts and will contribute to a better understanding of the community's practices! A big thank you for your help and time. Best regards, RÃ©mi Dufloer PhD Student, University of Lille ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ Bonjour , Dans le cadre de ma thÃ¨se Ã lâUniversitÃ© de Lille, je mÃ¨ne actuellement une Ã©tude sur la maniÃ¨re dont les dÃ©veloppeurs gÃ¨rent certains scÃ©narios de bugs. Lâobjectif est de mieux comprendre les pratiques actuelles, les outils utilisÃ©s et les besoins des dÃ©veloppeurs en matiÃ¨re de debugging sur un scÃ©nario prÃ©cis. Voici le lien du questionnaire : [ https://sondages.inria.fr/index.php/566958?lang=en | https://sondages.inria.fr/index.php/566958?lang=en ] Votre participation Ã ce court questionnaire (5 - 10 minutes) nous aiderait Ã©normÃ©ment Ã analyser les mÃ©thodes existantes et Ã identifier les Ã©ventuelles lacunes dans les solutions disponibles. Ce survey est ouvert durant 6 semaines (fermeture le 15 mai 2025 ). Les rÃ©ponses obtenues seront analysÃ©es et feront l'objet d'une publication scientifique. Les rÃ©sultats seront publiÃ©s [ https://remidufloer.github.io/Dufloer.github.io/survey.html | ici ] . Si vous le pouvez, nâhÃ©sitez pas Ã partager ce questionnaire avec dâautres dÃ©veloppeurs susceptibles dâÃªtre intÃ©ressÃ©s. Chaque rÃ©ponse compte et contribuera Ã une meilleure comprÃ©hension des pratiques de la communautÃ© ! Un grand merci pour votre aide et votre temps. Bien cordialement, Dufloer RÃ©mi Doctorant, UniversitÃ© de Lille

1 1

Sorter in Completion Engine in Pharo 13
by Omar Abedelkader April 6, 2025

April 6, 2025

Hello, I hope this message finds you well. This is to inform you about the available sorter options in our code completion engine and how to change them as needed. Currently, there are four different sorter configurations you can choose from: 1. AlphabeticSorter â Sorts suggestions in alphabetical order. 2. ReverseAlphabeticSorter â Sorts suggestions in reverse alphabetical order. 3. NoSorter â Displays suggestions in the original order as provided by the completion engine. 4. SizeSorter â Modifies the suggestion list to prioritize and return the closest match based on what you are currently typing. If you would like to change the sorter, please follow these steps: Open Settings â Code Browsing â Code Completion â Sorter , then select SizeSorter (or any other preferred sorter). Default Sorter : NoSorter Best regards, -- Omar ABEDELKADER Doctorant, Ãquipe EVREF [ https://www.inria.fr/fr/evref | inria.fr/fr/evref ] [ https://www.cristal.univ-lille.fr/profil/omarabedelkader/ | cristal.univ-lille.fr/omarabedelkader ] / Institut National de Recherche en Sciences et Technologies du NumÃ©rique Parc Scientifique de la Haute Borne Park Plaza - BÃ¢timent A - 40 avenue Halley 59650 Villeneuve d'Ascq - France Si vous lisez ce courriel en dehors de vos heures de travail, merci de ne le traiter quâen cas dâurgence avÃ©rÃ©e. Si ce courriel ne vous est pas destinÃ©, merci de ne pas en prendre connaissance, le dÃ©truire et en informer lâexpÃ©diteur. Merci de nâimprimer ce courriel quâen cas de nÃ©cessitÃ©.

4 3

Cannot commit to github in Pharo12
by Aik-Siong Koh April 2, 2025

April 2, 2025

In Pharo12, I click/Sources/Git Repository Browser/ In the Git Repository Browser, I see *SuperApp Uncommitted changes, 1 incoming, 1 main I Select/SuperApp. RightClick/Commit/ I get the following error. Please advise. Thanks. Aik-Siong Koh

3 5