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

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

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Cyril - as mentioned on Discord, thanks for advising and sorting this out (for the bigger changes in P13 - it will be useful to get something in the release notes - but definitely don't want to stand in the way of progress)!. Tim On Mon, 13 May 2024, at 1:55 PM, Cyril FERLICOT-DELBECQUE via Pharo-users wrote: > I added some documentation here:â¯ > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > I hope this helps :) > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> Cyril >> >> could you add that in the wiki somewhere. I will publish something on pharo weekly. >> >> S >> >>> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> 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 >> >> 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 13, 2024

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

by Marcus Denker

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 > > > > >

May 13, 2024

[ANN] docker-pharo-vm v10.2.0-2024-05-13 [v10.2.0 [2024-05-13]] released!

by Buenos Aires Smalltalk

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

Tx! > On 13 May 2024, at 08:55, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > I added some documentation here:â¯ > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > I hope this helps :) > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr <https://ferlicot.fr/> > > On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> Cyril >> >> could you add that in the wiki somewhere. I will publish something on pharo weekly. >> >> S >> >>> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> 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 >> >> 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 13, 2024

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

by stephane ducasse

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

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Cyril FERLICOT-DELBECQUE

I added some documentation here:â¯ https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… I hope this helps :) -- Cyril Ferlicot-Delbecquehttps://ferlicot.fr On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Cyril > > could you add that in the wiki somewhere. I will publish something on pharo weekly. > > S > >> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> 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 > > 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 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

https://pharoweekly.wordpress.com/2024/05/13/about-controling-change-format… > On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> 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 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 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

Cyril could you add that in the wiki somewhere. I will publish something on pharo weekly. S > On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> 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 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 13, 2024

Re: P12 new Tonel formatting and PR implications

by Cyril FERLICOT-DELBECQUE

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 13, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by stephane ducasse

we have the unique feature or rewriting deprecation now this is true is this is why tests help a lot. I migrate regularly all our software: microdown, pillar, moose and more. And this is life. Now do not expect that all the suddent Pharo 10 will improve and see bug fixed. Even apple or microsoft or oracle do not support for free old versions. And the fixed versions of P10 is called P11 and P12. S > On 13 May 2024, at 05:15, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Switch version is never pain free. > Davide > > > > > > > > On Monday, May 13, 2024 at 11:05:39 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > > > > > I understand. > Can you tell us what is blocking you to switch versions? > > > You should know that we did an amazing amount of job fixing a lot of glitches and improving > Pharo over the last two years. > > Would you be interested in a special support for Pharo10 and at which price? Because we were thinking > about a LTS for Pharo but this is not free :). > > Have fun. > > > >>> On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> >>> Not really. Did you check in Pharo 12? >> >> No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. >> Davide >> >> >> >>> We got too busy on more important issues. >> >>> S >> >> >> >> >> >>> On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> >>> Hi Guys, >>> >>> Any news about this issue? It's happening also to me. >>> >>> Cheers >>> Davide >>> >>> >>> >>> >>> >>> >>> On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: >>> >>> >>> >>> >>> >>> Hi Stephane >>> >>> Many thanks for following up on the issue with the extra comment tab in the System Browser. >>> >>> As requested, I have included more information below: >>> >>> Versions >>> Over the last few days, I have seen the issue in >>> Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) >>> I believe this is the latest stable P10 release for Windows 64. >>> It was created as a new image via Pharo Launcher version: 3.0.1 >>> >>> Previously I was using >>> Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) >>> And I was getting the normal comment tab behaviour. >>> I still can see that when I fire up that old image. >>> >>> Background >>> I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. >>> Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. >>> I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. >>> I then posed the question on discord for guidance. >>> >>> Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). >>> This time I didnât make any changes, alter settings, or loading any code or libraries. >>> I checked the simple image and verified that the System Browser issue was happening. >>> Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >>> >>> >>> Cheers and regards >>> Mark >>> Perth, Western Australia >>> >>> From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >>> >>> Hi mark >>> >>> Which version of Pharo are you using? >>> In P11 I saw some regressions. >>> S >>> >>> >>>> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>>> >>>> >>> >>> >>> >> >> >> 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 13, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by Davide Varvello

Switch version is never pain free. Davide On Monday, May 13, 2024 at 11:05:39 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: I understand. Can you tell us what is blocking you to switch versions? You should know that we did an amazing amount of job fixing a lot of glitches and improving Â Pharo over the last two years.Â Would you be interested in a special support for Pharo10 and at which price? Because we were thinking about a LTS for Pharo but this is not free :). Have fun.Â >> On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote:Â > > >> Not really. Did you check in Pharo 12?Â > > No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. > DavideÂ > > > >> We got too busy on more important issues. > >> S > > > > > >> On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> >> >> Hi Guys, >> >> Any news about this issue? It's happening also to me. >> >> Cheers >> Davide >> >> >> >> >> Â Â >> Â Â >> Â Â On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: >> >> >> >> >> >> Hi Stephane >> Â Â Â >> Many thanks for following up on the issue with the extra comment tab in the System Browser. >> Â Â Â >> As requested, I have included more information below: >> Â Â Â >> Versions >> Over the last few days, I have seen the issue in >> Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) >> I believe this is the latest stable P10 release for Windows 64. >> It was created as a new image via Pharo Launcher version: 3.0.1 >> Â Â Â >> Previously I was using >> Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) >> And I was getting the normal comment tab behaviour. >> I still can see that when I fire up that old image. >> Â Â Â >> Background >> I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. >> Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. >> I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. >> I then posed the question on discord for guidance. >> Â Â Â >> Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). >> This time I didnât make any changes, alter settings, or loading any code or libraries. >> I checked the simple image and verified that the System Browser issue was happening. >> Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >> Â Â Â >> Â Â Â >> Cheers and regards >> Mark >> Perth, Western Australia >> Â Â Â >> From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >> Â Â Â >> Hi markÂ >> Â Â Â >> Which version of Pharo are you using? >> In P11 I saw some regressions. >> S >> >> >>> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>> Â Â Â >>> >> Â Â Â >> >> > > > 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 13, 2024

The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by Davide Varvello

From: Davide Varvello <varvello(a)yahoo.com> To: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Monday, May 13, 2024 at 10:43:37 AM GMT+2 Subject: Re: [Pharo-users] The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted... > On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote:Â > Not really. Did you check in Pharo 12?Â No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. DavideÂ > We got too busy on more important issues. >S > On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > Hi Guys, > > Any news about this issue? It's happening also to me. > > Cheers > Davide > > > > >Â Â >Â Â >Â Â On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > > > > > Hi Stephane >Â Â Â > Many thanks for following up on the issue with the extra comment tab in the System Browser. >Â Â Â > As requested, I have included more information below: >Â Â Â > Versions > Over the last few days, I have seen the issue in > Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) > I believe this is the latest stable P10 release for Windows 64. > It was created as a new image via Pharo Launcher version: 3.0.1 >Â Â Â > Previously I was using > Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) > And I was getting the normal comment tab behaviour. > I still can see that when I fire up that old image. >Â Â Â > Background > I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. > Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. > I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. > I then posed the question on discord for guidance. >Â Â Â > Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). > This time I didnât make any changes, alter settings, or loading any code or libraries. > I checked the simple image and verified that the System Browser issue was happening. > Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >Â Â Â >Â Â Â > Cheers and regards > Mark > Perth, Western Australia >Â Â Â > From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >Â Â Â > Hi markÂ >Â Â Â > Which version of Pharo are you using? > In P11 I saw some regressions. > S > > >> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>Â Â Â >> >Â Â Â > > 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 13, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Esteban - understood. So it sounds like - quickly walk through all your project packages - add a little comment "upgrade to new tonel formt" and then commit (with everyone checked in before) sounds like the way to go. I'll get on that with projects that I work with. It does of course imply everyone move up to P12 (from P11) to avoid flip flopping between formats - and I don't think there is any reason to stick to P11 as P12 seems solid and without anything controversial to hold back on. Thanks for pushing things forward. Tim On Mon, 13 May 2024, at 6:31 AM, Esteban Lorenzano via Pharo-users wrote: > Hi, > > This is indeed a noisy change. That's the reason it was a change we were holding back during years, but at a point we needed to do it (there is a spec for tonel format we made together with Gemstone people and at a point, we needed to go to the agreed definition. > > So, yes... this will cause annoying moments until all projects are migrated. My recommendation is to make a PR with the new format and work from there. > > Esteban > > ps: there will be still some noise, next year, since we need to clean up a bit around... I am sorry in advance. > > On 12/05/2024 23:55, stephane ducasse wrote: >> The team will be back from vacationâ¦. last week was a three free days week :). >> >> S >> >>> On 12 May 2024, at 06:21, 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 >> >> 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 13, 2024

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

by Marcus Denker

# 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

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Esteban Lorenzano

Hi, This is indeed a noisy change. That's the reason it was a change we were holding back during years, but at a point we needed to do it (there is a spec for tonel format we made together with Gemstone people and at a point, we needed to go to the agreed definition. So, yes... this will cause annoying moments until all projects are migrated. My recommendation is to make a PR with the new format and work from there. Esteban ps: there will be still some noise, next year, since we need to clean up a bit around... I am sorry in advance. On 12/05/2024 23:55, stephane ducasse wrote: > The team will be back from vacationâ¦. last week was a three free days > week :). > > S > >> On 12 May 2024, at 06:21, 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 > > 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 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

The team will be back from vacationâ¦. last week was a three free days week :). S > On 12 May 2024, at 06:21, 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 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 12, 2024

P12 new Tonel formatting and PR implications

by Tim Mackinnon

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 12, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by stephane ducasse

+ 1000 S > On 10 May 2024, at 13:03, 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 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 12, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by stephane ducasse

Not really. Did you check in Pharo 12? We got too busy on more important issues. S > On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi Guys, > > Any news about this issue? It's happening also to me. > > Cheers > Davide > > > > On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > > Hi Stephane > > > Many thanks for following up on the issue with the extra comment tab in the System Browser. > > > As requested, I have included more information below: > > > Versions > > Over the last few days, I have seen the issue in > > Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) > > I believe this is the latest stable P10 release for Windows 64. > > It was created as a new image via Pharo Launcher version: 3.0.1 > > > Previously I was using > > Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) > > And I was getting the normal comment tab behaviour. > > I still can see that when I fire up that old image. > > > Background > > I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. > > Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. > > I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. > > I then posed the question on discord for guidance. > > > Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). > > This time I didnât make any changes, alter settings, or loading any code or libraries. > > I checked the simple image and verified that the System Browser issue was happening. > > Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ > > > > Cheers and regards > > Mark > > Perth, Western Australia > > > From: stephane ducasse <stephane.ducasse(a)inria.fr> > Sent: Sunday, 8 January 2023 10:43 PM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... > > > Hi mark > > > Which version of Pharo are you using? > > In P11 I saw some regressions. > > S > > > > > On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com <mailto:mark.odonoghue.2010@gmail.com> wrote: > > > > 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 12, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Tim Mackinnon

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 10, 2024