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

[ANN] Historia - an event sourcing framework for Pharo

by Masashi UMEZAWA

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]

April 29, 2025

Pharo13 freeze mode, Starting Pharo14 branch

by Guillermo Polito

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

April 25, 2025

Re: Survey: Identifying and Fixing Undesirable Behaviors Across Software Versions

by Remi Dufloer

Hello, Just a kind reminder that our research survey is still open We sincerely thank those who have already completed it. If you have not yet had the opportunity, your participation would be of great value to our study. Access the survey here: https://sondages.inria.fr/index.php/566958?lang=en You will find more information about the project in the forwarded message below. Thank you once again for your time and support. Best regards, Remi Dufloer > De: "Remi Dufloer" <remi.dufloer(a)inria.fr> > Ã: "pharo-dev" <pharo-dev(a)lists.pharo.org> > EnvoyÃ©: Mercredi 2 Avril 2025 17:38:19 > Objet: Survey: Identifying and Fixing Undesirable Behaviors Across Software > Versions > 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

April 11, 2025

Re: Sorter in Completion Engine in Pharo 13

by stephane ducasse

You can check the heuristic class but in essence tmp > local variables> superclass variables self message -> method in the class then in superclass super message -> the right one ClassName -> shared var > sharedVar of superclass > global environment The problem of size is that often it proposes you something that is just out of scope just because it is smaller and globally sorting breaks all the rest. So if we keep it we should just through away all the rest because why bothering if this is just to break everythinng after We are working on better heuristics for class names: H1 we look in repository level package (all the packages within the project) So this is local package > package in the same project > global H2 we look in the dependent packages and the results are promising. So this is local to package > dependent packages > global Now Iâm thinking that we could also have a way to declare preference per project. For example with Copiy Domenico could simple look first in his package and extensions. The current heuristics also takes into account playground variables. We are also working on taking into account the past method defined. So as you see this is not just sorting. > On 5 Apr 2025, at 22:44, Daniel Slomovits <daniels220(a)gmail.com> wrote: > > Is there documentation of the intended behavior/reasoning behind the semantic sort somewhere? I feel like I might often prefer the SizeSorter behavior (if I'm understanding it correctly), but if that's going to be removed, maybe I would take a look at the semantic sorter and see if I can add some refinement options there. > > On Fri, Apr 4, 2025 at 2:20â¯AM sducasseatwork--- via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >> But pay attention that we will remove the sorter because it often contradicts the semantics sorting implemented >> by default. I often put the sorter on NoSorter. >> >> S >> >>> On 3 Apr 2025, at 21:42, Omar Abedelkader <omar.abedelkader(a)inria.fr <mailto:omar.abedelkader@inria.fr>> wrote: >>> >>> 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: >>> AlphabeticSorter â Sorts suggestions in alphabetical order. >>> ReverseAlphabeticSorter â Sorts suggestions in reverse alphabetical order. >>> NoSorter â Displays suggestions in the original order as provided by the completion engine. >>> 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 >>> inria.fr/fr/evref <https://www.inria.fr/fr/evref> >>> cristal.univ-lille.fr/omarabedelkader <https://www.cristal.univ-lille.fr/profil/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 >>> <rf-inria.png> >>> 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Ã©. >>> >> StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

April 6, 2025

Re: Sorter in Completion Engine in Pharo 13

by Daniel Slomovits

Is there documentation of the intended behavior/reasoning behind the semantic sort somewhere? I feel like I might often prefer the SizeSorter behavior (if I'm understanding it correctly), but if that's going to be removed, maybe I would take a look at the semantic sorter and see if I can add some refinement options there. On Fri, Apr 4, 2025 at 2:20â¯AM sducasseatwork--- via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > But pay attention that we will remove the sorter because it often > contradicts the semantics sorting implemented > by default. I often put the sorter on NoSorter. > > S > > On 3 Apr 2025, at 21:42, Omar Abedelkader <omar.abedelkader(a)inria.fr> > wrote: > > 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 > inria.fr/fr/evref <https://www.inria.fr/fr/evref> > cristal.univ-lille.fr/omarabedelkader > <https://www.cristal.univ-lille.fr/profil/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 > <rf-inria.png> > > *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Ã©.* > > >

April 5, 2025

Re: Sorter in Completion Engine in Pharo 13

by sducasseatwork＠mailo.com

But pay attention that we will remove the sorter because it often contradicts the semantics sorting implemented by default. I often put the sorter on NoSorter. S > On 3 Apr 2025, at 21:42, Omar Abedelkader <omar.abedelkader(a)inria.fr> wrote: > > 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: > AlphabeticSorter â Sorts suggestions in alphabetical order. > ReverseAlphabeticSorter â Sorts suggestions in reverse alphabetical order. > NoSorter â Displays suggestions in the original order as provided by the completion engine. > 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 > inria.fr/fr/evref <https://www.inria.fr/fr/evref> > cristal.univ-lille.fr/omarabedelkader <https://www.cristal.univ-lille.fr/profil/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 > <rf-inria.png> > 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Ã©. >

April 4, 2025

Sorter in Completion Engine in Pharo 13

by Omar Abedelkader

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Ã©.

April 3, 2025

Re: Cannot commit to github in Pharo12

by Aik-Siong Koh

Hi: I have tried to debug this problem without success. I have upload the entire image folder to https://www.askoh.com/misc/Pharo12SymbolicMbD.zip The repo of interest is https://github.com/aiksiongkoh/SuperApp Please help. Thanks, Aik-Siong Koh Cyril FERLICOT-DELBECQUE via Pharo-dev wrote: > This is weird because this error happens if a class is exported with > the Tonel format in a package (aka a Folder) but has a different > package in the metadata of the class. > > But here I'm checking the repo and things seems good > > image.png > > The folder is StCad-Geo and the category is StCad-Geo-GEO (which is > the tag also). > > From the debugger you got I was expecting this class to have > StMath-GEO as category... > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > On Friday, January 3rd, 2025 at 10:58 PM, Aik-Siong Koh > <askoh(a)askoh.com> wrote: >> 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 >

April 2, 2025

Survey: Identifying and Fixing Undesirable Behaviors Across Software Versions

by Remi Dufloer

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

April 2, 2025