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

Pharo VM Release - v10.0.5

by tesonep＠gmail.com

Hello, we have released a new version of the Pharo VM for Pharo 11. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download) Also, OBS packages are ready to be updated using your distribution package manager. This is the new VM that will be stable for Pharo 11 release and Pharo 12 alpha, it is also compatible with Pharo 10 images but it is not the default for Pharo 10. Changelog * Testing scavenger tenuring by @PalumboN in https://github.com/pharo-project/pharo-vm/pull/588 * Deleting Pharo image from the VM repo by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/591 * Cleaning Up Third Party Libraries by @tesonep in https://github.com/pharo-project/pharo-vm/pull/581 **Full Changelog**: https://github.com/pharo-project/pharo-vm/compare/v10.0.4...v10.0.5 Thanks a lot, and any doubt please let us know. Cheers, Pablo on behalf of the whole Pharo team. -- Pablo Tesone. tesonep(a)gmail.com

May 5, 2023

Re: Porting from VW to Pharo

by Christian Haider

One more thing about SUnit and SUnitToo: I would not switch, because it all transports nicely to Pharo, because the class is named the same (and the namespace is dropped on transform. Look at TargetSmalltalk class>>#namespacesToIgnore). Christian Von: Steffen MÃ¤rcker <merkste(a)web.de> Gesendet: Freitag, 5. Mai 2023 10:15 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian, I just gave it a try with a virgin 64 Bit 8.3 image and loaded * Smalltalk Transform Project * PDFtalk Project * Pharo FileOut PDFtalk The code loaded fine but I had a few hiccups with the tests. * Many tests use #assert:equals: which SUnitToo (loaded automatically) surprisingly does not provide. * After adding this method to TestCase, all but four test run. The Pattern that is used to match in - testVASmalltalkAddTimeAndVersion - testSqueakAddTimeAndVersion - testPharoAddTimeAndVersion - testGemstoneAddTimeAndVersion Did not take PUL into account. This works: '# From VisualWorksÂ®*, * of * on * at *' * In the following tests, some selectors cannot be found: - testMethodAddsForValuemap - #_gs_printvalueWith: - testMethodAddsForObject - #_gs_Symbol_literalString - testWriteSystemExtensionMethods - #_gs_printvalueWith: Btw, I switched to SUnit to ease Porting to Pharo. I'll have a look into the #category parameter today. OT PDFtalk: Do you have plans to support verifying signatures in PDF files or singing using a certificate? Kind regards, Steffen Christian Haider schrieb am Mittwoch, 12. April 2023 21:07:05 (+02:00): Hi Steffen, thanks for trying and asking! I was loading the code needed into a 8.3, 64bit virgin image and realized that loading is not that straight forward and described too briefly. First, you need a non-default setting for the store prerequisites. I added this to the store access page: <https://wiki.pdftalk.de/doku.php?id=storeaccess> https://wiki.pdftalk.de/doku.php?id=storeaccess . It is critical to load the prereqs from store and not from parcels! The first thing to load is the bundle {Smalltalk Transform Project}. To see examples you need to load the subject of transformation: PDFtalk. You need to load to top bundle {PDFtalk Project} which includes the test classes you are missing in your image. At last, load the [Pharo Fileout PDFtalk] package. I improved the landing page <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> https://wiki.pdftalk.de/doku.php?id=smalltalktransform a bit to make this clearer. I just tried and this loads without errors or warnings. (Actually good that the load did not work for you, because I added a mistake in January which causes a 8.3 image to crash when you open a browser. Sorry for that.) Now you should be all set for generating a fileout of PDFtalk for Pharo (in the current unfinished state). Thanks for spotting the problems with the documentation. I will get over it tomorrow. I am quick in renaming and making structural changes when things are not working as I wantâ¦ But the docs should be correct, of course. About the project structure. Currently, everything belonging to a project, need to be transformed in one go. This is not a big deal, because all code transformations are described on the package level and can be easily recombined as the bundle structure changes. The last piece of the transformation puzzle is to make the transformations modular, so that the renamings of prerequisite packages can be used without the need to transform the prereqs as well. I hope to get at that soonâ¦ In the meantime, I would start with your Core project to get a feel for the mechanics. I am sure the rest will fall nicely into its places. About how to structure your code in Pharo with Git, I donât know much about that. Actually, I would also be interested in some guidelines to bake them into the transformationsâ¦ If you are seriously interested, we could have an online session to hack around with itâ¦ Cheers, Christian Von: Steffen MÃ¤rcker <merkste(a)web.de <mailto:merkste@web.de> > Gesendet: Dienstag, 11. April 2023 17:52 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian and Richard, thanks for your answers. I'll try to go through the process step by step and come back with questions to the list if that's okay. First, after loading the "Pharo Fileout PDFTalk", VW (8.3, 64 Bit) shows two unloadable definitions: - PostscriptInterpreterTests>>_ph_testOperatorNotFound - ColorValueTest>>_ph_testBridgedNamedColors Both classes are not loaded Second, it appears that some of the selectors mentioned on <https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation> https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation have been renamed, e.g., PackageChanges>>unusedClasses More general, regarding project structure. What is the best approach to port a project that consists of multiple loosely coupled packages (not in a bundle) some of which being optional? Like - Package Project Core - Package Project Core Tests (requires Core) - Package Project Extension A (requires Core) - Package Project Extension A Tests (requires Extension A) - Package Project Examples (requires Core and Extension A) And how should I structure this on the Pharo site and in an iceberg repository? One Git repository per package or all in the same? Is there a guide to this or a specific Mooc lesson? Kind regards, Steffen Christian Haider schrieb am Donnerstag, 6. April 2023 18:16:00 (+02:00): Yes, PDFtalk is the only example, because it was created to port that library. Any other uses are welcome. The project has been dormant for a year now because of other obligations, but I hope to resume soon. The documentation is, as Richard notes, in a suboptimal state. I think that the information is still accurate. Any help with this would be welcome, for example by asking questions or by criticizing concrete issues. Christian Von: Richard Sargent < <mailto:richard.sargent@gemtalksystems.com> richard.sargent(a)gemtalksystems.com> Gesendet: Donnerstag, 6. April 2023 17:55 An: Any question about pharo is welcome < <mailto:pharo-users@lists.pharo.org> pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo The best(?) place to start is perhaps <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> https://wiki.pdftalk.de/doku.php?id=smalltalktransform. The only examples are various ports of PDFtalk (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22â¯AM Steffen MÃ¤rcker < <mailto:merkste@web.de> merkste(a)web.de> wrote: Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? <https://wiki.pdftalk.de/doku.php?id=setupvisualworks> https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter. -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos unter vivaldi.com herunter

May 5, 2023

Re: Porting from VW to Pharo

by Christian Haider

Hi Steffen, you have the wrong version of SUnitToo. I guess, yours is loaded from Store (7.10 - 2,tgriggs) from 2013. This doesnât have assert:equals: (interestingly). You need to load the parcel (version '8.1 - 1') (with assert:equals:) Maybe you have used a different setting for the Store prerequisites than https://wiki.pdftalk.de/doku.php?id=storeaccess . (search parcels first). I also published a new version where [SUnitToo] is explicitly marked to load the parcel. To circumvent this annoying issue, I usually load [SUnitToo(ls)] first thing in a new image with the [StoreForPostgreSQL] parcel. I am building a new image and protocol every manual step and run the tests. I thought that I fixed all issuesâ¦ Thank you for the match pattern! I didnât see this, because I donât have the NC version, but use the commercial 8.3. About the failing tests: Thanks! I did not test this in isolationâ¦ I will fix them. Usually, because I work on all dialects, I have also the [(Gemstone|Squeak|VASmalltalk) FileOut PDFtalk] packages loaded. About cryptography: No. I never needed it and I am happy about that :). I have no intention to do something in that direction, but I could help anybody who want to do that. Happy hacking, Christian Von: Steffen MÃ¤rcker <merkste(a)web.de> Gesendet: Freitag, 5. Mai 2023 10:15 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian, I just gave it a try with a virgin 64 Bit 8.3 image and loaded * Smalltalk Transform Project * PDFtalk Project * Pharo FileOut PDFtalk The code loaded fine but I had a few hiccups with the tests. * Many tests use #assert:equals: which SUnitToo (loaded automatically) surprisingly does not provide. * After adding this method to TestCase, all but four test run. The Pattern that is used to match in - testVASmalltalkAddTimeAndVersion - testSqueakAddTimeAndVersion - testPharoAddTimeAndVersion - testGemstoneAddTimeAndVersion Did not take PUL into account. This works: '# From VisualWorksÂ®*, * of * on * at *' * In the following tests, some selectors cannot be found: - testMethodAddsForValuemap - #_gs_printvalueWith: - testMethodAddsForObject - #_gs_Symbol_literalString - testWriteSystemExtensionMethods - #_gs_printvalueWith: Btw, I switched to SUnit to ease Porting to Pharo. I'll have a look into the #category parameter today. OT PDFtalk: Do you have plans to support verifying signatures in PDF files or singing using a certificate? Kind regards, Steffen Christian Haider schrieb am Mittwoch, 12. April 2023 21:07:05 (+02:00): Hi Steffen, thanks for trying and asking! I was loading the code needed into a 8.3, 64bit virgin image and realized that loading is not that straight forward and described too briefly. First, you need a non-default setting for the store prerequisites. I added this to the store access page: <https://wiki.pdftalk.de/doku.php?id=storeaccess> https://wiki.pdftalk.de/doku.php?id=storeaccess . It is critical to load the prereqs from store and not from parcels! The first thing to load is the bundle {Smalltalk Transform Project}. To see examples you need to load the subject of transformation: PDFtalk. You need to load to top bundle {PDFtalk Project} which includes the test classes you are missing in your image. At last, load the [Pharo Fileout PDFtalk] package. I improved the landing page <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> https://wiki.pdftalk.de/doku.php?id=smalltalktransform a bit to make this clearer. I just tried and this loads without errors or warnings. (Actually good that the load did not work for you, because I added a mistake in January which causes a 8.3 image to crash when you open a browser. Sorry for that.) Now you should be all set for generating a fileout of PDFtalk for Pharo (in the current unfinished state). Thanks for spotting the problems with the documentation. I will get over it tomorrow. I am quick in renaming and making structural changes when things are not working as I wantâ¦ But the docs should be correct, of course. About the project structure. Currently, everything belonging to a project, need to be transformed in one go. This is not a big deal, because all code transformations are described on the package level and can be easily recombined as the bundle structure changes. The last piece of the transformation puzzle is to make the transformations modular, so that the renamings of prerequisite packages can be used without the need to transform the prereqs as well. I hope to get at that soonâ¦ In the meantime, I would start with your Core project to get a feel for the mechanics. I am sure the rest will fall nicely into its places. About how to structure your code in Pharo with Git, I donât know much about that. Actually, I would also be interested in some guidelines to bake them into the transformationsâ¦ If you are seriously interested, we could have an online session to hack around with itâ¦ Cheers, Christian Von: Steffen MÃ¤rcker <merkste(a)web.de <mailto:merkste@web.de> > Gesendet: Dienstag, 11. April 2023 17:52 An: Any question about pharo is welcome < <mailto:pharo-users@lists.pharo.org> pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian and Richard, thanks for your answers. I'll try to go through the process step by step and come back with questions to the list if that's okay. First, after loading the "Pharo Fileout PDFTalk", VW (8.3, 64 Bit) shows two unloadable definitions: - PostscriptInterpreterTests>>_ph_testOperatorNotFound - ColorValueTest>>_ph_testBridgedNamedColors Both classes are not loaded Second, it appears that some of the selectors mentioned on <https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation> https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation have been renamed, e.g., PackageChanges>>unusedClasses More general, regarding project structure. What is the best approach to port a project that consists of multiple loosely coupled packages (not in a bundle) some of which being optional? Like - Package Project Core - Package Project Core Tests (requires Core) - Package Project Extension A (requires Core) - Package Project Extension A Tests (requires Extension A) - Package Project Examples (requires Core and Extension A) And how should I structure this on the Pharo site and in an iceberg repository? One Git repository per package or all in the same? Is there a guide to this or a specific Mooc lesson? Kind regards, Steffen Christian Haider schrieb am Donnerstag, 6. April 2023 18:16:00 (+02:00): Yes, PDFtalk is the only example, because it was created to port that library. Any other uses are welcome. The project has been dormant for a year now because of other obligations, but I hope to resume soon. The documentation is, as Richard notes, in a suboptimal state. I think that the information is still accurate. Any help with this would be welcome, for example by asking questions or by criticizing concrete issues. Christian Von: Richard Sargent < <mailto:richard.sargent@gemtalksystems.com> richard.sargent(a)gemtalksystems.com> Gesendet: Donnerstag, 6. April 2023 17:55 An: Any question about pharo is welcome < <mailto:pharo-users@lists.pharo.org> pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo The best(?) place to start is perhaps <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> https://wiki.pdftalk.de/doku.php?id=smalltalktransform. The only examples are various ports of PDFtalk (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22â¯AM Steffen MÃ¤rcker < <mailto:merkste@web.de> merkste(a)web.de> wrote: Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? <https://wiki.pdftalk.de/doku.php?id=setupvisualworks> https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter. -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos unter vivaldi.com herunter

May 5, 2023

Re: Porting from VW to Pharo

by Steffen MÃ¤rcker

Dear Christian, I just gave it a try with a virgin 64 Bit 8.3 image and loaded * Smalltalk Transform Project * PDFtalk Project * Pharo FileOut PDFtalk The code loaded fine but I had a few hiccups with the tests. * Many tests use #assert:equals: which SUnitToo (loaded automatically) surprisingly does not provide. * After adding this method to TestCase, all but four test run. The Pattern that is used to match in - testVASmalltalkAddTimeAndVersion - testSqueakAddTimeAndVersion - testPharoAddTimeAndVersion - testGemstoneAddTimeAndVersion Did not take PUL into account. This works: '# From VisualWorksÂ®*, * of * on * at *' * In the following tests, some selectors cannot be found: - testMethodAddsForValuemap - #_gs_printvalueWith: - testMethodAddsForObject - #_gs_Symbol_literalString - testWriteSystemExtensionMethods - #_gs_printvalueWith: Btw, I switched to SUnit to ease Porting to Pharo. I'll have a look into the #category parameter today. OT PDFtalk: Do you have plans to support verifying signatures in PDF files or singing using a certificate? Kind regards, Steffen Christian Haider schrieb am Mittwoch, 12. April 2023 21:07:05 (+02:00): Hi Steffen, thanks for trying and asking! I was loading the code needed into a 8.3, 64bit virgin image and realized that loading is not that straight forward and described too briefly. First, you need a non-default setting for the store prerequisites. I added this to the store access page: https://wiki.pdftalk.de/doku.php?id=storeaccess . It is critical to load the prereqs from store and not from parcels! The first thing to load is the bundle {Smalltalk Transform Project}. To see examples you need to load the subject of transformation: PDFtalk. You need to load to top bundle {PDFtalk Project} which includes the test classes you are missing in your image. At last, load the [Pharo Fileout PDFtalk] package. I improved the landing page https://wiki.pdftalk.de/doku.php?id=smalltalktransform a bit to make this clearer. I just tried and this loads without errors or warnings. (Actually good that the load did not work for you, because I added a mistake in January which causes a 8.3 image to crash when you open a browser. Sorry for that.) Now you should be all set for generating a fileout of PDFtalk for Pharo (in the current unfinished state). Thanks for spotting the problems with the documentation. I will get over it tomorrow. I am quick in renaming and making structural changes when things are not working as I wantâ¦ But the docs should be correct, of course. About the project structure. Currently, everything belonging to a project, need to be transformed in one go. This is not a big deal, because all code transformations are described on the package level and can be easily recombined as the bundle structure changes. The last piece of the transformation puzzle is to make the transformations modular, so that the renamings of prerequisite packages can be used without the need to transform the prereqs as well. I hope to get at that soonâ¦ In the meantime, I would start with your Core project to get a feel for the mechanics. I am sure the rest will fall nicely into its places. About how to structure your code in Pharo with Git, I donât know much about that. Actually, I would also be interested in some guidelines to bake them into the transformationsâ¦ If you are seriously interested, we could have an online session to hack around with itâ¦ Cheers, Christian Von: Steffen MÃ¤rcker <merkste(a)web.de> Gesendet: Dienstag, 11. April 2023 17:52 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian and Richard, thanks for your answers. I'll try to go through the process step by step and come back with questions to the list if that's okay. First, after loading the "Pharo Fileout PDFTalk", VW (8.3, 64 Bit) shows two unloadable definitions: - PostscriptInterpreterTests>>_ph_testOperatorNotFound - ColorValueTest>>_ph_testBridgedNamedColors Both classes are not loaded Second, it appears that some of the selectors mentioned on https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation have been renamed, e.g., PackageChanges>>unusedClasses More general, regarding project structure. What is the best approach to port a project that consists of multiple loosely coupled packages (not in a bundle) some of which being optional? Like - Package Project Core - Package Project Core Tests (requires Core) - Package Project Extension A (requires Core) - Package Project Extension A Tests (requires Extension A) - Package Project Examples (requires Core and Extension A) And how should I structure this on the Pharo site and in an iceberg repository? One Git repository per package or all in the same? Is there a guide to this or a specific Mooc lesson? Kind regards, Steffen Christian Haider schrieb am Donnerstag, 6. April 2023 18:16:00 (+02:00): Yes, PDFtalk is the only example, because it was created to port that library. Any other uses are welcome. The project has been dormant for a year now because of other obligations, but I hope to resume soon. The documentation is, as Richard notes, in a suboptimal state. I think that the information is still accurate. Any help with this would be welcome, for example by asking questions or by criticizing concrete issues. Christian Von: Richard Sargent <richard.sargent(a)gemtalksystems.com> Gesendet: Donnerstag, 6. April 2023 17:55 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo The best(?) place to start is perhaps https://wiki.pdftalk.de/doku.php?id=smalltalktransform. The only examples are various ports of PDFtalk (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22â¯AM Steffen MÃ¤rcker <merkste(a)web.de> wrote: Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter. -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos unter vivaldi.com herunter

May 5, 2023

This week (18/2023) on the Pharo Issue Tracker

by Marcus Denker

With some last fixes, Pharo11 now is ready for release, Pharo12 improvements continue, with a focus on Protocols/ClassOrganizer, Compiler, Code Completion and CompiledMethodTrailer/sourcePointer simplifications. For the later, these posts to the pharo-dev list have more details: [Pharo12] Simplify CompiledMethod trailer: just support fixed sourcePointers https://lists.pharo.org/empathy/thread/XBAX4TN2F2CBD6VCU4PCAB7KXKTOS5GU [Pharo12] Simpler sourcePointer encoding https://lists.pharo.org/empathy/thread/AZQ3JHTV22XNO5STSII62UJEVE3ANDFN [Pharo12] commentSourcePointer and Metaclass https://lists.pharo.org/empathy/thread/QBVM3DV4NDXETJUH7QVOZCZYGENFGLJB # Pharo11 - 13526-Attempt-to-release-a-shared-cairo-font-face #13574 https://github.com/pharo-project/pharo/pull/13574 - Fix wrong double click #13577 https://github.com/pharo-project/pharo/pull/13577 - Fix/filter #13589 https://github.com/pharo-project/pharo/pull/13589 - Debugger fixes #13592 https://github.com/pharo-project/pharo/pull/13592 - Add new welcomebrowser #13623 https://github.com/pharo-project/pharo/pull/13623 - Make protocol classification a setting #13615 https://github.com/pharo-project/pharo/pull/13615 # Pharo112 ## Clean Blocks - Clean blocks for announcement #13590 https://github.com/pharo-project/pharo/pull/13590 ## SystemOrganizer - Make Smalltalk environnement return a RPackageOrganizer #13403 https://github.com/pharo-project/pharo/pull/13403 - Remove references to SystemOrganization #13632 https://github.com/pharo-project/pharo/pull/13632 - Deprecate SystemOrganization #13497 https://github.com/pharo-project/pharo/pull/13497 ## Protocols / ClassOrganization - Cleanup protocol announcements in ClassOrganization #13646 https://github.com/pharo-project/pharo/pull/13646 - Test ClassOrganization>>#hasProtocol: #13644 https://github.com/pharo-project/pharo/pull/13644 - ClassOrganization classification cleanings #13373 https://github.com/pharo-project/pharo/pull/13373 - Ensure #addSelector:withMethod: classifies methods #13635 https://github.com/pharo-project/pharo/pull/13635 - Reduce cyclomatic complexity of #classify:under: #13630 https://github.com/pharo-project/pharo/pull/13630 - Do not reclassify already classified method #13621 https://github.com/pharo-project/pharo/pull/13621 - Simplify classify:under: #13604 https://github.com/pharo-project/pharo/pull/13604 - Remove ClassOrganization>>#protocolNameOfElement:ifAbsent: #13605 https://github.com/pharo-project/pharo/pull/13605 - Improve #renameProtocolNamed:toBe: #13466 https://github.com/pharo-project/pharo/pull/13466 - Do not rely on #protocolNameOfElement: in Traits #13582 https://github.com/pharo-project/pharo/pull/13582 - Remove usage of #protocolNameOfElement:ifAbsent: in traits #13593 https://github.com/pharo-project/pharo/pull/13593 - Remove hack from ClassOrganization>>protocolNameOfElement: #13653 https://github.com/pharo-project/pharo/pull/13653 ## Improvements - rubric: doit actions on empty selection selects the current expression #13096 https://github.com/pharo-project/pharo/pull/13096 - Simplify code export #13624 https://github.com/pharo-project/pharo/pull/13624 ## Code Completion - Completion complete empty tokens #13638 https://github.com/pharo-project/pharo/pull/13638 - Autocompletion must replace from start of the word if case-insensitivâ¦ #13548 https://github.com/pharo-project/pharo/pull/13548 - Code Completion: multiple fixes on replacements annoying bugs #13625 https://github.com/pharo-project/pharo/pull/13625 - Completion: prepare for empty token #13636 https://github.com/pharo-project/pharo/pull/13636 - Complete super message send #13637 https://github.com/pharo-project/pharo/pull/13637 ## CompiledMethod trailer cleanup / sourcePointer - HEInstaller should take the trailerSize into account #13627 https://github.com/pharo-project/pharo/pull/13627 - this PR introduces CompiledMethod>>#clearSourcePointer and #sourcePointer: #13578 https://github.com/pharo-project/pharo/pull/13578 - Deprecated CompiledMethodTrailer #13579 https://github.com/pharo-project/pharo/pull/13579 - skip some SourceFileArrayTest #13585 https://github.com/pharo-project/pharo/pull/13585 - Fix-SourceFileArrayTest for new encoding #13596 https://github.com/pharo-project/pharo/pull/13596 - #sourceCodeAt: should return nil in failure case #13586 https://github.com/pharo-project/pharo/pull/13586 - Simpler sourcePointer encoding #13583 https://github.com/pharo-project/pharo/pull/13583 - Set #trailerSize to 5 #13580 https://github.com/pharo-project/pharo/pull/13580 - CommentSourcePointer-move-methods-down #13640 https://github.com/pharo-project/pharo/pull/13640 - move commentSourcePointer from ClassDescription to Class #13643 https://github.com/pharo-project/pharo/pull/13643 - fix BehaviorTest>>#testInstSize #13648 https://github.com/pharo-project/pharo/pull/13648 - Faster #setSourcePointer: #13645 https://github.com/pharo-project/pharo/pull/13645 ## Compiler - Add compiler option to not optimise special sends #13569 https://github.com/pharo-project/pharo/pull/13569 - Compiler: do generation #13541 https://github.com/pharo-project/pharo/pull/13541 - Cleanup-optionInlineRepeat-is-default #13614 https://github.com/pharo-project/pharo/pull/13614 - MethodMapTest-use-Compiler #13620 https://github.com/pharo-project/pharo/pull/13620 - Compiler: get requestor #13606 https://github.com/pharo-project/pharo/pull/13606 - AST: add a scanner state #13557 https://github.com/pharo-project/pharo/pull/13557 ## Cleanups / Tests - Remove some dead code in ChangeSet #13622 https://github.com/pharo-project/pharo/pull/13622 - Add test on CompiledCode>>#equivalentTo: #13595 https://github.com/pharo-project/pharo/pull/13595 - extract return from ifTrue:ifFalse: expression #13603 https://github.com/pharo-project/pharo/pull/13603 - extract return from ifTrue:ifFalse: expression #13601 https://github.com/pharo-project/pharo/pull/13601 - use nested and: expression instead of ifTrueifFalse #13611 https://github.com/pharo-project/pharo/pull/13611 - extract return from ifTrue:ifFalse: expression #13609 https://github.com/pharo-project/pharo/pull/13609

May 5, 2023

Re: Pharo being featured in Exercism's Mind Shifting May

by bajger＠gmail.com

Hi Sean! Sorry, I didnât realize link points to private conversation. Anyway, here is result - links to video segments related to Pharo (extending to what Offray already wrote): Introducing Pharo: [https://youtu.be/RpbpnmTfd8w?t=790](https://youtu.be/RpbpnmTfd8w?t=790 "https://youtu.be/RpbpnmTfd8w?t=790") Unique features of Pharo: [https://youtu.be/RpbpnmTfd8w?t=3059](https://youtu.be/RpbpnmTfd8w?t=3059 "https://youtu.be/RpbpnmTfd8w?t=3059") Cheers! David

May 2, 2023

Re: Pharo being featured in Exercism's Mind Shifting May

by Offray Vladimir Luna CÃ¡rdenas

Hi, Thanks for featuring Pharo in the Mind shifting May. For sure it did that to me (as Squeak). Here is the video: https://youtu.be/RpbpnmTfd8w Cheers, Offray On 27/04/23 7:35, bajger(a)gmail.com wrote: > > Hi there! > > Hi there! Pharo track will be promoted on Mind shifting May of > Exercism initiative. Here are some details from one Exercism founder > (Erik): > > https://forum.exercism.org/t/pharo-being-featured-in-mind-shifting-may/5420 > > > There are couple of things we could improve here: > where it is used: weâd definitely find better and newer examples that > ATMs usecaseâ¦ > > where it is great: I would add productivity, once people get through > initial learning curve. It is tightly connected to bullets below > (image based approach and liveness and immersive env.) > > Features: embeddability and interoperability with othe PLs - working > on minimal Pharo image that can be part of e.g. C program and vice versa. > > > So if you have ideas, thoughts how this script can be improved, please > reply! >

May 1, 2023

ESUG Presentation deadline is 1st of JUNE!

by stephane ducasse

Hello people do not wait the last moment, it will help the organizers. ESUG 2023 Call for Presentations 28.8.2023 to 01.9.2023 Lyon France https://esug.github.io <https://esug.github.io/> https://esug.github.io/2023-Conference/conf2023.html Deadline for submission is 1 st of June! ESUG is the premium and fun conference around smalltalk technologies. You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ - Submit a talk, a software or a paper to one of the events. See below. - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. ## Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - XP practices, Development tools, Experience reports - Model driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls and Show us Your Business New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. Show your business 10 min session (Get prepared!!) Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2023-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] Title: [ESUG 2023] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org>

May 1, 2023

ESUG 2023 student volunteer program!

by stephane ducasse

Please distribute to the community and more Call for Student Volunteers Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. Pay attention: the places are limited so do not wait till the last minute to apply. Conference details: Send an email to stephane.ducasse at inria.fr <http://inria.fr/> and Oleksandr Zaitsev <olk.zaytsev(a)gmail.com <mailto:olk.zaytsev@gmail.com>> with: Title: [ESUG 2023 Student] name, gender, university/school, country, email address short description of you and why you are interested in participating For which period is accommodation covered? Accommodation is covered from Sunday 27.8.2023 to 01.9.2023 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. Information about hotel Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already! _______________________________________________

May 1, 2023