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

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