- Pharo-dev - lists.pharo.org

Pharo News of the Week 52/2024

by Marcus Denker

# Pharo News of the Week 52/2024 This is the changekog for the last week of 2024: # The week on the Pharo Issue Tracker # Fixes - Resolution for issue 17548 - Removed Network setting BlabEmail #17564 https://github.com/pharo-project/pharo/pull/17564 - Duplicate class refactoring #17558 https://github.com/pharo-project/pharo/pull/17558 - 17493-Dropping-a-fileout-raises-an-error #17533 https://github.com/pharo-project/pharo/pull/17533 - fix search of element in SpCollectionListModel. #1681 https://github.com/pharo-spec/Spec/pull/1681 # Enhancements - enhance(morphic drop-handler): Better management of drop handler #17562 https://github.com/pharo-project/pharo/pull/17562 - Update FFI generation code to not generate multiple time the same methods #17559 https://github.com/pharo-project/pharo/pull/17559 # VM - Fix linking of UnixOSProcessPlugin - Remove dead code #888 https://github.com/pharo-project/pharo-vm/pull/888 - Fix failing tests #887 https://github.com/pharo-project/pharo-vm/pull/887 - fixing-classTag-tests #886 https://github.com/pharo-project/pharo-vm/pull/886 - Cleaning #881 https://github.com/pharo-project/pharo-vm/pull/881 - Druid fix vm #880 https://github.com/pharo-project/pharo-vm/pull/880 # Iceberg - Branch: PrefilledCommit1852, Fixes # 1852 #1857 https://github.com/pharo-vcs/iceberg/pull/1857 # Cleanups - Cleanup scale factor methods #17555 https://github.com/pharo-project/pharo/pull/17555 - Remove users of asFileName #17561 https://github.com/pharo-project/pharo/pull/17561 - Remove unused code, user of asFileName #925 https://github.com/pharo-spec/NewTools/pull/925 - Fix SpDemoPresenter stupid uneecessary dependencies #1689 https://github.com/pharo-spec/Spec/pull/1689 - Better comment and removed unused instance variable #17560 https://github.com/pharo-project/pharo/pull/17560 # Compiler - Rename AST -> OC #17553 https://github.com/pharo-project/pharo/pull/17553 - P13: post AST to OC renaming #17566 https://github.com/pharo-project/pharo/pull/17566

Jan. 17, 2025

New VM Release v10.3.3

by Guillermo Polito

Hi all, Weâve published a new VM release (v10.3.3) to be used with Pharo versions 10 through 13. 10.3.3 includes all changes in 10.3.2 (that was rolled back) plus several improvements. Highlights: - improves the naming schema of built artifacts to differentiate releases from intermediate/nightly builds - is built on the old file server (that we recovered!) to support compatibility with older GLibC versions - builds and run properly on newer linux systems (we fixed a couple of linking and compilation issues with newer versions of gcc) - many improvements in the perm space Please find in the wiki information about the build and versions https://github.com/pharo-project/pharo-vm/wiki Full release changes log https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.3 Finally, a big thanks to MaxLeske and Norbert for testing, and to everybody who contributed even in the previous conversations. Cheers, G

Jan. 16, 2025

New Smalltalk Blog

by Benoit St-Jean

Enjoy "The Transcript Show" ! https://transcriptshow.blogspot.com/

Jan. 13, 2025

Re: Pharo Launcher & Monticello & Code Repositories

by stephane ducasse

Hi benoit happy new year and sorry not seeing your email before > On 12 Nov 2024, at 18:31, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > 1) I've been using Pharo Launcher 3.2 on Windows 10 for a while and it seems like there's a problem with launching images starting with version 11. It just doesn't work. Any hint? Can you provide more information so that we can see what we can do. > 2) On a totally different subject, is there a package to be able load the Monticello Browser tool back into the image starting with Pharo 11? It's really annoying to deprive users from easily loading code from all the repos still using the Monticello format! I do not know. We do not support mcz loading. We sincerely understand that it can be painful but we cannot rewrite all the old tools. Embrace Git and Iceberg is a super nice tool for that. We are working on removing morphic and this is a large effort. If you want I can pair program with you to port one of your projects to github. > 3) Finally, is there a preferred ***central*** repository to store Pharo code? Something like Squeaksource was, or RubyGems (for Ruby) or Cincom Public Repository (VisualWorks Smalltalk) ? We always wanted to do that but we got stuck launching a market place. The idea is that you publish your code anywhere you want on github, gitlabâ¦. and you publish a description of such project in the marketplace. We did not have the manpower to launch this project. If you want to help we can tell you what we designed: the simplest thing that could work - a git repo. Now christophe should have the information somewhere. S

Jan. 7, 2025

Re: [Pharo-users] "Evaluation of SUnit" â New blog post on all: objects all: theTime

by stephane ducasse

Thanks for sharing it with us. It is great! > On 22 Nov 2024, at 23:10, Yanni Chiu <yannix7db(a)gmail.com> wrote: > > The blog post has "Nobody thought about automating that process. Until > Kent Beck did." That is not accurate, AFAIK. I believe it was in Kent > Beck's original EXtreme Programming book where he says the practices > were gathered from various Smalltalk shops he consulted at during the > Smalltalk heyday in the early 90's. > > For what it's worth, here's the history I know. Around 1993, in > Toronto, I was working at Footprint Software on VisualBanker (a suite > of code to support banking that 4 of the 5 major Canadian banks > bought). With my programming buddy (no "pair programming" at the time) > our task was to build a persistence framework (supporting Relational, > ObjectFiler, and in-memory). > > My task in a previous job was to convert (the AT&T Unix) C compiler to > support the "new" ANSI C standard. Thankfully, I was provided with a > test suite of C code, so that if it compiled without errors, then the > compiler was standard compliant. So, looking for something similar to > the ANSI C test suite I'd encountered, I set up test cases where all > methods starting with "test" would be run, and ran the tests against > all the backend data stores. The next day, my programming buddy > (George), who started at 6am (to have a faster commute) tells me this > test thing is great, and shows me the UI he built so we could just > push a button. We can check the same behaviour for all backends, and > we can coordinate our code changes through the tests (to mitigate our > different schedule). > > A year later, the company's product was deemed slow, so they > contracted Kent Beck to review our code base. He eventually comes > around to us. We showed him what we did with tests, and then he just > paused for about a minute staring out the window. We thought we were > doing something really bad. A few months later, George said to me "did > you see the SUnit thing posted on comp.lang.smalltalk". The basic > "test"-prefixed test cases were there, but with the addition of the > setUp and tearDown concept. > > Every once in a while I think to write this up. The "Nobody thought > about automating..." words pushed me over this time. Maybe 15 years > ago, I was able to find the original comp.lang.smalltalk SUnit > posting, but could not locate it this time when I wanted to verify the > dates. > > Yanni Chiu, > Smalltalk oldtimer, Toronto > > On Fri, Nov 22, 2024 at 8:58â¯AM Koen De Hondt > <koen(a)all-objects-all-the-time.st> wrote: >> >> Dear Pharo users and developers, >> >> I wrote a blog post in which I evaluate SUnit. >> >> Enjoy reading it! >> >> Ciao, >> Koen >> 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

Jan. 7, 2025

Re: Cannot commit to github in Pharo12

by Aik-Siong Koh

Jan. 6, 2025

Re: Cannot commit to github in Pharo12

by Cyril FERLICOT-DELBECQUE

This is weird because this error happens if a class is exported with the Tonel format in a package (aka a Folder) but has a different package in the metadata of the class. But here I'm checking the repo and things seems good [image.png] The folder is StCad-Geo and the category is StCad-Geo-GEO (which is the tag also). >From the debugger you got I was expecting this class to have StMath-GEO as category... -- Cyril Ferlicot-Delbecquehttps://ferlicot.fr On Friday, January 3rd, 2025 at 10:58 PM, Aik-Siong Koh <askoh(a)askoh.com> wrote: > In Pharo12, I click/Sources/Git Repository Browser/ > In the Git Repository Browser, I see > *SuperApp Uncommitted changes, 1 incoming, 1 main > I Select/SuperApp. > RightClick/Commit/ > I get the following error. Please advise. > Thanks. > Aik-Siong Koh

Jan. 6, 2025

Re: Cannot commit to github in Pharo12

by Aik-Siong Koh

Guillermo: Thank you very much for helping. https://github.com/aiksiongkoh/SuperApp Aik-Siong Koh Guillermo Polito wrote: > Hi Aik-Siong Koh, > > would you please share with us: > > - the repository if open source > - some instructions to reproduce > > G > >> Le 3 janv. 2025 Ã 10:58â¯PM, Aik-Siong Koh <askoh(a)askoh.com> a Ã©crit : >> >> In Pharo12, I click/Sources/Git Repository Browser/ >> In the Git Repository Browser, I see >> *SuperApp Uncommitted changes, 1 incoming, 1 main >> I Select/SuperApp. >> RightClick/Commit/ >> I get the following error. Please advise. >> Thanks. >> Aik-Siong Koh >> <mnhmbfjhogmnehhc.png>

Jan. 6, 2025

Re: Cannot commit to github in Pharo12

by Guillermo Polito

Hi Aik-Siong Koh, would you please share with us: - the repository if open source - some instructions to reproduce G > Le 3 janv. 2025 Ã 10:58â¯PM, Aik-Siong Koh <askoh(a)askoh.com> a Ã©crit : > > In Pharo12, I click/Sources/Git Repository Browser/ > In the Git Repository Browser, I see > *SuperApp Uncommitted changes, 1 incoming, 1 main > I Select/SuperApp. > RightClick/Commit/ > I get the following error. Please advise. > Thanks. > Aik-Siong Koh > <mnhmbfjhogmnehhc.png>

Jan. 6, 2025

Cannot commit to github in Pharo12

by Aik-Siong Koh

In Pharo12, I click/Sources/Git Repository Browser/ In the Git Repository Browser, I see *SuperApp Uncommitted changes, 1 incoming, 1 main I Select/SuperApp. RightClick/Commit/ I get the following error. Please advise. Thanks. Aik-Siong Koh

Jan. 3, 2025