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

Re: [Pharo-dev] [ANN] Pharo 11 Released !

by Santiago Bragagnolo

Partyyy! Thanks to all who made this new release possible! [image: image.png] El jue, 11 may 2023 a las 13:39, Esteban Lorenzano (<estebanlm(a)netc.eu>) escribiÃ³: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > Pharo is a pure object-oriented programming language and a powerful > environment focused on simplicity and immediate feedback. > > > > - Simple & powerful language: No constructors, no types declaration, > no interfaces, no primitive types. Yet a powerful and elegant language with > a full syntax fitting in one postcard! Pharo is objects and messages all > the way down. > - Live, immersive environment: Immediate feedback at any moment of > your development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > - Amazing debugging experience: Pharo environment includes a debugger > unlike anything you've seen before. It allows you to step through code, > restart the execution of methods, create methods on the fly, and much more! > - Pharo is yours: Pharo is made by an incredible community, with more > than 100 contributors for the last revision of the platform and hundreds of > people constantly contributing with frameworks and libraries. > - Fully open-source: Pharo full stack is released under MIT > <https://opensource.org/licenses/MIT> License and available on GitHub > <https://github.com/pharo-project/pharo> > > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of > improvement, clean-up and modularization. Also, we included a number of > usability and speed improvements. A complete list of changes and > improvements is available in our Changelog > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > > Some highlights of this amazing version: > Highlights > Tools > > - Iceberg (the git client/VCS control tool) has received a lot of > tweaks and fixes to work better with GitHub and other Git services. > - Our debugger now incorporates lots of tweaks and notably the > capability of adding bindings in the context interaction model. > - The is a new implementation of rewrite tools and improved > refactoring support. > - There is a new tool: The Document Browser, which presents Microdown > (markdown compatible) documents placed on the web or locally. > - New Tools presented in Calypso (the System Browser) and additional > extended Inspectors. > - All versions of NewTools, Spec, Roassal and Microdown have been > updated with their respective bug fixes and improvements. > > System > > - Extended Full Blocks and Constant Clock closures support. > - Additional Inlining and optimizations > - Bug Fixes and Clean up. > - Ephemeron Finalization support. > > Virtual machine > > - Ephemerons Production Ready. > - Initial support for Single-Instruction Multiple-Data (SIMD). > - Third-Party Dependency Update (Newer versions, Graphic Libraries > using Hardware Acceleration). > - Clean Ups: Remove lots of old code, notably old experiments, and > dead code. > > Development Effort > This new version is the result of 1412 Pull Requests integrated just in > the Pharo repository. We have closed 972 issues and received contributions > from more than 70 different contributors. We have also a lot of work in the > separate projects that are included in each Pharo release: > > > - http://github.com/pharo-spec/NewTools > <https://github.com/pharo-spec/NewTools> > - http://github.com/pharo-spec/NewTools-DocumentBrowser > <https://github.com/pharo-spec/NewTools-DocumentBrowser> > - http://github.com/pharo-spec/Spec > <https://github.com/pharo-spec/Spec> > - http://github.com/pharo-vcs/Iceberg > <https://github.com/pharo-vcs/Iceberg> > - http://github.com/ObjectProfile/Roassal3 > <https://github.com/ObjectProfile/Roassal3> > - http://github.com/pillar-markup/Microdown > <https://github.com/pillar-markup/Microdown> > - http://github.com/pillar-markup/BeautifulComments > <https://github.com/pillar-markup/BeautifulComments> > - http://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > > Contributors > We always say Pharo is yours. It is yours because we made it for you, but > most importantly because it is made by the invaluable contributions of our > great community (yourself). A large community of people from all around the > world contributed to Pharo 11.0 by making pull requests, reporting bugs, > participating in discussion threads, providing feedback, and a lot of > helpful tasks in all our community channels. Thank you all for your > contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

May 11, 2023

[ANN] Pharo 11 Released !

by Esteban Lorenzano

Dear Pharo users and dynamic language lovers: We have released Pharo (https://pharo.org/) version 11! What is Pharo? Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. Fully open-source: Pharo full stack is released under MIT (https://opensource.org/licenses/MIT) License and available on GitHub (https://github.com/pharo-project/pharo) ... more on the Pharo Features page (http://www.pharo.org/features) In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog (https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…) Some highlights of this amazing version: Highlights Tools Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. The is a new implementation of rewrite tools and improved refactoring support. There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. New Tools presented in Calypso (the System Browser) and additional extended Inspectors. All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. System Extended Full Blocks and Constant Clock closures support. Additional Inlining and optimizations Bug Fixes and Clean up. Ephemeron Finalization support. Virtual machine Ephemerons Production Ready. Initial support for Single-Instruction Multiple-Data (SIMD). Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). Clean Ups: Remove lots of old code, notably old experiments, and dead code. Development Effort This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: http://github.com/pharo-spec/NewTools (https://github.com/pharo-spec/NewTools) http://github.com/pharo-spec/NewTools-DocumentBrowser (https://github.com/pharo-spec/NewTools-DocumentBrowser) http://github.com/pharo-spec/Spec (https://github.com/pharo-spec/Spec) http://github.com/pharo-vcs/Iceberg (https://github.com/pharo-vcs/Iceberg) http://github.com/ObjectProfile/Roassal3 (https://github.com/ObjectProfile/Roassal3) http://github.com/pillar-markup/Microdown (https://github.com/pillar-markup/Microdown) http://github.com/pillar-markup/BeautifulComments (https://github.com/pillar-markup/BeautifulComments) http://github.com/pharo-project/pharo-vm (https://github.com/pharo-project/pharo-vm) Contributors We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation

May 11, 2023

Pharo contribution Jenkins end of service

by Christophe Demarey

Hi all, Some years ago, we provided a Jenkins instance to check the health / quality of projects that are not in Pharo core but important for the community: https://ci.inria.fr/pharo-contribution/ <https://ci.inria.fr/pharo-contribution/> Since, we moved to GitHub and GitHub actions are mainly used to achieve the same goal. Therefore there is no more reason to keep this service. Thatâs why we decided to stop the Pharo contribution Jenkins on 12th June 2023. If you need to save some data (job artefacts, job setup), let us know. The server is now up but it has not been updated since a while and can stop working from time to time. On 12th June 2023, we will shutdown the server and all data will be removed. The Pharo team.

May 11, 2023

Re: Packages

by BalÅ¡a Å arenac

Hello, I would just add: for renaming packages prefer refactoring over transformation. `RBRenamePackageRefactoring` is the class that's called when you invoke rename package from the UI. `RBRenamePackageTransformation` is unused class. While it does work it represents code duplication and might not be present in Pharo in the future. BalÅ¡a ------- Original Message ------- On Tuesday, May 9th, 2023 at 10:18, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi Steffen, > > > Le 8 mai 2023 Ã 13:40, Steffen MÃ¤rcker merkste(a)web.de a Ã©crit : > > > > Hi, > > > > is there a way to create an empty package programatically, > > > RPackageOrganizer default createPackageNamed: #packageName > > > and how do I > > rename a package programmatically? > > > You can take a look at RBRenamePackageTransformation class comment. > > > Is there a documentation about packages > > and how exactly their naming scheme relates to tags? > > > > You can get tags with: > (RPackageOrganizer default packageNamed: 'RPackage-Core') actualClassTags > > Inspecting one tag, you can ask its real name: > self categoryName "#'RPackage-Core-Baseâ" > > As you can see, a package tag is prefixed by the package name and a dash. > > > There are some comments in RPackageOrganizer and RPackage. > > > Christophe

May 9, 2023

Re: Packages

by Christophe Demarey

Hi Steffen, > Le 8 mai 2023 Ã 13:40, Steffen MÃ¤rcker <merkste(a)web.de> a Ã©crit : > > Hi, > > is there a way to create an empty package programatically, RPackageOrganizer default createPackageNamed: #packageName > and how do I > rename a package programmatically? You can take a look at RBRenamePackageTransformation class comment. > Is there a documentation about packages > and how exactly their naming scheme relates to tags? You can get tags with: (RPackageOrganizer default packageNamed: 'RPackage-Core') actualClassTags Inspecting one tag, you can ask its real name: self categoryName "#'RPackage-Core-Baseâ" As you can see, a package tag is prefixed by the package name and a dash. There are some comments in RPackageOrganizer and RPackage. Christophe

May 9, 2023

Packages

by Steffen MÃ¤rcker

Hi, is there a way to create an empty package programatically, and how do I rename a package programmatically? Is there a documentation about packages and how exactly their naming scheme relates to tags? Kind regards, Steffen

May 8, 2023

Re: Porting from VW to Pharo

by Steffen MÃ¤rcker

Hi Christian! I'll have a look. Over the weekend, I pushed a bit forward. The #category: worked as expected. However, I observed that Pharo seems to create packages and package tags implicitly. For instance: - If I import the VW packages "Transducers" and "Transducers Tests", two packages are created as expected. - If I import "Transducers-Tests" (note the -) instead, no new package is created and a new package tag is created instead. This means, we have to be careful when porting packages including - in their name from VW to Pharo. So far I could not figure out how to avoid this automatic categorization. But maybe I am missing something as a Pharo newbee. I was also experimenting with baselines. It would be nice to be able to define a baseline already in the export. For now, I created a package "BaselineOf<myProject>" with a class of the same name. It inherits from a dummy class "BaselineOf" in my project transform package. It would be nice to have the baseline in this package too and to create the same-named package during the export. Is there a way to do this right now? I noticed in the wiki that #unusedClasses: is #ignoredNames: now, right? Regarding crypto in PDFtalk: I was just wondering. This is quite difficult to do right, I am certainly missing too much knowledge to do it on my own right now. Maybe some day. ;-) Important: Thank you for your kind support! Best, Steffen Christian Haider schrieb am Samstag, 6. Mai 2023 19:05:22 (+02:00): All references disentangled. Everything should be clean now. 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 . 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 -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos unter vivaldi.com herunter

May 8, 2023

[ANN] docker-pharo-vm v10.0.5-2023.05.07 [v10.0.5 [2023-05-07]] released!

by Buenos Aires Smalltalk

May 8, 2023

Re: Porting from VW to Pharo

by Christian Haider

All references disentangled. Everything should be clean now. 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 <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 6, 2023

Re: [Pharo-dev] Pharo VM Release - v10.0.5

by Noury Bouraqadi

Many thanks to the Pharo team! Noury On May 5 2023, at 7:22 pm, tesonep(a)gmail.com wrote: > 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 (http://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 (mailto:tesonep@gmail.com) > >

May 6, 2023