- Pharo-dev - lists.pharo.org

Pharo on Bluesky and Mastodon

by Marcus Denker

Hello, Bluesky: https://bsky.app/profile/pharoproject.bsky.social We are on Mastodon, too (since 2018!) https://mastodon.social/@pharoproject Marcus

Feb. 14, 2025

Pharo News of the Week 06/2025

by Marcus Denker

# Pharo News of the Week 06/2025 - [ANN] GSoC 2025 Mentors/Topics needed: https://www.pharo.org/news/2025-01-30-GSOC2025.html - [ANN] We are now on bluesky: https://bsky.app/profile/pharoproject.bsky.social - [ANN] and of course mastodon since a long time: https://mastodon.social/@pharoproject If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Update version in #documentBrowser for BaselineOfPharo for Pharo 11 to âv1.0.4â #17766 https://github.com/pharo-project/pharo/pull/17766 # Pharo 12 - Backport changes to not restore ffi methods if they are not installed #17780 https://github.com/pharo-project/pharo/pull/17780 # Fixes - Fix opening of the Dependency analyzer #17763 https://github.com/pharo-project/pharo/pull/17763 - Fix browsing of methods in Epicea #17764 https://github.com/pharo-project/pharo/pull/17764 - Do not resume running process #17777 https://github.com/pharo-project/pharo/pull/17777 - Fixing browse in KMDescriptionPresenter #17776 https://github.com/pharo-project/pharo/pull/17776 - Fix cursor navigation #17772 https://github.com/pharo-project/pharo/pull/17772 - Fix save image dialog default values #17767 https://github.com/pharo-project/pharo/pull/17767 - 17563-propertyAtput-looks-bogus, #17754 https://github.com/pharo-project/pharo/pull/17754 # Features - Addition of new setting for using SpClosedWindowListPresenter or not #17757 https://github.com/pharo-project/pharo/pull/17757 # Code Completion - Branch: addingSetterToCoHeuristic #17782 https://github.com/pharo-project/pharo/pull/17782 # VM - Remove debugging code #911 https://github.com/pharo-project/pharo-vm/pull/911 - Simplify signal handler space calculation: use SIGSTKSZ, posix defined #910 https://github.com/pharo-project/pharo-vm/pull/910 # Newtools - changed menu bug display and updated baseline #970 https://github.com/pharo-spec/NewTools/pull/970 - Update world menu entry for the finder #982 https://github.com/pharo-spec/NewTools/pull/982 - Fix selection in save file presenter #980 https://github.com/pharo-spec/NewTools/pull/980 - Unsubscribe if user dont want to use the presenter anymore #977 https://github.com/pharo-spec/NewTools/pull/977 - Started to pass the stApplication in the open method #976 https://github.com/pharo-spec/NewTools/pull/976 - Moved IRMethod extension to OCIRMethod #975 https://github.com/pharo-spec/NewTools/pull/975 - Memory leak fix #972 https://github.com/pharo-spec/NewTools/pull/972 - adds property to morph when closed and remove it when unhidden #971 https://github.com/pharo-spec/NewTools/pull/971 # Tests - Skipping two tests to get the green bar for now. #17743 https://github.com/pharo-project/pharo/pull/17743 - Fix and improve WindowAnnouncementTest #17773 https://github.com/pharo-project/pharo/pull/17773 - Fix testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses #17769 https://github.com/pharo-project/pharo/pull/17769 # Website - Update community.md: add bluesky link #84 https://github.com/pharo-project/pharo-website/pull/84 # Cleanups - Branch: 17675-Opal-Extension-symbolic-to-Debugging-Core #17735 https://github.com/pharo-project/pharo/pull/17735 - Branch: 17672-Rename-formatter-in-EFtests-to-avoid-spurious-sender-clash #17736 https://github.com/pharo-project/pharo/pull/17736 - Remove String>>isValidSelector #17741 https://github.com/pharo-project/pharo/pull/17741 - 17746-remove-ClassdeprecationRefactorings, Fixes #17746 #17747 https://github.com/pharo-project/pharo/pull/17747 - 17742-isSelectorSymbol-should-be-renamed-isUsedAsSelectorSymbol #17748 https://github.com/pharo-project/pharo/pull/17748 - 17667-remove-display-of-empty-sharedVariables-from-class-default-tempâ¦ #17749 https://github.com/pharo-project/pharo/pull/17749 - Branch: 17750-FormasText-from-MD-to-Form, #17751 https://github.com/pharo-project/pharo/pull/17751 - Branch: FixKMLeftInstanceVariable, #17758 https://github.com/pharo-project/pharo/pull/17758 - Removed Stuff linked to the presenter #17761 https://github.com/pharo-project/pharo/pull/17761 - Clean tool registry2 #17765 https://github.com/pharo-project/pharo/pull/17765

Feb. 7, 2025

Re: [Pharo-users] "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by stephane ducasse

Thanks. I have some other books under preparation :) S > On 1 Feb 2025, at 23:51, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > Congratulation Stephane on completing this book. > > I feel it is crucial. It removes a major hurdle for new, part time and/or returning programmers to get what they need with a UI for their Pharo programs. > > For me, it also helps me advocating for Pharo with my colleagues. > > Cheers > Mark > > On Sun, 2 Feb 2025, 12:07 am stephane ducasse, <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >> Thanks. >> Writing this book was a daunting huge difficult exhausting task that took me around 4 years or more. >> >> This publisher is managed using a not so great Php software and I can tell you that you can feel it when >> you have to manage the books. >> >> S >> >>> On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>> >>> hello!, >>> >>> Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. >>> >>> happy smalltalking >>> >>> >>> giorgio >>> >>> On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>> Hi Giorgio, >>>> >>>> Thank you for reporting the issue. >>>> >>>> Yes, it is an error. We saw it a few days ago, but it has not been fixed yet. >>>> >>>> Best regards, >>>> Koen >>>> >>>>> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>>>> >>>>> hello, >>>>> >>>>> The Amazon site says that the language is French. Is that an error? >>>>> >>>>> thanks >>>>> >>>>> ciao >>>>> >>>>> giorgio >>>>> >>>>> <Screenshot 2024-11-07 at 12.25.47.png> >>>>> >>>>> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>>>> Dear Pharo users and developers, >>>>>> >>>>>> It required an enormous effort to review, rewrite, and extend it, but I am happy to announce that it is finally here: the book on application building in Pharo with Spec 2.0. >>>>>> >>>>>> I wrote a blog post about it <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>>>>> >>>>>> Ciao, >>>>>> Koen >>>> >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Feb. 6, 2025

Pharo Association 2024 Review

by tesonep＠gmail.com

Dear Pharo Association members, Pharoers and Smalltalkers from all over the world We are writing you to thank you again for your support of the Pharo Association. With your help, we are able to perform a lot of activities to increase the impact of Pharo, enlarge its community and have a better programming life for everyone. For the people who are not members of the association, we take the opportunity to tell you all the accomplishments of the association last year and invite you to participate in any of the forms our association provides. We want to profit this time of the year to tell you the most important actions that the association has supported the last years. - *Infrastructure for Pharo: *as an association, we support the maintenance of the infrastructure used by Pharo. We provided the funds for the hosting of Pharo services (website, file server, mailing lists) and domains. Most of the services that we daily use are supported by your help. Thanks for allowing the community to use the Pharo Launcher or getting an image from ZeroConf. - *Conference Sponsoring:* we all love to go to nice conferences and much more if there is Pharo-related content on it. This year as it is tradition we supported the *ESUG 2024 *conference. Having a place to interchange and to publish all the advances in Pharo is key to its development. - *Summer School: *With the objective of extending the Pharo community, in 2024, we sponsored a summer school at Split, Croatia about advanced object-oriented design with Pharo. Due to the nice reception and results, this year we are again sponsoring a summer school in February at Montpellier. - *Pharo Music: *Smalltalk has been always a language close to the arts, and Pharo is not an exception. This year, we heavily sponsored the development of Phausto, Coypu and CoypuIDE. *Phausto <https://github.com/lucretiomsp/phausto>* is a library and API that allows to use the FAUST compiler and its libraries (Functional Audio Stream) inside Pharo. *Coypu <https://github.com/lucretiomsp/Coypu>* is a package with methods and classes for Pharo designed for programming music on-the-fly, and it has its *IDE <https://github.com/pharo-graphics/CoypuIDE>* developed in Bloc. This tools has been presented in numerous technical and musical conferences, and in all of them they have generated a lot of attention and interest. We are much than happy with the results we are obtaining. - *Student Sponsoring:* we sponsored the access of students using Pharo to Summer Schools and visits to labs. We sponsored also the food and drinks of small meetings where students can learn and play with Pharo. This sponsoring is particularly important because often the labs are not allowed to pay trips of students, limiting the access to international students. Because of that, we sponsored students from Argentina (2), Serbia, Madagascar (3), Chile, and Bolivia. Without your support we would not be able to plant Pharo seeds all over the world. Your help is base to increase the community and to help all the people interested in Pharo. - *Book Sponsoring: *During last year, we have sponsored the write of 4 new books about Pharo. These books covers subjects for newcomers and experts, going from the style of code, testing and UI creation. All the books are available to the community (*https://books.pharo.org/ <https://books.pharo.org/>*) and even you can get a physical copy. We consider that we need to provide the material to let all the people interested to grow in their Pharo experience. We want to thank you again for your support as all the support we are getting are from our members. We remember you that you can renew or increase your subscription at *https://association.pharo.org <https://association.pharo.org/>*. Your support is really important for us because it enables us to do actions that would be almost impossible to do. Finally we remember you that we are always open to listen your opinions and suggestions, and to receive requests for sponsoring or support at *association(a)pharo.org <association(a)pharo.org>*. Sorry if you have got this mails from different channels. Thank you so much again, and we desired you and excellent new year! *Pharo Association*

Feb. 5, 2025

Re: About String and Symbol equality

by Aik-Siong Koh

How did Pharo diverge from the other Smalltalks? Was it a good decision? stephane ducasse wrote: > Hello people > > In Pharo (following Squeak tradition) a string is equals to its symbol > representation. > e.g. > âtintinâ = #tintin > > true > > In other Smalltalk dialects this is not the case. > > We have been working (sponsored by Lifeware) to support both semantics > (yes this is a kind of > daunting task and it can raise bugs). > > Our objective is to help people make business with Pharo. So âsimpleâ > cross compatibility is something that we consider e.g. to deploy > applications in Gemstone for example. > (We would love to have a Pharo compiler working on Gemstone generating > Gemstone VM bytecodes this is why we love the work of James Foster but > this is another story). > > So since we are pragmatic people we could be convinced that the > semantics of Pharo is not good :) > and that by default we should use the semantics of GS or VW. > > The first step is to be able to choose which one to use within Pharo > and be able to switch. > We are nearly there for Pharo 13. > > The second step is to get a nice default. > And we need the help of the community for this. > > Do you have any advice, arguments for and against any of the two > choices that could be put on the table to influence our decisions for > Pharo 14. > > So let us know :) > > Stef on the behalf of the Pharo consortium. > > > 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 > > > > >

Feb. 3, 2025

About String and Symbol equality

by stephane ducasse

Hello people In Pharo (following Squeak tradition) a string is equals to its symbol representation. e.g. âtintinâ = #tintin > true In other Smalltalk dialects this is not the case. We have been working (sponsored by Lifeware) to support both semantics (yes this is a kind of daunting task and it can raise bugs). Our objective is to help people make business with Pharo. So âsimpleâ cross compatibility is something that we consider e.g. to deploy applications in Gemstone for example. (We would love to have a Pharo compiler working on Gemstone generating Gemstone VM bytecodes this is why we love the work of James Foster but this is another story). So since we are pragmatic people we could be convinced that the semantics of Pharo is not good :) and that by default we should use the semantics of GS or VW. The first step is to be able to choose which one to use within Pharo and be able to switch. We are nearly there for Pharo 13. The second step is to get a nice default. And we need the help of the community for this. Do you have any advice, arguments for and against any of the two choices that could be put on the table to influence our decisions for Pharo 14. So let us know :) Stef on the behalf of the Pharo consortium. 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

Feb. 2, 2025

Re: [Pharo-users] "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by stephane ducasse

Thanks. Writing this book was a daunting huge difficult exhausting task that took me around 4 years or more. This publisher is managed using a not so great Php software and I can tell you that you can feel it when you have to manage the books. S > On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: > > hello!, > > Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. > > happy smalltalking > > > giorgio > > On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >> Hi Giorgio, >> >> Thank you for reporting the issue. >> >> Yes, it is an error. We saw it a few days ago, but it has not been fixed yet. >> >> Best regards, >> Koen >> >>> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>> >>> hello, >>> >>> The Amazon site says that the language is French. Is that an error? >>> >>> thanks >>> >>> ciao >>> >>> giorgio >>> >>> <Screenshot 2024-11-07 at 12.25.47.png> >>> >>> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>> Dear Pharo users and developers, >>>> >>>> It required an enormous effort to review, rewrite, and extend it, but I am happy to announce that it is finally here: the book on application building in Pharo with Spec 2.0. >>>> >>>> I wrote a blog post about it <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>>> >>>> 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

Feb. 1, 2025

Pharo News of the Week 05/2025

by Marcus Denker

# Pharo News of the Week 05/2025 - [Video] Tp33 first pattern programming: https://www.youtube.com/watch?v=EwPuypfRQTg - [ANN] Google Summer of Code 2025: Call for Students https://gsoc.pharo.org If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Backport fix-SDL-default-renderer-by-platform to Pharo 11 #17696 https://github.com/pharo-project/pharo/pull/17696 # Pharo 12 - Backport correction evaluation of dynamic variables from the debugger #956 - Backport correction evaluation of dynamic variables from the debugger #956 https://github.com/pharo-spec/NewTools/pull/956 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.2â #17691 https://github.com/pharo-project/pharo/pull/17691 # Fixes - Do not restore ffi methods if they are not installed #17686 https://github.com/pharo-project/pharo/pull/17686 - Fix broken Pharo image #17712 https://github.com/pharo-project/pharo/pull/17712 - Bring back 'Fit all' menu item #17709 https://github.com/pharo-project/pharo/pull/17709 - Fixes: 17680 RB-Rename-class-from-in-text-editor-select-the-class-of-â¦ #17681 https://github.com/pharo-project/pharo/pull/17681 - 17677 pharo syntax tutorial testtest divide two by zero signals zero divide #17679 https://github.com/pharo-project/pharo/pull/17679 # Rules - Edited two rules to implement that #initializeWindow: has to call super and can't override preferredExtent #17695 https://github.com/pharo-project/pharo/pull/17695 - Refactoring Engine https://github.com/pharo-project/pharo/pull/17654 # Window Handling - Migrate about window to Spec #17708 https://github.com/pharo-project/pharo/pull/17708 - Cleaning window title #17711 https://github.com/pharo-project/pharo/pull/17711 # VM - Forward port 10.3.3 to pharo-12 branch #903 https://github.com/pharo-project/pharo-vm/pull/903 - Improve project structure #904 https://github.com/pharo-project/pharo-vm/pull/904 # Iceberg / Git - Cleaning Spec #1885 https://github.com/pharo-vcs/iceberg/pull/1885 - Removing dead code #1890 https://github.com/pharo-vcs/iceberg/pull/1890 - Fix IceTipCommitBrowser to have a cleaner initialization of the model #1888 https://github.com/pharo-vcs/iceberg/pull/1888 - Clean protocols #1886 https://github.com/pharo-vcs/iceberg/pull/1886 - Improve protocols #89 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/89 # Newtools - SpClosedWindowPresenter don't add itself in last closed window now #969 https://github.com/pharo-spec/NewTools/pull/969 - No glamorous icon names #968 https://github.com/pharo-spec/NewTools/pull/968 - No glamorous icon names #967 https://github.com/pharo-spec/NewTools/pull/967 - Cleaning title definition #966 https://github.com/pharo-spec/NewTools/pull/966 - Introduce a new About Pharo based on Spec instead of Morphic #965 https://github.com/pharo-spec/NewTools/pull/965 - Categorize an uncategorized method #964 https://github.com/pharo-spec/NewTools/pull/964 - Closed window is now independent and works with Announcements #963 https://github.com/pharo-spec/NewTools/pull/963 - Post cleaning fix2 #962 https://github.com/pharo-spec/NewTools/pull/962 - Post cleaning fixes #961 https://github.com/pharo-spec/NewTools/pull/961 - On the class side of course #960 https://github.com/pharo-spec/NewTools/pull/960 - Fixing the build I hope #959 https://github.com/pharo-spec/NewTools/pull/959 - Cleaning spec #957 https://github.com/pharo-spec/NewTools/pull/957 # Cleanup - Cleaning spec #1709 https://github.com/pharo-spec/Spec/pull/1709 - Cleaning title definition #1711 https://github.com/pharo-spec/Spec/pull/1711 - Cleaning SpMorphic: less duplication around centered #1712 https://github.com/pharo-spec/Spec/pull/1712 - Branch: automatebenchresult, Adding the timing to the benchmarks , aâ¦ #17622 https://github.com/pharo-project/pharo/pull/17622 - Cleanup compiler extensions. #17662 https://github.com/pharo-project/pharo/pull/17662 - AST-Core-Tests should not depend on Monticello #17665 https://github.com/pharo-project/pharo/pull/17665 - Branch: RedoingClosePresenter, Deleted everything so SpClosedWindowListPresenter can be independant #17676 https://github.com/pharo-project/pharo/pull/17676 - Move (OC)DoItVariable to the compiler #17678 https://github.com/pharo-project/pharo/pull/17678 - Cleaning Presenter #17683 https://github.com/pharo-project/pharo/pull/17683 - Post clean fix2 #17693 https://github.com/pharo-project/pharo/pull/17693 - Reintroducing test methods in a way that they are not counted as simiâ¦ #17694 https://github.com/pharo-project/pharo/pull/17694 - Reduce usage of protocol initialize-release #17701 https://github.com/pharo-project/pharo/pull/17701 - Cleanup refactorings #17700 https://github.com/pharo-project/pharo/pull/17700 - Depends on Roassal branch Pharo13 #17705 https://github.com/pharo-project/pharo/pull/17705 - Removed the undeclared for now. #17706 https://github.com/pharo-project/pharo/pull/17706 - Cleanup Tests #17710 https://github.com/pharo-project/pharo/pull/17710

Jan. 31, 2025

Re: Pharo News of the Week 04/2025

by Noury Bouraqadi

Thank you Marcus and all the contributors for the update and continuously improving Pharo. FYI I copy pasted the email into 2 AIs (ChatGPT and Claude) the email, and prompted them to make a summary. ChatGPT output was useless. Claude's one is more interesting. So, I'm sharing it with you below. I also asked them to make a mind map of the news list. Here, ChatGPT, made the more intersting result, though the texts are poor. Attached. Best, Noury --- Here's a summary of the key updates from Pharo's weekly news and issue tracker: Major Updates: - New VM release v10.3.3 - Updates to Pharo 11 and 12 baselines (Iceberg v2.2.3, NewTools v0.9.1, Spec v1.3.5) - Fuel update for Pharo 13 Notable Improvements: - Fixed tenured primitives and timestamp parsing - Enhanced word navigation and protocol removal in Calypso - Added password support in SpRequestDialog - Integrated Welcome Browser into NewTools - Added drag & drop support to inspectors Cleanup & Infrastructure: - Reorganized compiler tests - Improved build process (Roassal/NewTools loading sequence) - Removed deprecated code and redundant features - Enhanced ColorPicker integration - Multiple fixes to Spec framework Development Tools: - New snapshot browser in Iceberg - Improved error messages in Tonel - Multiple NewTools enhancements including playground size memorization - Better metadata support in Spec presenters A spotter survey is currently open for community feedback. On Jan 27 2025, at 5:01 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > # Pharo News of the Week 04/2025 > > - [ANN] New VM Release v10.3.3 https://www.pharo.org/news/2025-01-21-VM10-3-3.html > - [Blog Post]: Subject in SUnit Tests https://all-objects-all-the-time.st/#/blog/posts/ > - [Survey] please take a second to take the spotter survey: https://sondages.inria.fr/index.php/319877?lang=en > > If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 > # The week on the Pharo Issue Tracker > > # Pharo 11 > - Update version in #iceberg for BaselineOfPharo for Pharo 11 to âv2.2.3â #17644 > https://github.com/pharo-project/pharo/pull/17644 > > # Pharo 12 > - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.1â #17666 > https://github.com/pharo-project/pharo/pull/17666 > > - Update version in #spec for BaselineOfPharo for Pharo 12 to âv1.3.5â #17643 > https://github.com/pharo-project/pharo/pull/17643 > > > # Features > - Update Fuel for Pharo 13 #17635 > https://github.com/pharo-project/pharo/pull/17635 > > # Fixes > - Fixed fall back code on new tenured primitives by jordanmontt Â· Pull Request #17617 Â· pharo-project/pharo > https://github.com/pharo-project/pharo/pull/17617 > > - Calypso: Fix remove protocol when there is no method in the protocol #17628 > https://github.com/pharo-project/pharo/pull/17628 > > - Branch: realunclosewindow, added all behaviors needed to use SpClosedWindowListPresebter #17629 > https://github.com/pharo-project/pharo/pull/17629 > > - Update word navigation to handle different character groups #17630 > https://github.com/pharo-project/pharo/pull/17630 > > - Fix timestamp parsing in SourceFileArray #17633 > https://github.com/pharo-project/pharo/pull/17633 > > # VM > - Remove old versions of libgit in new builds #902 > https://github.com/pharo-project/pharo-vm/pull/902 > > > # Compiler > - Move OpalCompiler-UI tests to OpalCompiler-UI-Tests #17664 > https://github.com/pharo-project/pharo/pull/17664 > > - Move OCBytecodeDecompilerExamplesTest to Flashback #17663 > https://github.com/pharo-project/pharo/pull/17663 > > # Iceberg /Tonel /git > - Port Hernan's snapshot browser to Iceberg #1875 > https://github.com/pharo-vcs/iceberg/pull/1875 > > - Improve error messages #123 > https://github.com/pharo-vcs/tonel/pull/123 > > # CI/Bootrap/Image load > - Load roassal before NewTool > https://github.com/pharo-project/pharo/pull/17650 > > - Remove double loading of welcome browser #17655 > https://github.com/pharo-project/pharo/pull/17655 > > - Load Microdown before NewTools (Anyway NewTools will load it) #17652 > https://github.com/pharo-project/pharo/pull/17652 > > # Newtools > - Branch: Pharo13, renamed it to presenter and cleaned the class #941 > https://github.com/pharo-spec/NewTools/pull/941 > > - Merge ColorPicker in NewTools #954 > https://github.com/pharo-spec/NewTools/pull/954 > > - Fix Code Rewriter to take care of the context's application #953 > https://github.com/pharo-spec/NewTools/pull/953 > > - Remove method with equivalent in traits #952 > https://github.com/pharo-spec/NewTools/pull/952 > > - Integrate Welcome Browser into NewTools by jecisc Â· Pull Request #951 Â· pharo-spec/NewTools > https://github.com/pharo-spec/NewTools/pull/951 > > - Branch: Making Playground Memorizing its Size #949 > https://github.com/pharo-spec/NewTools/pull/949 > > - Branch: FixingLastInitialExtentForWindow #948 > https://github.com/pharo-spec/NewTools/pull/948 > > - Branch: 946-StFinder-produces-DNU-on-browse, Fixes: #964 #947 > https://github.com/pharo-spec/NewTools/pull/947 > > - Add drag&drop support to inspectors #945 > https://github.com/pharo-spec/NewTools/pull/945 > > # Spec > - Allow passwords in SpRequestDialog, Fixes #1705 #1706 > https://github.com/pharo-spec/Spec/pull/1706 > > - fix: make Fuel serialization work with native collections #1704 > https://github.com/pharo-spec/Spec/pull/1704 > > - P13: Introduce metadata and properties support in SpAbstractPresenterâ¦ #1701 > https://github.com/pharo-spec/Spec/pull/1701 > > # Cleanup > - Remove dead code #17632 > https://github.com/pharo-project/pharo/pull/17632 > > - Moving ColorPicker extension to the extended class. #17637 > https://github.com/pharo-project/pharo/pull/17637 > > - Remove the refresh because we should not have a dependency from Morphâ¦ #17638 > https://github.com/pharo-project/pharo/pull/17638 > > - Branch: MakingDrTestMemorizingSize. #17649 > https://github.com/pharo-project/pharo/pull/17649 > > - Remove Morphic MCSnapshotBrowser #17659 > https://github.com/pharo-project/pharo/pull/17659 > > - Remove dead code #17658 > https://github.com/pharo-project/pharo/pull/17658 > > - Doing a pass on ProfStef. #17653 > https://github.com/pharo-project/pharo/pull/17653 > > # Website > - Update Companies.md: new form links #82 > https://github.com/pharo-project/pharo-website/pull/82 >

Jan. 28, 2025

Pharo News of the Week 04/2025

by Marcus Denker

# Pharo News of the Week 04/2025 - [ANN] New VM Release v10.3.3 https://www.pharo.org/news/2025-01-21-VM10-3-3.html - [Blog Post]: Subject in SUnit Tests https://all-objects-all-the-time.st/#/blog/posts/ - [Survey] please take a second to take the spotter survey: https://sondages.inria.fr/index.php/319877?lang=en If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Update version in #iceberg for BaselineOfPharo for Pharo 11 to âv2.2.3â #17644 https://github.com/pharo-project/pharo/pull/17644 # Pharo 12 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.1â #17666 https://github.com/pharo-project/pharo/pull/17666 - Update version in #spec for BaselineOfPharo for Pharo 12 to âv1.3.5â #17643 https://github.com/pharo-project/pharo/pull/17643 # Features - Update Fuel for Pharo 13 #17635 https://github.com/pharo-project/pharo/pull/17635 # Fixes - Fixed fall back code on new tenured primitives by jordanmontt Â· Pull Request #17617 Â· pharo-project/pharo https://github.com/pharo-project/pharo/pull/17617 - Calypso: Fix remove protocol when there is no method in the protocol #17628 https://github.com/pharo-project/pharo/pull/17628 - Branch: realunclosewindow, added all behaviors needed to use SpClosedWindowListPresebter #17629 https://github.com/pharo-project/pharo/pull/17629 - Update word navigation to handle different character groups #17630 https://github.com/pharo-project/pharo/pull/17630 - Fix timestamp parsing in SourceFileArray #17633 https://github.com/pharo-project/pharo/pull/17633 # VM - Remove old versions of libgit in new builds #902 https://github.com/pharo-project/pharo-vm/pull/902 # Compiler - Move OpalCompiler-UI tests to OpalCompiler-UI-Tests #17664 https://github.com/pharo-project/pharo/pull/17664 - Move OCBytecodeDecompilerExamplesTest to Flashback #17663 https://github.com/pharo-project/pharo/pull/17663 # Iceberg /Tonel /git - Port Hernan's snapshot browser to Iceberg #1875 https://github.com/pharo-vcs/iceberg/pull/1875 - Improve error messages #123 https://github.com/pharo-vcs/tonel/pull/123 # CI/Bootrap/Image load - Load roassal before NewTool https://github.com/pharo-project/pharo/pull/17650 - Remove double loading of welcome browser #17655 https://github.com/pharo-project/pharo/pull/17655 - Load Microdown before NewTools (Anyway NewTools will load it) #17652 https://github.com/pharo-project/pharo/pull/17652 # Newtools - Branch: Pharo13, renamed it to presenter and cleaned the class #941 https://github.com/pharo-spec/NewTools/pull/941 - Merge ColorPicker in NewTools #954 https://github.com/pharo-spec/NewTools/pull/954 - Fix Code Rewriter to take care of the context's application #953 https://github.com/pharo-spec/NewTools/pull/953 - Remove method with equivalent in traits #952 https://github.com/pharo-spec/NewTools/pull/952 - Integrate Welcome Browser into NewTools by jecisc Â· Pull Request #951 Â· pharo-spec/NewTools https://github.com/pharo-spec/NewTools/pull/951 - Branch: Making Playground Memorizing its Size #949 https://github.com/pharo-spec/NewTools/pull/949 - Branch: FixingLastInitialExtentForWindow #948 https://github.com/pharo-spec/NewTools/pull/948 - Branch: 946-StFinder-produces-DNU-on-browse, Fixes: #964 #947 https://github.com/pharo-spec/NewTools/pull/947 - Add drag&drop support to inspectors #945 https://github.com/pharo-spec/NewTools/pull/945 # Spec - Allow passwords in SpRequestDialog, Fixes #1705 #1706 https://github.com/pharo-spec/Spec/pull/1706 - fix: make Fuel serialization work with native collections #1704 https://github.com/pharo-spec/Spec/pull/1704 - P13: Introduce metadata and properties support in SpAbstractPresenterâ¦ #1701 https://github.com/pharo-spec/Spec/pull/1701 # Cleanup - Remove dead code #17632 https://github.com/pharo-project/pharo/pull/17632 - Moving ColorPicker extension to the extended class. #17637 https://github.com/pharo-project/pharo/pull/17637 - Remove the refresh because we should not have a dependency from Morphâ¦ #17638 https://github.com/pharo-project/pharo/pull/17638 - Branch: MakingDrTestMemorizingSize. #17649 https://github.com/pharo-project/pharo/pull/17649 - Remove Morphic MCSnapshotBrowser #17659 https://github.com/pharo-project/pharo/pull/17659 - Remove dead code #17658 https://github.com/pharo-project/pharo/pull/17658 - Doing a pass on ProfStef. #17653 https://github.com/pharo-project/pharo/pull/17653 # Website - Update Companies.md: new form links #82 https://github.com/pharo-project/pharo-website/pull/82

Jan. 27, 2025