May 2024 - Pharo-users - lists.pharo.org

This week (20/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Backport use of FormSet for ToggleMenuItemMorph submenu markers #16631 https://github.com/pharo-project/pharo/pull/16631 # Ehancements - [Enhancement] Add "copy class name" to extras menu in Calypse #16635 https://github.com/pharo-project/pharo/pull/16635 - Add missing RGGlobalVariable>>isInstanceVariable #16644 https://github.com/pharo-project/pharo/pull/16644 - Introduce CompiledMethod>>#isInstanceSide #16626 https://github.com/pharo-project/pharo/pull/16626 # Fixes - Issue 16430 - String>> asSymbol no protected against concurrent access (alternative solution) #16565 https://github.com/pharo-project/pharo/pull/16565 - [Bug]: Date>>#addMonths: should Respect Offset #16603 https://github.com/pharo-project/pharo/pull/16603 - sort subdirectories in the same order as the file tree table #748 https://github.com/pharo-spec/NewTools/pull/748 # VM - Fixed VirtualMachine 76 and 78 parameters #16641 https://github.com/pharo-project/pharo/pull/16641 - Do not retain any selectors in CogAbstractInstruction #798 https://github.com/pharo-project/pharo-vm/pull/798 - add tests for type harmonization #807 https://github.com/pharo-project/pharo-vm/pull/807 - remove warning because of type and unsigned shift issues #800 https://github.com/pharo-project/pharo-vm/pull/800 - Fixed ntb page selection change announcement if built without pages #1542 https://github.com/pharo-spec/Spec/pull/1542 # Package Structure - Sindarin/ScriptableDebugger should be listed as external project #16653 https://github.com/pharo-project/pharo/pull/16653 - Sindarin in Pharo13 need to be loaded from Pharo13 branch of ScriptableDebugger (and not Pharo12 branch) #751 https://github.com/pharo-spec/NewTools/pull/751 - Simplify Calypso packaging #16602 https://github.com/pharo-project/pharo/pull/16602 - Cleanup: CoverageCollectorTest should be in an own test package #16613 https://github.com/pharo-project/pharo/pull/16613 # Rules - proposition rule for nil branch #16547 https://github.com/pharo-project/pharo/pull/16547 - [Enhancement] Add a rule ReBaselineProperlyPackagedRule #16630 https://github.com/pharo-project/pharo/pull/16630 - [Enhancement] Add a rule ReBaselineWithProperSuperclassRule #16633 https://github.com/pharo-project/pharo/pull/16633 - proposition for a potential new rule: useless ifTrue:ifFalse: #16638 https://github.com/pharo-project/pharo/pull/16638 - add ReStatementsAfterReturnConditionalRule #16640 https://github.com/pharo-project/pharo/pull/16640 - Review ReClassNotCategorizedRuleTest>>#testRule #16649 https://github.com/pharo-project/pharo/pull/16649 - Improve ReBaselineProperlyPackagedRule and ReBaselineWithProperSuperclassRule and cover with tests #16648 https://github.com/pharo-project/pharo/pull/16648 - Enhancement: Provide a lint rule to check for a "super initialize" call in instance side #initialize methods #16615 https://github.com/pharo-project/pharo/pull/16615 - tests for rules from the General-Rules package #16474 https://github.com/pharo-project/pharo/pull/16474 # Cleanups - Reduce references to Undeclared global variable #16642 https://github.com/pharo-project/pharo/pull/16642 - Remove deprecated way to access the global package organizer #754 https://github.com/pharo-spec/NewTools/pull/754 - Remove the package Deprecated12, introduce package Deprecated13 #16538 https://github.com/pharo-project/pharo/pull/16538 - proposition refactoring -> Cleanup: 2 duplicated methods in FreeType #16583 https://github.com/pharo-project/pharo/pull/16583 - Clean up in SDL_Texture and SDL_Renderer #16601 https://github.com/pharo-project/pharo/pull/16601 - Simplify script pragma for FinderUI #16623 https://github.com/pharo-project/pharo/pull/16623 - CommentTestCase should be moved to PharoDocComment-Tests #16619 https://github.com/pharo-project/pharo/pull/16619 - Package "System-DependenciesTests" should be "System-Dependencies-Tests" #16621 https://github.com/pharo-project/pharo/pull/16621 - Cleanup: AthensTransformTest>>transformClass should be in accessing #16628 https://github.com/pharo-project/pharo/pull/16628 - Fix lint in ReShouldSendSuperSetUpAsFirstMessage class>>#checksMethod (second PR) #16643 https://github.com/pharo-project/pharo/pull/16643 - Remove part of ReAsClassRule about #asClass #16658 https://github.com/pharo-project/pharo/pull/16658 - Cleanup: Remove deprecated announcement #SnapshotDone in SnapshotOperation>>#performSnapshot for Pharo 13 #16657 https://github.com/pharo-project/pharo/pull/16657 - Cleanup: unnecessary class BlLoadProjectWorldMenu #16655 https://github.com/pharo-project/pharo/pull/16655 - SourceFile>>#isOpen should use isNotNil #16651 https://github.com/pharo-project/pharo/pull/16651 - Remove Gofer #16606 https://github.com/pharo-project/pharo/pull/16606 - Remove reference to a deprecated class #1822 https://github.com/pharo-vcs/iceberg/pull/1822 - Fixing call to deprecated code #749 https://github.com/pharo-spec/NewTools/pull/749 - Use isNotNil instead notNil in initializePresenters #753 https://github.com/pharo-spec/NewTools/pull/753 # Website - Update community.md: Social Media Section #74 https://github.com/pharo-project/pharo-website/pull/74 - Update community.md: update tweet suggestion form #73 https://github.com/pharo-project/pharo-website/pull/73 - Update Companies.md #72 https://github.com/pharo-project/pharo-website/pull/72 - Update 2024-04-26-pharo12-released.md: fix typy #69 https://github.com/pharo-project/pharo-website/pull/69

May 17, 2024

Re: Getting started with the easy projects

by Richard O'Keefe

Life has been getting in the way. Thanks for the "Managing your code" chapter. I've got that now. On Fri, 17 May 2024 at 00:00, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi richard > > I wanted to tell you that there is also a chapter about how to contribute > in the Managing your code > [image: preview.png] > > 2020-05-12-ManageCode > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > PDF Document Â· 2,1 MB > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > > > S > > > On 4 May 2024, at 09:10, stephane ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Hi richard > > I can write something once you have a look at the video and let me know > what you would like to know. > > S > > On 3 May 2024, at 14:27, Sebastian Jordan Montano < > sebastian.jordan(a)inria.fr> wrote: > > You have the guide how to contribute to a fix in Pharo: > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > Sebastian > > ----- Mail original ----- > > De: "Richard O'Keefe" <raoknz(a)gmail.com> > Ã: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > EnvoyÃ©: Vendredi 3 Mai 2024 12:28:16 > Objet: [Pharo-users] Re: Getting started with the easy projects > > > What I was really asking was about the very basic mechanics of it. > "Where are the instructions about how to sign up" > meant "do I have to register somewhere and if so where and how?" > "Where are the instructions about what to do" > meant "suppose I have registered and have the latest Pharo open > on my laptop; how do I connect to the repository, how do I submit > a change for review?" I have been playing with Pharo since version 1 > but I've never actually connected to a repository. > > I think a "Complete Idiot's Guide to Getting Started with Distributed > Development in Phraro" probably already exists somewhere, I just > don't know where to look for it. > > On Sat, 27 Apr 2024 at 21:05, stephane ducasse > <stephane.ducasse(a)inria.fr> wrote: > > > Hi richard > > https://github.com/orgs/pharo-project/projects/8 > lists some easy projects. I'd like to make a contribution. > > > Cool. > The first thing I suggest is to take the stupidiest issue like adding a > comment > in a method > or fixing a badly written comment and make a PR. > I like to do this trivial things because there are easy to give a positive > slant > on my energy. > > Where are the instructions on how to sign up and what > to do? Fair warning, I'll probably need a bit of hand-holdingâ¦ > > > For the contributions feel free to pick what you like > > - Some easy things are: better comments, improving test coverage > - Now Iâm pretty sure that we can get collection improvements > - This one could interest you: underscores in numeric literals > https://github.com/pharo-project/pheps/pull/18/files > We had long design discussions and I think that the result is good but we > never > got the time to implement it. > > S > > > > > 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 > > > > > > 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 > > > > > > > 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 > > > > > >

May 17, 2024

Re: Getting started with the easy projects

by stephane ducasse

Hi richard I wanted to tell you that there is also a chapter about how to contribute in the Managing your code https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdfï¿¼ 2020-05-12-ManageCode PDF Document Â· 2,1 MB S > On 4 May 2024, at 09:10, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi richard > > I can write something once you have a look at the video and let me know what you would like to know. > > S > >> On 3 May 2024, at 14:27, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> wrote: >> >> You have the guide how to contribute to a fix in Pharo: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> Sebastian >> >> ----- Mail original ----- >>> De: "Richard O'Keefe" <raoknz(a)gmail.com> >>> Ã: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >>> EnvoyÃ©: Vendredi 3 Mai 2024 12:28:16 >>> Objet: [Pharo-users] Re: Getting started with the easy projects >> >>> What I was really asking was about the very basic mechanics of it. >>> "Where are the instructions about how to sign up" >>> meant "do I have to register somewhere and if so where and how?" >>> "Where are the instructions about what to do" >>> meant "suppose I have registered and have the latest Pharo open >>> on my laptop; how do I connect to the repository, how do I submit >>> a change for review?" I have been playing with Pharo since version 1 >>> but I've never actually connected to a repository. >>> >>> I think a "Complete Idiot's Guide to Getting Started with Distributed >>> Development in Phraro" probably already exists somewhere, I just >>> don't know where to look for it. >>> >>> On Sat, 27 Apr 2024 at 21:05, stephane ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Hi richard >>>> >>>> https://github.com/orgs/pharo-project/projects/8 >>>> lists some easy projects. I'd like to make a contribution. >>>> >>>> >>>> Cool. >>>> The first thing I suggest is to take the stupidiest issue like adding a comment >>>> in a method >>>> or fixing a badly written comment and make a PR. >>>> I like to do this trivial things because there are easy to give a positive slant >>>> on my energy. >>>> >>>> Where are the instructions on how to sign up and what >>>> to do? Fair warning, I'll probably need a bit of hand-holdingâ¦ >>>> >>>> >>>> For the contributions feel free to pick what you like >>>> >>>> - Some easy things are: better comments, improving test coverage >>>> - Now Iâm pretty sure that we can get collection improvements >>>> - This one could interest you: underscores in numeric literals >>>> https://github.com/pharo-project/pheps/pull/18/files >>>> We had long design discussions and I think that the result is good but we never >>>> got the time to implement it. >>>> >>>> S >>>> >>>> >>>> >>>> >>>> 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 >>>> >>>> >>>> >>>> > > 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 > > > > > 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

May 16, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Answering my own question - it writes out file to the disk outside of Iceberg's knowledge - so you have to open a terminal and: git commit -a -m "Update tonel formal to V3" git push I 've submitted a PR to improve the instructions in the open docs repo. On Thu, 16 May 2024, at 12:09 AM, Tim Mackinnon wrote: > Hey Cyril - before I raise a bug, I've tried running that script on > CodeParadise and first off, its missing a declaration for respository > (although I think you can execute and get away with it). > > I also hit an error that it assume that every package of your project > is loaded - so it probably needs a comment caveat to explain that you > shoujld have loaded every project before running it (or we correct the > internal code that makes that assumption). > > But having run it - I'm a bit confused what should happen? I was > expecting dirty projects that I would then commit (having made a branch > to submit a PR on) - however no packages appear dirty and so there is > nothing to commit? I guess I'm a bit confused what > #forInternalStoreFileOut: on: does ? Is it writing something out to > disk - and if so, what do we do with that in pharo - or are we expected > to do something on the terminal? If so - the instructions don't make > that very clear? > > To be honest I was expecting something that caused something that cause > a comment change that would cause every package to force a commit in > the iceberg browser? > > Can you clarify a bit more please? > > Tim > > On Mon, 13 May 2024, at 10:45 AM, Cyril FERLICOT-DELBECQUE via > Pharo-users wrote: >> Hi, >> >> Here are some additional notes to what was already answered. >> >> If you want to convert all the files of a repository at once to avoid >> to have multiple PR with format changes you can use this script and >> commit the resulting files: >> >> | projectName | >> projectName := 'Spec2'. >> repository := IceRepository repositories detect: [ :repo | repo name = >> projectName ]. >> repository workingCopy packages do: [ :pkg | >> IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion >> mcVersion on: repository ] >> >> Also, if you work on a project both in p12 and p11, you can avoid the >> ping pong by fixing a version of tonel in the properties file. The file >> to update is the .properties that is in the source folder and it should >> look like this: >> >> { >> #format : #tonel, >> #version: #'1.0' >> } >> >> P12 will take into account the tonel version asked and use it. In >> previous version of Pharo, this additional line will be ignored and >> Tonel v1 will be used. >> >> With both of those options it should be possible to reduce the pain of >> the format update. >> >> Have a nice day >> >> -- >> Cyril Ferlicot-Delbecque >> https://ferlicot.fr >> >> >> On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>> >>> It seems like a change whose consequences need some attention ? >>> >>> What are others doing? >>> >>> Tim

May 15, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Cyril - before I raise a bug, I've tried running that script on CodeParadise and first off, its missing a declaration for respository (although I think you can execute and get away with it). I also hit an error that it assume that every package of your project is loaded - so it probably needs a comment caveat to explain that you shoujld have loaded every project before running it (or we correct the internal code that makes that assumption). But having run it - I'm a bit confused what should happen? I was expecting dirty projects that I would then commit (having made a branch to submit a PR on) - however no packages appear dirty and so there is nothing to commit? I guess I'm a bit confused what #forInternalStoreFileOut: on: does ? Is it writing something out to disk - and if so, what do we do with that in pharo - or are we expected to do something on the terminal? If so - the instructions don't make that very clear? To be honest I was expecting something that caused something that cause a comment change that would cause every package to force a commit in the iceberg browser? Can you clarify a bit more please? Tim On Mon, 13 May 2024, at 10:45 AM, Cyril FERLICOT-DELBECQUE via Pharo-users wrote: > Hi, > > Here are some additional notes to what was already answered. > > If you want to convert all the files of a repository at once to avoid > to have multiple PR with format changes you can use this script and > commit the resulting files: > > | projectName | > projectName := 'Spec2'. > repository := IceRepository repositories detect: [ :repo | repo name = > projectName ]. > repository workingCopy packages do: [ :pkg | > IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion > mcVersion on: repository ] > > Also, if you work on a project both in p12 and p11, you can avoid the > ping pong by fixing a version of tonel in the properties file. The file > to update is the .properties that is in the source folder and it should > look like this: > > { > #format : #tonel, > #version: #'1.0' > } > > P12 will take into account the tonel version asked and use it. In > previous version of Pharo, this additional line will be ignored and > Tonel v1 will be used. > > With both of those options it should be possible to reduce the pain of > the format update. > > Have a nice day > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >> >> It seems like a change whose consequences need some attention ? >> >> What are others doing? >> >> Tim

May 15, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Tim Mackinnon

Davide - I encourage you to consider whether you can do that tiny bit more from "posting a working on this list". You can of course choose what you want, and Pharo is free for everyone, but as is often mentioned - its a project that belongs to everyone and the more we can each do, the better (and quicker) it gets. I too started out thinking I was too busy, and that posting a solution that "others" could run with was enough - but then I noticed how busy some of the key people are, fixing things that are beyond my perceived capability. And it dawned on my that I could at least create an issue on Github with my poposed fix and some more details around the problem (and maybe post that here to widen conversation) - this at least made things more efficient to get fixed. And then I noticed sometimes those fixes never got applied, and I realised that those key people really are super busy and I want them to fix/improve the harder stuff - and honestly - it wasn't that much harder to launch a fresh image - create branch, apply my fix and submit a PR - in fact I learned a lot more doing it AND I helped those busy people too. win/win. So why not consider giving it a go next time? In fact your settings idea would be a great one to flex your passion on? Of course - posting a fix is helpful - but at least create the issue. Tim On Tue, 14 May 2024, at 6:17 AM, Davide Varvello wrote: > Hi Tim, > > I get it and appreciate your suggestion. My approach to contribute to > the Pharo community is when I can solve an issue to post my solution or > a workaround on this list, I know pushing code to github would be > better but I canât do more than this actually, sorry. > > Cheers > Davide > > > > > > > > On Friday, May 10, 2024 at 07:03:55 PM GMT+2, Tim Mackinnon > <tim(a)testit.works> wrote: > > > > > > > Davide - why don't you submit a PR? I'm sure you can figure out how to > add a settings to the system (can't offhand remember, but there are > examples - and you can ask on the discord) and it would be a nice > contribution to make . > > Its all the little contributions that make the system better - I know > I've been there, and saw how the others do it and so had a go. > > Tim > > On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: >> Hi Guys, >> It seems to me the default size of a lot of windows is too small, so after some search and thanks to thisÂ https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ >> >> I discovered I can change the default size of many type of windows simply changing ClyBrowserMorph>>initialExtent. >> HTH >> >> It would be good to be able to manage the size of windows in Settings >> >> Cheers >> Davide >>

May 15, 2024

Fwd: Submission is open for the ESUG 2024 Innovation Technology Awards

by Noury Bouraqadi

---------- Forwarded Message --------- From: Noury Bouraqadi <bouraqadi(a)gmail.com> Subject: Submission is open for the ESUG 2024 Innovation Technology Awards Date: May 14 2024, at 5:39 pm To: Members ESUG <esug-list(a)lists.esug.org> Dear fellow Smalltalkers, Please find below the call of the call for submissions to the ESUG 2024 Innovation Technology Awards. Best, Noury ---- Innovation Technology Awards 19th Edition Have you developed a cool Smalltalk project you want to share? Developers of any Smalltalk-based software can participate (https://forms.gle/8k8DwauZj8VJb6cu9) During the conference, participants demonstrate their systems in a session Monday July 8th, during which the conference attendees vote. The top 3 teams will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results will be announced in the Awards ceremony that is held during the social event. Submit now (https://forms.gle/8k8DwauZj8VJb6cu9) Submission Deadline: Sunday June 30th

May 14, 2024

Re: [Pharo-dev] Open Call: Object-Centric Breakpoints experiment

by Steven Costiou

Dear community, we are still looking for participants for our experiment in the EVREF team! Please help us! We need 15 more participants, if you are interested and if you believe you can work your way around a debugger, the experiment is fully available online here (using Pharo 9): https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd We would like to show our results at ESUG, but for that we really need these 15 additional participations so that we can trust the results better. Thanks in advance, and many thanks to the people who already participated! Steven. Le 2024-02-02 14:14, Steven Costiou a Ã©crit : > Dear Community, > > as part of a research project in the EVREF team, we are looking for people to participate to an empirical experiment on object-centric breakpoints - a debugging tool present in Pharo 9. > > Many people from the community already participated, and we thank them very much ð > > We are still looking for participants, we need 40 people to do the experiment! > > Please help us, in return it helps us understand better our tools and their impact and therefore build better tools for the Pharo community! > > For those who want to know a bit more, see my original email below. > For those who just want to jump at the experiment, you can go there https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd > > Thanks in advance ð > Steven. > > --- > > We would like to invite you to participate to our experimental study on Object-Centric Breakpoints. > This study aims to evaluate and to understand how Object-Centric Breakpoints impacts the debugging activity. > > This experiment takes place in **Pharo 9**. > In this experiment, we ask you to solve 2 debugging tasks, one with standard Pharo tools and one other with Object-Centric Breakpoints. > Between the two tasks, you will have to follow a tutorialand warmup tasks to learn how to use the tool. > > **How to Participate:** > All instructions are here, please read them carefully: https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd > > **About the Experiment:** > > The experiment last between 40 minutes and 2 hours. > Participants should have experience with Pharo development and debugging. > We recommend having more than 6 months experience in Pharo and debugging in general. > You will gain insights into the Object-Centric Breakpoints approach and contribute to advancements in debugging research. > > Help us to build better debugging tools that help you debug! > > **Some constraints:** > > - You are not allowed to load external tools and baselines, but you can use anything that is in the base image > - Please do the experiment in one shot if possible without interruptions > - The experiment sends anonymous data to our inria server, please make sure that you have a valid internet connection > - Please try to use the object-centric breakpoints when the experimental framework asks you to > > **Notes:** > Participation is voluntary, and everything is anonymous. > You can abandon the experiment at any point (and your data will be discarded). > For any question, you can contact us: steven.costiou(a)inria.fr and valentin.bourcier(a)inria.fr > > Thank you for considering participating in our study. > Your contribution will be valuable in advancing the field of debugging and helping us understand what tools we need to build for Pharo. > > Sincerely, > Steven and Valentin, > EVREF team, Inria

May 14, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Davide Varvello

Hi Tim, I get it and appreciate your suggestion. My approach to contribute to the Pharo community is when I can solve an issue to post my solution or a workaround on this list, I know pushing code to github would be better but I canât do more than this actually, sorry. Cheers Davide On Friday, May 10, 2024 at 07:03:55 PM GMT+2, Tim Mackinnon <tim(a)testit.works> wrote: Davide - why don't you submit a PR? I'm sure you can figure out how to add a settings to the system (can't offhand remember, but there are examples - and you can ask on the discord) and it would be a nice contribution to make . Its all the little contributions that make the system better - I know I've been there, and saw how the others do it and so had a go. Tim On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: > Hi Guys, > It seems to me the default size of a lot of windows is too small, so after some search and thanks to thisÂ https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ > > I discovered I can change the default size of many type of windows simply changing ClyBrowserMorph>>initialExtent. > HTH > > It would be good to be able to manage the size of windows in Settings > > Cheers > Davide >

May 14, 2024

Re: [Pharo-dev] This week (19/2024) on the Pharo Issue Tracker

by stephane ducasse

Yes I understood that after sending my mail > On 13 May 2024, at 11:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Only the first issue is for Pharo 12, all the other for Pharo 13. > (the idea is to have just one headline Pharo 12 for all the issues backported) > > Marcus > >> On 13 May 2024, at 15:31, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I imagine that this is for Pharo 13 >> >> S >> >>> On 13 May 2024, at 03:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> # Pharo 12 >>> >>> - 16576-Problem-with-completion-in-the-tutorial #16582 >>> https://github.com/pharo-project/pharo/pull/16582 >>> >>> >>> # Virtual Machine >>> >>> - Bump to MacOS 11 and above #792 >>> https://github.com/pharo-project/pharo-vm/pull/792 >>> >>> - Do not use asserta: in a statement #788 >>> https://github.com/pharo-project/pharo-vm/pull/788 >>> >>> - Moving pharo.signatures files for OSX Bundle to Resources folder #770 >>> https://github.com/pharo-project/pharo-vm/pull/770 >>> >>> >>> # Features >>> >>> - New debugger extension model to display dynamic extensions #739 >>> https://github.com/pharo-spec/NewTools/pull/739 >>> >>> - add asAccessor #16579 >>> https://github.com/pharo-project/pharo/pull/16579 >>> >>> - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 >>> https://github.com/pharo-project/pharo/pull/16555 >>> >>> - add two's complement display for negative integers #746 >>> https://github.com/pharo-spec/NewTools/pull/746 >>> >>> # Fixes >>> >>> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 >>> https://github.com/pharo-project/pharo/pull/16510 >>> >>> - Taskbar option to close windows hidden behind other windows #16552 >>> https://github.com/pharo-project/pharo/pull/16552 >>> >>> - prof stef lesson view did not understand has binding of #16578 >>> https://github.com/pharo-project/pharo/pull/16578 >>> >>> - fix precedence computation #16581 >>> https://github.com/pharo-project/pharo/pull/16581 >>> >>> # Refactoring Engine >>> >>> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 >>> https://github.com/pharo-project/pharo/pull/16600 >>> >>> - Refactor: preconditions return array of preconditions by default #16527 >>> https://github.com/pharo-project/pharo/pull/16527 >>> >>> >>> # Rules >>> >>> - add ReOverridingExtentsionMethod rule #16550 >>> https://github.com/pharo-project/pharo/pull/16550 >>> >>> - add rule to avoid that TestCase rely on Initialize #16513 >>> https://github.com/pharo-project/pharo/pull/16513 >>> >>> # Tests (Green tests on CI) >>> >>> - Fix testCodeCruftLeftInMethods #16598 >>> https://github.com/pharo-project/pharo/pull/16598 >>> >>> - Update roassal to v1.06d #16595 >>> https://github.com/pharo-project/pharo/pull/16595 >>> >>> - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 >>> https://github.com/pharo-project/pharo/pull/16584 >>> >>> - 16569-CI-Pharo13-code-with-halt-was-merged #16570 >>> https://github.com/pharo-project/pharo/pull/16570 >>> >>> - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 >>> https://github.com/pharo-spec/NewTools/pull/712 >>> >>> >>> # Cleanups >>> >>> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 >>> https://github.com/pharo-project/pharo/pull/16563 >>> >>> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 >>> https://github.com/pharo-project/pharo/pull/16588 >>> >>> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 >>> https://github.com/pharo-project/pharo/pull/16586 >>> >>> - Changed 'Transcript show:' construct to 'self trace' #16385 >>> https://github.com/pharo-project/pharo/pull/16385 >>> >>> - removing dependency to UIManager in StFuelStackCommand #745 >>> https://github.com/pharo-spec/NewTools/pull/745 >>> >>> # Documentation >>> >>> - Update CONTRIBUTING.md #16575 >>> https://github.com/pharo-project/pharo/pull/16575 >> >> 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 >> >> >> >> >> > 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

May 14, 2024