February 2024 - Pharo-dev - lists.pharo.org

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

by Marcus Denker

# Fixes / Improvements - Implement Process>>state as the single source of truth for #isX methods (implements #14904) #16072 https://github.com/pharo-project/pharo/pull/16072 - Fix SDL2 class>>primCreateRGBSurfaceForCairoWidth:height: #16223 https://github.com/pharo-project/pharo/pull/16223 - add a way to allow some obsoletes through an environment variable #16222 https://github.com/pharo-project/pharo/pull/16222 - 16132-Caret-return-char-broken-in-Pharo-11-macOS-Keyboard-as-US-International---PC #16206 https://github.com/pharo-project/pharo/pull/16206 - Fix tests in metacello, Spec font chooser and date comments #16195 https://github.com/pharo-project/pharo/pull/ # Tools - Improving Message list morph UI #16096 https://github.com/pharo-project/pharo/pull/16096 - Do not show preview presenter when not needed #696 https://github.com/pharo-spec/NewTools/pull/696 - Align suffixes of FileBrowser #706 https://github.com/pharo-spec/NewTools/pull/706 - move edit path button close to the path #705 https://github.com/pharo-spec/NewTools/pull/705 - Add new folder button to file browser #704 https://github.com/pharo-spec/NewTools/pull/704 - Prevent errors in file operations. #703 https://github.com/pharo-spec/NewTools/pull/703 - Allow to sort some file browser columns #701 https://github.com/pharo-spec/NewTools/pull/701 - Catch preview errors in FileBrowser #700 https://github.com/pharo-spec/NewTools/pull/700 # Refactoring Engine - Fix: extract method failing tests #16198 https://github.com/pharo-project/pharo/pull/16198 - Refactor: push down method driver #16197 https://github.com/pharo-project/pharo/pull/16197 # Cleanup - Enhancement check keyword casing via lint rule #16220 https://github.com/pharo-project/pharo/pull/16220 - Fix: failing CI tests #16199 https://github.com/pharo-project/pharo/pull/16199 - Cleanup: Move more deprecated method to Deprecated12 #16194 https://github.com/pharo-project/pharo/pull/16194 - Cleanup: Small glitch in AsciiCharset class>>#toLowercase: #16192 https://github.com/pharo-project/pharo/pull/16192 - Cleanup: Cleanup Character protocols #16190 https://github.com/pharo-project/pharo/pull/16190 - Cleanup: Move deprecated #allCharacters to Deprecated12 package #16188 https://github.com/pharo-project/pharo/pull/16188 - Cleanup: deprecate nominallyUnsent: #16183 https://github.com/pharo-project/pharo/pull/16183 - DateAndTime asXXX methods should not be in accessing protocol #16181 https://github.com/pharo-project/pharo/pull/16181

Feb. 24, 2024

Re: IMPORTANT: Pharo 12 will enter feature freeze on March 1st

by Christophe Demarey

Hi Koen, Youâre right. It is on the radar for the release. I just added the tag. There is no formal process to identify them but if one feel a bug is really annoying and should be fixed before the release, he/she can inform us on the list. Cheers, Christophe > Le 22 fÃ©vr. 2024 Ã 15:46, Koen De Hondt <koen(a)all-objects-all-the-time.st> a Ã©crit : > > Esteban, > > I see that some issues are tagged with To fix before release <https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%…> > > What is the process to decide what to fix before the release? > > Can we add issues? In particular, this issue is very annoying: > > > https://github.com/pharo-project/pharo/issues/15564 > > > I do not see the same tags in https://github.com/pharo-spec/Spec. Does that mean that no Spec issues are selected to be fixed before the release? > > Ciao, > Koen > > >> On 13 Feb 2024, at 11:25, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >> Hi, >> >> The development of Pharo 12 will enter in feature freeze on March 1st and we plan to have at least one month of stabilization (but we will release when we are ready, in April). >> >> cheers, >> >> Esteban >> >> >

Feb. 22, 2024

Re: IMPORTANT: Pharo 12 will enter feature freeze on March 1st

by Koen De Hondt

Esteban, I see that some issues are tagged with To fix before release <https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%…> What is the process to decide what to fix before the release? Can we add issues? In particular, this issue is very annoying: https://github.com/pharo-project/pharo/issues/15564ï¿¼ No menubar in Mac OS Sonoma Â· Issue #15564 Â· pharo-project/pharo github.com I do not see the same tags in https://github.com/pharo-spec/Spec. Does that mean that no Spec issues are selected to be fixed before the release? Ciao, Koen > On 13 Feb 2024, at 11:25, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hi, > > The development of Pharo 12 will enter in feature freeze on March 1st and we plan to have at least one month of stabilization (but we will release when we are ready, in April). > > cheers, > > Esteban > >

Feb. 22, 2024

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

by Marcus Denker

# This week (07/2024) on the Pharo Issue Tracker # Fixes - Replace $r key combination in method editor pane #16168 https://github.com/pharo-project/pharo/pull/16168 - Fix SDL2 binding #16165 https://github.com/pharo-project/pharo/pull/16165 - 16161-Clean-up-undeclared-assumes-all-undeclared-are-globals #16162 https://github.com/pharo-project/pharo/pull/16162 - 15733-OldClassDefinitionBuilder-needs-to-support-usesinstanceVariableNames #16151 https://github.com/pharo-project/pharo/pull/16151 - Fix hierarchical implementors bug #16150 https://github.com/pharo-project/pharo/pull/16150 - restore SystemProgressMorph dectivation #16143 https://github.com/pharo-project/pharo/pull/16143 # Refactoring Engine - Fix: extract method command #16179 https://github.com/pharo-project/pharo/pull/16179 - Refactor: extract method transformation improvements #16178 https://github.com/pharo-project/pharo/pull/16178 - Make addReturn answer the receiver #16170 https://github.com/pharo-project/pharo/pull/16170 - Test for semantics of extract method transformation and additional code supporting it #16167 https://github.com/pharo-project/pharo/pull/16167 - 16153-AST-testIsClean-and-testHasNonLocalReturn-failing-and-more #16159 https://github.com/pharo-project/pharo/pull/16159 - Test: semantics of extract method transformation #16158 https://github.com/pharo-project/pharo/pull/16158 - 16133 transforming deprecation should not raise a debugger by default but rewrite the code #16157 https://github.com/pharo-project/pharo/pull/16157 - Add exact commit and tag information in recorded metacello directives #16155 https://github.com/pharo-project/pharo/pull/16155 - Feat: extract method source string api #16154 https://github.com/pharo-project/pharo/pull/16154 - Cleanup: isDirectlyUsed and isUsed #16146 https://github.com/pharo-project/pharo/pull/16146 # Cleanup - Rename RPackage-Tests #16120 https://github.com/pharo-project/pharo/pull/16120 - Integrate BeautifulComments directly into Pharo #16176 https://github.com/pharo-project/pharo/pull/16176 - #asUncommentedCode is deprecated, we can remove the test #16152 https://github.com/pharo-project/pharo/pull/16152 - 16055-Cleanup-uses-cascaded-nextPutAll-in-ObjectstoreOn #16142 https://github.com/pharo-project/pharo/pull/16142 - fix: #16137 remove grapoh viz support from Dependency analysis since â¦ #16138 https://github.com/pharo-project/pharo/pull/16138 - More GraViz cleanups #16139 https://github.com/pharo-project/pharo/pull/16139

Feb. 21, 2024

Re: IMPORTANT: Pharo 12 will enter feature freeze on March 1st

by Guillermo Polito

Thanks Esteban. Everybody, please join us in the bugfixing phase to have a robust release! G > El 13 feb 2024, a las 11:25, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> escribiÃ³: > > Hi, > > The development of Pharo 12 will enter in feature freeze on March 1st and we plan to have at least one month of stabilization (but we will release when we are ready, in April). > > cheers, > > Esteban > >

Feb. 13, 2024

IMPORTANT: Pharo 12 will enter feature freeze on March 1st

by Esteban Lorenzano

Hi, The development of Pharo 12 will enter in feature freeze onÂ March 1st and we plan to have at least one month of stabilization (but we will release when we are ready, in April). cheers, Esteban

Feb. 13, 2024

Call for presentation @ ESUG 2024

by stephane ducasse

Dear friends Please distribute the following call ESUG 2024 Call for Presentations from 8 to 11 July 2024 Lille France https://esug.github.io https://esug.github.io/2024-Conference/conf2024.html 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, software to the award competition, or a paper to IWST http://https://esug.github.io/2024-Conference/IWST2024.html - 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 in 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 We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. - Show your business in a 10-minute session (Get prepared!!) - Teaching pearls: we want some sessions 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-minute sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2024-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr] Title: [ESUG 2024] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: ## 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 Steven Costiou <steven.costiou at inria.fr> and Oleksandr Zaitsev <olk.zaytsev at gmail.com> with: title: [ESUG 2024 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 from 8 to 11 July 2024 (including nights from Sunday to Monday and from Wednesday to Thursday ). Students will be hosted in student rooms. ESUG additionally covers 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, that 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 a student volunteer, do not book yourself, we have arranged the booking already!

Feb. 13, 2024

Re: A little post Why class number is an idiotic quality metric?

by stephane ducasse

https://pharoweekly.wordpress.com/2024/02/10/why-class-number-is-an-idiotic… > On 10 Feb 2024, at 10:13, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > > https://wordpress.com/post/pharoweekly.wordpress.com/4226 > > > 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 > > > > > 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. 11, 2024

Re: A little post Why class number is an idiotic quality metric?

by James Foster

For those that didn't write the post, here is a linkâ¦ https://pharoweekly.wordpress.com/2024/02/10/why-class-number-is-an-idiotic… James > On Feb 10, 2024, at 1:13â¯AM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > > https://wordpress.com/post/pharoweekly.wordpress.com/4226 > > > 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. 11, 2024

A little post Why class number is an idiotic quality metric?

by stephane ducasse

https://wordpress.com/post/pharoweekly.wordpress.com/4226 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. 10, 2024