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

[ANN] docker-pharo-vm v10.3.0-2024-07-30 [v10.3.0 [2024-07-30]] released!

by Buenos Aires Smalltalk

July 30, 2024

Re: TelePharo status

by Denis Kudriashov

Hi Gerry. I started to adopt it for NewTools but I don't have time currently to finish it. Kind of abandon project to be honest. Maybe one day I will come back to it.. Regards, Denis Ð¿Ð½, 29 Ð¸ÑÐ». 2024â¯Ð³., 09:19 Gerry Weaver <gerryw(a)compvia.com>: > Hello All, > > Are there any plans to get TelePharo working again? I've been checking > when each new version is released, but no luck so far. I haven't tried > version 12, because I assume it is not working. I'm thinking about a > project where it would be pretty cool to have TelePharo. Unfortunately, > I lack the exprerience with Pharo to attempt to fix it myself. > > > -- > Thanks, > Gerry > >

July 29, 2024

TelePharo status

by Gerry Weaver

Hello All, Are there any plans to get TelePharo working again? I've been checking when each new version is released, but no luck so far. I haven't tried version 12, because I assume it is not working. I'm thinking about a project where it would be pretty cool to have TelePharo. Unfortunately, I lack the exprerience with Pharo to attempt to fix it myself. -- Thanks, Gerry

July 29, 2024

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

by Marcus Denker

The most important not obvious news of the week: We managed to get the CI in a good shape again! Test are now green for all three platforms. This is one of these aspects of development that are easily overlooked: Just keeping the CI green and running is far more work in a real project than you would naively think. Summer break: the weekly mails (but not the improvements to Pharo!) will take a break. In the week of 26/08 we post the weeksly logs for weeka 31-34. # Pharo 12 Backports - Automatically type 'NULL' arguments in FFI (backport to P12) #16926 https://github.com/pharo-project/pharo/pull/16926 - [Backport] Update FormSet to not recompute each scalling all the time #16887 https://github.com/pharo-project/pharo/pull/16887 # Fixes - Fix bug in protocol management of Traits #16936 https://github.com/pharo-project/pharo/pull/16936 - Instance of NullWorldRenderer did not understand #fullscreenMode: when run headless / in CI #16925 https://github.com/pharo-project/pharo/pull/16925 - Catch CmCommandAborted in Calypso #16920 https://github.com/pharo-project/pharo/pull/16920 - Fixes icon for packages drop list in StRequestClassPresenter #16856 https://github.com/pharo-project/pharo/pull/16856 - Handles permission problems on FileBrowser #813 https://github.com/pharo-spec/NewTools/pull/813 - Use equality to compare file references in file navigation system #811 https://github.com/pharo-spec/NewTools/pull/811 # Improvements - Enable specification of a comparison strategy to compare list items #1573 https://github.com/pharo-spec/Spec/pull/1573 - Improve IconStyler highlight to be base on theme #16943 https://github.com/pharo-project/pharo/pull/16943 - Add isPackage #16935 https://github.com/pharo-project/pharo/pull/16935 # Rules - improve ReCollectionProtocolRule #16918 https://github.com/pharo-project/pharo/pull/16918 - Deprecated package #16931 https://github.com/pharo-project/pharo/pull/16931 - change rules description UI #16929 https://github.com/pharo-project/pharo/pull/16929 # Cleanup - ListView-Tests should depends on Tests #1576 https://github.com/pharo-spec/Spec/pull/1576 - ListView adapters should be close to morphic adapters #1575 https://github.com/pharo-spec/Spec/pull/1575 - Fix dependency test #806 https://github.com/pharo-spec/NewTools/pull/806 - Remove MCMergeBrowser #16950 https://github.com/pharo-project/pharo/pull/16950 - Monticello: remove dead code and some Morphic UI #16949 https://github.com/pharo-project/pharo/pull/16949 - Move UndefinedClassVariable out of the Kernel #16947 https://github.com/pharo-project/pharo/pull/16947 - Remove useless method: CompiledMethod >> argumentNames #16937 https://github.com/pharo-project/pharo/pull/16937

July 26, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by Tim Mackinnon

Thats a great set of observations Richard - I think I'd want it to work like you have described too - probably showing an inherited method in a light grey to indicate its inherited (but dark enough so you can compare it to the one on the other side. I could potentially forsee an option where you could "show all inherited" methods on both sides to check how close objects are (in this case, probably up to the point where the inheritance trees unite - for many thats object). Another interesting (though experiment) option is to also show overriden methods and make space for things to keep lining up. Not totally sure on this - but thinking it might reveal accidental overrides or expose smells (again - just thinking aloud though). There's lots of interesting room to explore things in this tool, Tim p.s. Agree on the scroll behaviour and also the jump to next. On Thu, 25 Jul 2024, at 2:19 PM, Richard O'Keefe wrote: > OK, so I tried Class-diff in Pharo 11. I noticed two issues. > (1) I expected it to work like kdiff3, where scrolling scrolls both panes. > I'm so used to flying around differences using > Next/Previous/Last/First Difference buttons that I do very little > scrolling in kdiff3, but when I do scroll, it does its best to keep > the two panes aligned. > (2) Comparing Array and String, I eventually figured out that I was > being shown selectors *defined* in each class, but no selectors > *inherited* by a class. For example, String canUnderstand: #asArray > but inherits it, so it's not shown in the String pain, while Array > defines it. This *looks* like a "one class has it and the other lacks > it" case but it's *actually" a "both classes have it and it's > different in each", so a difference I'd really like to see. > I tracked this down to > self aligner > align: self sourceClass selectors sort > with: self targetClass selectors sort. > in updateAlignment, Changing that to > self aligner > align: self sourceClass allSelectors asArray sort > with: self targetClass allSelectors asArray sort > got me closer to what I wanted, but then accessing the source code of > inherited methods didn't work because inherited methods, by > definition, aren't in the class's own method dictionary. I could work > around that too, but it's 1:19 AM where I am. In fact that's not > quite what I want anyway. I don't want to be shown methods inherited > by *both* classes from Object (although methods inherited from Object > by one class and redefined or inherited from another class by the > other are ones I do want to see). > > On Wed, 24 Jul 2024 at 14:06, Richard O'Keefe <raoknz(a)gmail.com> wrote: >> >> Thanks for the advice about Spec2. >> I was keen to try Class-diff out, so I fired up Pharo, followed the >> installation instructions with no problems, and then tried the >> example. >> The example got a run-time error, and I expect that it's because the >> Pharo release I fired up was Pharo 9. >> >> Which release(s) of Pharo is Class-diff intended to work with? >> >> On Tue, 23 Jul 2024 at 23:38, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >> > >> > >> > Thanks for your nice feedback Richard, I will sketch something and see how it goes. >> > >> > About learning Spec2, for me, the best resource is to directly use the image examples. In the main menu, you have "Help -> Spec 2 demo" and "Help -> Spec 2 examples". And you also have the book in https://github.com/SquareBracketAssociates >> > >> > HernÃ¡n >> > >> > >> > El mar, 23 jul 2024 a las 10:30, Richard O'Keefe (<raoknz(a)gmail.com>) escribiÃ³: >> >> >> >> That's a very nice tool. There are two tweaks I'd like to see. >> >> Two classes having methods with the same *name* isn't the same as two >> >> classes having the same *method*. >> >> When the two classes have a method with the same name, there are at >> >> least three possibilities: >> >> >> >> - The methods are the same method >> >> >> >> - The methods are different, but the name is defined in some common >> >> superclass, so they had better be related methods. >> >> >> >> - The methods are completely unrelated, like #next in ReadStream and LIFOQueue. >> >> >> >> The third case applies to every method. Perhaps the best way >> >> therefore is to show >> >> something in the header, like >> >> >> >> (score) diff of descendants of <nearest common superclass> >> >> <column> <column> >> >> >> >> The first and second cases are the ones I want to tell apart so that I >> >> don't spend any time looking >> >> for differences that aren't there. >> >> >> >> What's the best way to learn how to use Spec2? >> >> >> >> On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand >> >> <hernan.morales(a)gmail.com> wrote: >> >> > >> >> > Dear Pharo community, >> >> > >> >> > I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. >> >> > >> >> > The project location is on GitHub: >> >> > >> >> > https://github.com/hernanmd/class-diff >> >> > >> >> > Feel free to send comments and contributions via PRs. >> >> > Have a great day, >> >> > >> >> > HernÃ¡n >> >> >

July 25, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by Richard O'Keefe

OK, so I tried Class-diff in Pharo 11. I noticed two issues. (1) I expected it to work like kdiff3, where scrolling scrolls both panes. I'm so used to flying around differences using Next/Previous/Last/First Difference buttons that I do very little scrolling in kdiff3, but when I do scroll, it does its best to keep the two panes aligned. (2) Comparing Array and String, I eventually figured out that I was being shown selectors *defined* in each class, but no selectors *inherited* by a class. For example, String canUnderstand: #asArray but inherits it, so it's not shown in the String pain, while Array defines it. This *looks* like a "one class has it and the other lacks it" case but it's *actually" a "both classes have it and it's different in each", so a difference I'd really like to see. I tracked this down to self aligner align: self sourceClass selectors sort with: self targetClass selectors sort. in updateAlignment, Changing that to self aligner align: self sourceClass allSelectors asArray sort with: self targetClass allSelectors asArray sort got me closer to what I wanted, but then accessing the source code of inherited methods didn't work because inherited methods, by definition, aren't in the class's own method dictionary. I could work around that too, but it's 1:19 AM where I am. In fact that's not quite what I want anyway. I don't want to be shown methods inherited by *both* classes from Object (although methods inherited from Object by one class and redefined or inherited from another class by the other are ones I do want to see). On Wed, 24 Jul 2024 at 14:06, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > Thanks for the advice about Spec2. > I was keen to try Class-diff out, so I fired up Pharo, followed the > installation instructions with no problems, and then tried the > example. > The example got a run-time error, and I expect that it's because the > Pharo release I fired up was Pharo 9. > > Which release(s) of Pharo is Class-diff intended to work with? > > On Tue, 23 Jul 2024 at 23:38, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > > > > > Thanks for your nice feedback Richard, I will sketch something and see how it goes. > > > > About learning Spec2, for me, the best resource is to directly use the image examples. In the main menu, you have "Help -> Spec 2 demo" and "Help -> Spec 2 examples". And you also have the book in https://github.com/SquareBracketAssociates > > > > HernÃ¡n > > > > > > El mar, 23 jul 2024 a las 10:30, Richard O'Keefe (<raoknz(a)gmail.com>) escribiÃ³: > >> > >> That's a very nice tool. There are two tweaks I'd like to see. > >> Two classes having methods with the same *name* isn't the same as two > >> classes having the same *method*. > >> When the two classes have a method with the same name, there are at > >> least three possibilities: > >> > >> - The methods are the same method > >> > >> - The methods are different, but the name is defined in some common > >> superclass, so they had better be related methods. > >> > >> - The methods are completely unrelated, like #next in ReadStream and LIFOQueue. > >> > >> The third case applies to every method. Perhaps the best way > >> therefore is to show > >> something in the header, like > >> > >> (score) diff of descendants of <nearest common superclass> > >> <column> <column> > >> > >> The first and second cases are the ones I want to tell apart so that I > >> don't spend any time looking > >> for differences that aren't there. > >> > >> What's the best way to learn how to use Spec2? > >> > >> On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand > >> <hernan.morales(a)gmail.com> wrote: > >> > > >> > Dear Pharo community, > >> > > >> > I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. > >> > > >> > The project location is on GitHub: > >> > > >> > https://github.com/hernanmd/class-diff > >> > > >> > Feel free to send comments and contributions via PRs. > >> > Have a great day, > >> > > >> > HernÃ¡n > >> >

July 25, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by stephane ducasse

Pharo 12 or 13 or 11 Pharo 9 is quite old S > On 24 Jul 2024, at 04:06, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > Thanks for the advice about Spec2. > I was keen to try Class-diff out, so I fired up Pharo, followed the > installation instructions with no problems, and then tried the > example. > The example got a run-time error, and I expect that it's because the > Pharo release I fired up was Pharo 9. > > Which release(s) of Pharo is Class-diff intended to work with? > > On Tue, 23 Jul 2024 at 23:38, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> >> >> Thanks for your nice feedback Richard, I will sketch something and see how it goes. >> >> About learning Spec2, for me, the best resource is to directly use the image examples. In the main menu, you have "Help -> Spec 2 demo" and "Help -> Spec 2 examples". And you also have the book in https://github.com/SquareBracketAssociates >> >> HernÃ¡n >> >> >> El mar, 23 jul 2024 a las 10:30, Richard O'Keefe (<raoknz(a)gmail.com>) escribiÃ³: >>> >>> That's a very nice tool. There are two tweaks I'd like to see. >>> Two classes having methods with the same *name* isn't the same as two >>> classes having the same *method*. >>> When the two classes have a method with the same name, there are at >>> least three possibilities: >>> >>> - The methods are the same method >>> >>> - The methods are different, but the name is defined in some common >>> superclass, so they had better be related methods. >>> >>> - The methods are completely unrelated, like #next in ReadStream and LIFOQueue. >>> >>> The third case applies to every method. Perhaps the best way >>> therefore is to show >>> something in the header, like >>> >>> (score) diff of descendants of <nearest common superclass> >>> <column> <column> >>> >>> The first and second cases are the ones I want to tell apart so that I >>> don't spend any time looking >>> for differences that aren't there. >>> >>> What's the best way to learn how to use Spec2? >>> >>> On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> wrote: >>>> >>>> Dear Pharo community, >>>> >>>> I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. >>>> >>>> The project location is on GitHub: >>>> >>>> https://github.com/hernanmd/class-diff >>>> >>>> Feel free to send comments and contributions via PRs. >>>> Have a great day, >>>> >>>> HernÃ¡n >>>> 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

July 24, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by Richard O'Keefe

Thanks for the advice about Spec2. I was keen to try Class-diff out, so I fired up Pharo, followed the installation instructions with no problems, and then tried the example. The example got a run-time error, and I expect that it's because the Pharo release I fired up was Pharo 9. Which release(s) of Pharo is Class-diff intended to work with? On Tue, 23 Jul 2024 at 23:38, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > Thanks for your nice feedback Richard, I will sketch something and see how it goes. > > About learning Spec2, for me, the best resource is to directly use the image examples. In the main menu, you have "Help -> Spec 2 demo" and "Help -> Spec 2 examples". And you also have the book in https://github.com/SquareBracketAssociates > > HernÃ¡n > > > El mar, 23 jul 2024 a las 10:30, Richard O'Keefe (<raoknz(a)gmail.com>) escribiÃ³: >> >> That's a very nice tool. There are two tweaks I'd like to see. >> Two classes having methods with the same *name* isn't the same as two >> classes having the same *method*. >> When the two classes have a method with the same name, there are at >> least three possibilities: >> >> - The methods are the same method >> >> - The methods are different, but the name is defined in some common >> superclass, so they had better be related methods. >> >> - The methods are completely unrelated, like #next in ReadStream and LIFOQueue. >> >> The third case applies to every method. Perhaps the best way >> therefore is to show >> something in the header, like >> >> (score) diff of descendants of <nearest common superclass> >> <column> <column> >> >> The first and second cases are the ones I want to tell apart so that I >> don't spend any time looking >> for differences that aren't there. >> >> What's the best way to learn how to use Spec2? >> >> On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >> > >> > Dear Pharo community, >> > >> > I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. >> > >> > The project location is on GitHub: >> > >> > https://github.com/hernanmd/class-diff >> > >> > Feel free to send comments and contributions via PRs. >> > Have a great day, >> > >> > HernÃ¡n >> >

July 24, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by HernÃ¡n Morales Durand

Hi Tim, I know Guille has been working with Metacello issues, but I don't know if specifically on this. But for me, it is correct that by default package loading is not logged by Epicea. Let me know if you open an issue and I will take a look. HernÃ¡n El lun, 22 jul 2024 a las 16:08, Tim Mackinnon (<tim(a)testit.works>) escribiÃ³: > This looks interesting, and I will definitely check it out. > > As a small side query - i've noticed a few times now that people are > giving load instructions like : > > EpMonitor disableDuring: [ > Metacello new > > > I understand that this de-clutters the work history, so its much easier > track real changes - however why isn't there an extension on Metacello in > Pharo, that does this automatically - e.g. #loadWithoutLogging ? > > Then everyones instructions could be much cleaner - and this extension > might also do something clever to log that you loaded a baseline - but not > show all the code loaded? > > I'm curuious on this - and possibly its PR we should submit? > > Tim > > On Mon, 22 Jul 2024, at 7:57 AM, HernÃ¡n Morales Durand wrote: > > Dear Pharo community, > > I am happy to present a new tool designed specifically for comparing > classes in Pharo. It provides a two-sided list of methods, so you can > quickly understand the relationships between two classes. > > The project location is on GitHub: > > https://github.com/hernanmd/class-diff > > Feel free to send comments and contributions via PRs. > Have a great day, > > HernÃ¡n > > >

July 23, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by HernÃ¡n Morales Durand

Thanks for your nice feedback Richard, I will sketch something and see how it goes. About learning Spec2, for me, the best resource is to directly use the image examples. In the main menu, you have "Help -> Spec 2 demo" and "Help -> Spec 2 examples". And you also have the book in https://github.com/SquareBracketAssociates HernÃ¡n El mar, 23 jul 2024 a las 10:30, Richard O'Keefe (<raoknz(a)gmail.com>) escribiÃ³: > That's a very nice tool. There are two tweaks I'd like to see. > Two classes having methods with the same *name* isn't the same as two > classes having the same *method*. > When the two classes have a method with the same name, there are at > least three possibilities: > > - The methods are the same method > > - The methods are different, but the name is defined in some common > superclass, so they had better be related methods. > > - The methods are completely unrelated, like #next in ReadStream and > LIFOQueue. > > The third case applies to every method. Perhaps the best way > therefore is to show > something in the header, like > > (score) diff of descendants of <nearest common superclass> > <column> <column> > > The first and second cases are the ones I want to tell apart so that I > don't spend any time looking > for differences that aren't there. > > What's the best way to learn how to use Spec2? > > On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > > > Dear Pharo community, > > > > I am happy to present a new tool designed specifically for comparing > classes in Pharo. It provides a two-sided list of methods, so you can > quickly understand the relationships between two classes. > > > > The project location is on GitHub: > > > > https://github.com/hernanmd/class-diff > > > > Feel free to send comments and contributions via PRs. > > Have a great day, > > > > HernÃ¡n > > >

July 23, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by Richard O'Keefe

That's a very nice tool. There are two tweaks I'd like to see. Two classes having methods with the same *name* isn't the same as two classes having the same *method*. When the two classes have a method with the same name, there are at least three possibilities: - The methods are the same method - The methods are different, but the name is defined in some common superclass, so they had better be related methods. - The methods are completely unrelated, like #next in ReadStream and LIFOQueue. The third case applies to every method. Perhaps the best way therefore is to show something in the header, like (score) diff of descendants of <nearest common superclass> <column> <column> The first and second cases are the ones I want to tell apart so that I don't spend any time looking for differences that aren't there. What's the best way to learn how to use Spec2? On Mon, 22 Jul 2024 at 18:58, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Dear Pharo community, > > I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. > > The project location is on GitHub: > > https://github.com/hernanmd/class-diff > > Feel free to send comments and contributions via PRs. > Have a great day, > > HernÃ¡n >

July 23, 2024

Re: [ANN] class-diff: a new tool for comparing classes

by Tim Mackinnon

This looks interesting, and I will definitely check it out. As a small side query - i've noticed a few times now that people are giving load instructions like : EpMonitor disableDuring: [ Metacello new I understand that this de-clutters the work history, so its much easier track real changes - however why isn't there an extension on Metacello in Pharo, that does this automatically - e.g. #loadWithoutLogging ? Then everyones instructions could be much cleaner - and this extension might also do something clever to log that you loaded a baseline - but not show all the code loaded? I'm curuious on this - and possibly its PR we should submit? Tim On Mon, 22 Jul 2024, at 7:57 AM, HernÃ¡n Morales Durand wrote: > Dear Pharo community, > > I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. > > The project location is on GitHub: > > https://github.com/hernanmd/class-diff > > Feel free to send comments and contributions via PRs. > Have a great day, > > HernÃ¡n >

July 22, 2024

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

by Marcus Denker

# Pharo 12 - Use identity comparisons when looking for elements in a list #1568 https://github.com/pharo-spec/Spec/pull/1568 - [P12][Backport] adding test to ensure it is possible to recompile code within a bloc with a dead home context twice #785 https://github.com/pharo-spec/NewTools/pull/785 # VM - Improving log of old space limit error reporting #833 https://github.com/pharo-project/pharo-vm/pull/833 # Fixes - 16897-Deprecation--messageText-results-in-MNU #16908 https://github.com/pharo-project/pharo/pull/16908 - Forward port https://github.com/pharo-spec/Spec/pull/1568 #1569 https://github.com/pharo-spec/Spec/pull/1569 - add error handler for latin1 encoding failure #796 https://github.com/pharo-spec/NewTools/pull/796 # Speed - Update FormSet to not recompute each scalling all the time #16886 https://github.com/pharo-project/pharo/pull/16886 # Rules - improve ReCollectionAtCollectionSizeRule #16916 https://github.com/pharo-project/pharo/pull/16916 - Delete ReDeprecateWithFirstCharacterDownshiftedRule and his test #16901 https://github.com/pharo-project/pharo/pull/16901 - tests for rules from style category #16896 https://github.com/pharo-project/pharo/pull/16896 - Small PR to add support to set class rules in the Smallint checker #16864 https://github.com/pharo-project/pharo/pull/16864 - Cyclomatic complexity rule #16851 https://github.com/pharo-project/pharo/pull/16851 - Fixes critics browser problems #797 https://github.com/pharo-spec/NewTools/pull/797 - Add critics on class option #794 https://github.com/pharo-spec/NewTools/pull/794 # Towards a green CI - StClassCritiqueBrowserPresenter: Remove method with Undeclared #799 https://github.com/pharo-spec/NewTools/pull/799 - Fix failing tests making CI to fail #16868 https://github.com/pharo-project/pharo/pull/16868 - fix testThatThereAreNoSelectorsRemainingThatAreSentButNotImplemented #16906 https://github.com/pharo-project/pharo/pull/16906 - Move UnifiedDiffJoinSection to Pharo #16915 https://github.com/pharo-project/pharo/pull/16915 - Move unified diff Morph to Tool-Diff #16909

July 22, 2024

[ANN] class-diff: a new tool for comparing classes

by HernÃ¡n Morales Durand

Dear Pharo community, I am happy to present a new tool designed specifically for comparing classes in Pharo. It provides a two-sided list of methods, so you can quickly understand the relationships between two classes. The project location is on GitHub: https://github.com/hernanmd/class-diff Feel free to send comments and contributions via PRs. Have a great day, HernÃ¡n

July 22, 2024

Re: MethodProxies

by Noury Bouraqadi

Thank you Seb! Noury On Jul 16 2024, at 4:20 pm, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> wrote: > Hello, > > > As presented at ESUG, we have released the new version of MethodProxies for Pharo 12 and 13. > MethodProxies is a library that allows to control message-passing to instrument any method in the system to execute an action before and after a method's execution. We worked a lot on this new version to optimize it to have a low overhead. > > We have also a release for Pharo11 and less but that version does not have our optimizations, but you can use it without any problem. If you really need Pharo 11 and want to use the new fast and optimized version, you can contact me. > > > You can find it here: https://github.com/pharo-contributions/MethodProxies > > Cheers, > Sebastian Jordan > >

July 16, 2024

MethodProxies

by Sebastian Jordan Montano

Hello, As presented at ESUG, we have released the new version of MethodProxies for Pharo 12 and 13. MethodProxies is a library that allows to control message-passing to instrument any method in the system to execute an action before and after a method's execution. We worked a lot on this new version to optimize it to have a low overhead. We have also a release for Pharo11 and less but that version does not have our optimizations, but you can use it without any problem. If you really need Pharo 11 and want to use the new fast and optimized version, you can contact me. You can find it here: [ https://github.com/pharo-contributions/MethodProxies | https://github.com/pharo-contributions/MethodProxies ] Cheers, Sebastian Jordan

July 16, 2024

[ANN] omz-plugin-browser

by HernÃ¡n Morales Durand

Dear Pharo Community, I'm excited to announce the release of omz-plugin-browser, a tool designed to simplify Oh-My-Zsh plugin management in Pharo. This user-friendly graphical interface allows you to effortlessly list, enable, and disable Oh-My-Zsh plugins, streamlining your development workflow. Key features of omz-plugin-browser include: - Intuitive GUI for easy plugin management - Quick listing of available plugins - One-click enabling and disabling of plugins - Seamless integration with Pharo's environment To get started with omz-plugin-browser, please visit https://github.com/hernanmd/omz-plugin-browser I welcome your feedback and contributions to help improve this tool. Please report issues or submit pull requests on our GitHub repository. Happy plugin managing! Best regards, HernÃ¡n

July 15, 2024

Re: [Pharo-dev] [ANN] Pharo Launcher 3.2 released!

by Tim Mackinnon

Just to add to what others have said - the presentation at Esug on 3.2 was very cool. You raised some very interesting use-cases that the command line gives (like using $vars to help manage consistent project naming). So thanks for pushing on this. Tim On Wed, 10 Jul 2024, at 6:45 PM, Christophe Demarey wrote: > Hi all, > > Pharo Launcher 3.2 has just been released! It is available from http://pharo.org/download. > > > Pharo Launcher now comes with a command-line version that you can use from a terminal! > You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/. > This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library. > > New features: > > â¢ Command Line support > > â¢ all commands available in the UI version of Pharo Launcher are supported > â¢ new commands > â¢ create an image from a Pull Request number (from Pharo repository) > â¢ create an image from a build number, a SHA > â¢ create an image and import your code from a repository > â¢ share easily an image (zip file with the Pharo image, the VM to run it and a launch script) > â¢ find easily the Pharo version where a bug was introduced with image *bisect* algorithm > â¢ launch an image with a script > â¢ list running Pharo processes > â¢ When creating an image, the image is now launched automatically > > â¢ CI moved to Github Actions > > Improvements: > > â¢ Better Mac Os system menu > â¢ Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user > â¢ When deleting more than 1 image at a time the message is not clear #594 <https://github.com/pharo-project/pharo-launcher/issues/594> > Bug fixes: > > â¢ Pharo 12.0 build list incomplete #667 <https://github.com/pharo-project/pharo-launcher/issues/667> > â¢ Use "Show" when no image is downloaded yet gives error #570 <https://github.com/pharo-project/pharo-launcher/issues/570> (thanks to @astares <https://github.com/astares>) > â¢ Development mode does not close pharoLauncher application #548 <https://github.com/pharo-project/pharo-launcher/issues/548> > â¢ Using "Show in folder" gives DNU #568 <https://github.com/pharo-project/pharo-launcher/issues/568> (thanks to @astares <https://github.com/astares>) > â¢ Launcher cannot launch Pharo-4.0 image #585 <https://github.com/pharo-project/pharo-launcher/issues/585> > > > Regards, > The Pharo team.

July 14, 2024

Re: [ANN] Pharo Launcher 3.2 released!

by Noury Bouraqadi

Thank you guys! You Rock! ð Noury On Jul 12 2024, at 10:24 am, bajger(a)gmail.com wrote: > Congrats Christophe for the release! Great achievement! I was (am) happy to collaborate on this project. Hopefully community would find it useful - please share your feedback! > > David

July 13, 2024

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

by Noury Bouraqadi

Thank you Marcus for all the time and the good energy you put into both Pharo and ESUG! Noury On Jul 12 2024, at 12:20 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > This week we reached 10.000 closed pull requests on the main repository (see https://github.com/pharo-project/pharo/pulls) > The week did not see many changes merged due to many contributors attending (and giving talks at) this years ESUG conference. > > # Pharo 12 Backports > - [P12] Fix MetacelloRepositoryGroup with duplicated repository #16859 > https://github.com/pharo-project/pharo/pull/16859 > > # Fixes > - Fix: deprecate method refactoring to applicability preconditions as list #16867 > https://github.com/pharo-project/pharo/pull/16867 > > - Fix multiple tests with refactoring driver for duplicate class. #16853 > https://github.com/pharo-project/pharo/pull/16853 > > - [P13] Fix MetacelloRepositoryGroup with duplicated repository #1686 > https://github.com/pharo-project/pharo/pull/16860 > > - ffi: add a cache for array types of same type and size #16877 > https://github.com/pharo-project/pharo/pull/16877 > > # Cleanup > - Update transmissionBlock: -> transmits: #793 > https://github.com/pharo-spec/NewTools/pull/793 >

July 12, 2024

Looking for new adventures

by Koen De Hondt

Dear Pharo Community, As you may have read on my blog <https://all-objects-all-the-time.st/#/blog/posts/1> or heard during my ESUGâ23 presentation, eighteen months ago I entered the Pharo scene after being away from the Smalltalk community for 20 years. For the last one and a half years, I have been a member of a team using Pharo and GemStone. I attended almost all Pharo Sprints in Lille (every last Friday of the month). In this channel, I have informed you about my intention to build a new browser based on Spec. That development has been on the back burner for the last five months because I have been working hard with StÃ©phane Ducasse to finish the book âApplication Building with Spec 2.0â. I have presented at ESUGâ23, and I am sad that I could not attend ESUGâ24 this week. >From the above, my contribution to the Pharo community is clear, and I think my drive to contribute more is also clear. In a few months, I will leave the team I am working with now. Therefore, I am looking for new adventures. If you are looking for a seasoned software developer who likes working in Smalltalk/Pharo very much, please send me a message, and I will be in touch rapidly. Please find more details on my career history on LinkedIn <https://www.linkedin.com/in/koendehondt/>. Best regards, Koen

July 12, 2024

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

by Marcus Denker

This week we reached 10.000 closed pull requests on the main repository (see https://github.com/pharo-project/pharo/pulls) The week did not see many changes merged due to many contributors attending (and giving talks at) this years ESUG conference. # Pharo 12 Backports - [P12] Fix MetacelloRepositoryGroup with duplicated repository #16859 https://github.com/pharo-project/pharo/pull/16859 # Fixes - Fix: deprecate method refactoring to applicability preconditions as list #16867 https://github.com/pharo-project/pharo/pull/16867 - Fix multiple tests with refactoring driver for duplicate class. #16853 https://github.com/pharo-project/pharo/pull/16853 - [P13] Fix MetacelloRepositoryGroup with duplicated repository #1686 https://github.com/pharo-project/pharo/pull/16860 - ffi: add a cache for array types of same type and size #16877 https://github.com/pharo-project/pharo/pull/16877 # Cleanup - Update transmissionBlock: -> transmits: #793 https://github.com/pharo-spec/NewTools/pull/793

July 12, 2024

Re: [ANN] Pharo Launcher 3.2 released!

by bajger＠gmail.com

Congrats Christophe for the release! Great achievement! I was (am) happy to collaborate on this project. Hopefully community would find it useful - please share your feedback! David

July 12, 2024

[ANN] Pharo Launcher 3.2 released!

by Christophe Demarey

Hi all, Pharo Launcher 3.2 has just been released! It is available from http://pharo.org/download. Pharo Launcher now comes with a command-line version that you can use from a terminal! You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/. This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library. New features: Command Line support all commands available in the UI version of Pharo Launcher are supported new commands create an image from a Pull Request number (from Pharo repository) create an image from a build number, a SHA create an image and import your code from a repository share easily an image (zip file with the Pharo image, the VM to run it and a launch script) find easily the Pharo version where a bug was introduced with image bisect algorithm launch an image with a script list running Pharo processes When creating an image, the image is now launched automatically CI moved to Github Actions Improvements: Better Mac Os system menu Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user When deleting more than 1 image at a time the message is not clear #594 <https://github.com/pharo-project/pharo-launcher/issues/594> Bug fixes: Pharo 12.0 build list incomplete #667 <https://github.com/pharo-project/pharo-launcher/issues/667> Use "Show" when no image is downloaded yet gives error #570 <https://github.com/pharo-project/pharo-launcher/issues/570> (thanks to @astares <https://github.com/astares>) Development mode does not close pharoLauncher application #548 <https://github.com/pharo-project/pharo-launcher/issues/548> Using "Show in folder" gives DNU #568 <https://github.com/pharo-project/pharo-launcher/issues/568> (thanks to @astares <https://github.com/astares>) Launcher cannot launch Pharo-4.0 image #585 <https://github.com/pharo-project/pharo-launcher/issues/585> Regards, The Pharo team.

July 10, 2024

Re: Help with PetitParser2 rules

by Rafael Luque

Thank you, Frank. I'll try your suggestion. El dom, 7 jul 2024 a las 6:19, vfclists (<vfclists(a)gmail.com>) escribiÃ³: > > > On Fri, 5 Jul 2024 at 10:39, Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > >> Hi all, >> >> I'm struggling with a small parser using PetitParser2. Here is a fragment >> of some of the rules I'm defining but their behaviour is not as I could >> expect: >> >> andKeyword := 'and' asPParser trim, #letter asPParser not. >> notKeyword := 'not' asPParser trim, #letter asPParser not. >> keyword := andKeyword / notKeyword. >> nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser >> star. >> word := nonKeywordIdentifier, #blank asPParser star. >> words := word star. >> >> The behaviour of the "nonKeywordIdentifier" is the expected: >> >> identifier end parse: 'hello'. "It parses successfully" >> identifier end parse: 'and'. "It fails as 'and' is a keyword" >> >> However the "words" rule's behavior is the following: >> >> words end parse: 'hello Pharo'. "It parses successfully" >> words end parse: 'hello and bye'. "It parses, when I would expect it >> fails because of 'and' is a keyword" >> >> I don't understand why the "words" rule works this way, but I'm starting >> with PetitParser. Any suggestions? >> >> Thank you. >> > > You might consider asking on stackoverflow. > > A PetitParser2 question has been answered there recently. > -- > Frank Church > > ======================= > >

July 7, 2024

Re: Help with PetitParser2 rules

by vfclists

On Fri, 5 Jul 2024 at 10:39, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi all, > > I'm struggling with a small parser using PetitParser2. Here is a fragment > of some of the rules I'm defining but their behaviour is not as I could > expect: > > andKeyword := 'and' asPParser trim, #letter asPParser not. > notKeyword := 'not' asPParser trim, #letter asPParser not. > keyword := andKeyword / notKeyword. > nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser > star. > word := nonKeywordIdentifier, #blank asPParser star. > words := word star. > > The behaviour of the "nonKeywordIdentifier" is the expected: > > identifier end parse: 'hello'. "It parses successfully" > identifier end parse: 'and'. "It fails as 'and' is a keyword" > > However the "words" rule's behavior is the following: > > words end parse: 'hello Pharo'. "It parses successfully" > words end parse: 'hello and bye'. "It parses, when I would expect it fails > because of 'and' is a keyword" > > I don't understand why the "words" rule works this way, but I'm starting > with PetitParser. Any suggestions? > > Thank you. > You might consider asking on stackoverflow. A PetitParser2 question has been answered there recently. -- Frank Church =======================

July 7, 2024

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

by Marcus Denker

Main work this week happend on the CI infrastruture (and getting the test green for Pharo13 again), we did not merge lots of PRs due to that. # Pharo 12 - [P12][Backport] Fix recompilation of dead block twice in debugger #16784 https://github.com/pharo-project/pharo/pull/16784 # Fixes - Improve contrasts of DarkBlueTheme #16822 https://github.com/pharo-project/pharo/pull/16822 # Cleanup - Fixing issue#14145: ycAbstractAllInstVarAccessorsCommand >> variable never set #16820 https://github.com/pharo-project/pharo/pull/16820 - fix #15843: Reduce references to Transcript #16830 https://github.com/pharo-project/pharo/pull/16830 - fixed issue #15252: Cleanup: Small Lint issue in ZnImageExampleDelegate>>#handlePostRequest: #16815 https://github.com/pharo-project/pharo/pull/16815 # Documentation - Updated class comments of UUID and UUIDGenerator #16817 https://github.com/pharo-project/pharo/pull/16817

July 5, 2024

Help with PetitParser2 rules

by Rafael Luque

Hi all, I'm struggling with a small parser using PetitParser2. Here is a fragment of some of the rules I'm defining but their behaviour is not as I could expect: andKeyword := 'and' asPParser trim, #letter asPParser not. notKeyword := 'not' asPParser trim, #letter asPParser not. keyword := andKeyword / notKeyword. nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser star. word := nonKeywordIdentifier, #blank asPParser star. words := word star. The behaviour of the "nonKeywordIdentifier" is the expected: identifier end parse: 'hello'. "It parses successfully" identifier end parse: 'and'. "It fails as 'and' is a keyword" However the "words" rule's behavior is the following: words end parse: 'hello Pharo'. "It parses successfully" words end parse: 'hello and bye'. "It parses, when I would expect it fails because of 'and' is a keyword" I don't understand why the "words" rule works this way, but I'm starting with PetitParser. Any suggestions? Thank you.

July 5, 2024

isLoop 2024: 2nd International School on Live Object-Oriented Programming

by Sebastian Jordan Montano

Hello everyone, We are happy to announce that on August 5-9 Pharo Consortium is organizing the International School on Live Object-Oriented Programming (isLoop 2024) in Montpellier - a sunny French city near the coast of the Mediterranean sea. Participation is free and open to everyone. But if you want to participate, you must fill the registration form as soon as possible: [ https://forms.gle/f8RBnU11MM8BLKeRA | https://forms.gle/f8RBnU11MM8BLKeRA ] More information can be found on our website: [ https://isloop24.pharo.org/ | https://isloop24.pharo.org ] If you have any additional questions, don't hesitate to contact Oleksandr at [ mailto:oleksandr.zaitsev@cirad.fr | oleksandr.zaitsev(a)cirad.fr ] And we would also be grateful if you could share this information with your colleagues and students. See you soon! Oleksandr Zaitsev and Sebastian Jordan

July 2, 2024