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

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Miloslav.Raus＠cuzk.cz

(Belated) âHi, Folksâ To stress the point: All of the 20-30 in-house apps I would have preferred to develop using Pharo(Squeak before that) were done in something that didnât lack one of the following enablers (if we skip diacritics/fonts/locales): Â· Drag & Drop (from the outside world) Â· taskbar/status icons Â· support for being launched as [Windows] Service Â· COM They might seem like small / moot points, but each and single one of them can be a show-stopper. Probably couldâve written the support myself in the meantime, but the total lack of interest was what kept me from trying, and even asking for it. I would have even tried to write something like Matrix myself (Fuel seemed promissing fot that use-case), but the rest of the ecosystem ... Cheers and good luck, M.R. From: RauÅ¡ Miloslav Sent: Thursday, February 29, 2024 5:56 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: RE: [Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes Funny how the story changes depending on the point where one stands. OooooHHHHH, WE HAVE _AN_ APP. vs: Oh, they have an app ... OS/Ecosystem Integration is what matters Â· native integration o Drag & Drop (from the outside world) o taskbar/status icons o support for being launched as [Windows] Service o COM on windows (and I mean propper support, not the Astares placebo) o .NET bridge everywhere o perhaps even @#%$ Java Semblance of multicore support (even faked, as is â was? â the oh-so-great Cincom âMatrixâ) wouldnât hurt (as far as dynamic/scripting languages go, TCL nailed it decades ago). But yeah, progress happens, it just might seem slow to the people who are watching from the side-lines (Since Squeak 3, I think). Keep on pushing forwards!

Feb. 29, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Miloslav.Raus＠cuzk.cz

Funny how the story changes depending on the point where one stands. OooooHHHHH, WE HAVE _AN_ APP. vs: Oh, they have an app ... OS/Ecosystem Integration is what matters Â· native integration o Drag & Drop (from the outside world) o taskbar/status icons o support for being launched as [Windows] Service o COM on windows (and I mean propper support, not the Astares placebo) o .NET bridge everywhere o perhaps even @#%$ Java Semblance of multicore support (even faked, as is â was? â the oh-so-great Cincom âMatrixâ) wouldnât hurt (as far as dynamic/scripting languages go, TCL nailed it decades ago). But yeah, progress happens, it just might seem slow to the people who are watching from the side-lines (Since Squeak 3, I think). Keep on pushing forwards! From: Noury Bouraqadi <bouraqadi(a)gmail.com> Sent: Tuesday, February 27, 2024 10:40 AM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>; Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes Cool. I think we need to share such success stories with the world through social media under the Pharo account. Just put the link of the story on LinkedIn and share the link here so we can like and share. Cheers, Noury On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: New Story posted on the Website: ApptiveGrid - Digitize and Automatize Business Processes https://www.pharo.org/success/ApptiveGrid.html Marcus

Feb. 29, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Noury Bouraqadi

Liked ð On Feb 27 2024, at 1:18 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Nice link: https://www.linkedin.com/company/pharoproject/ > > > On 27 Feb 2024, at 13:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Ah found it: > > > > I added a page: > > > > https://www.linkedin.com/company/102626671 > > > > > On 27 Feb 2024, at 12:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > Yes, that is a group. > > > > > > But I want to check how to post âas Pharoâ and not with my private account.. > > > > > > > On 27 Feb 2024, at 12:32, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > > > There is already a LinkedIn account for Pharo https://www.linkedin.com/groups/2558378/ > > > > On Feb 27 2024, at 11:38 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > Twitter and Facebook are posted today (posts are in the queue). > > > > > > > > > > I have on the TODO to create am official Pharo page? I think for LinkedIn. > > > > > > > > > > Marcus > > > > > > > > > > > On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > > > > > Cool. I think we need to share such success stories with the world through social media under the Pharo account. > > > > > > Just put the link of the story on LinkedIn and share the link here so we can like and share. > > > > > > > > > > > > Cheers, > > > > > > Noury > > > > > > On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > > > New Story posted on the Website: > > > > > > > > > > > > > > ApptiveGrid - Digitize and Automatize Business Processes > > > > > > > https://www.pharo.org/success/ApptiveGrid.html > > > > > > > > > > > > > > > > > > > > > Marcus

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Marcus Denker

Nice link: https://www.linkedin.com/company/pharoproject/ > On 27 Feb 2024, at 13:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Ah found it: > > I added a page: > > https://www.linkedin.com/company/102626671 > >> On 27 Feb 2024, at 12:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Yes, that is a group. >> >> But I want to check how to post âas Pharoâ and not with my private account.. >> >>> On 27 Feb 2024, at 12:32, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >>> >>> There is already a LinkedIn account for Pharo https://www.linkedin.com/groups/2558378/ >>> >>> On Feb 27 2024, at 11:38 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> Twitter and Facebook are posted today (posts are in the queue). >>> >>> I have on the TODO to create am official Pharo page? I think for LinkedIn. >>> >>> Marcus >>> >>> On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >>> >>> Cool. I think we need to share such success stories with the world through social media under the Pharo account. >>> Just put the link of the story on LinkedIn and share the link here so we can like and share. >>> >>> Cheers, >>> Noury >>> On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> New Story posted on the Website: >>> >>> ApptiveGrid - Digitize and Automatize Business Processes >>> https://www.pharo.org/success/ApptiveGrid.html >>> >>> >>> Marcus >> >

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Marcus Denker

Ah found it: I added a page: https://www.linkedin.com/company/102626671 > On 27 Feb 2024, at 12:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Yes, that is a group. > > But I want to check how to post âas Pharoâ and not with my private account.. > >> On 27 Feb 2024, at 12:32, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> There is already a LinkedIn account for Pharo https://www.linkedin.com/groups/2558378/ >> >> On Feb 27 2024, at 11:38 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> Twitter and Facebook are posted today (posts are in the queue). >> >> I have on the TODO to create am official Pharo page? I think for LinkedIn. >> >> Marcus >> >> On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> Cool. I think we need to share such success stories with the world through social media under the Pharo account. >> Just put the link of the story on LinkedIn and share the link here so we can like and share. >> >> Cheers, >> Noury >> On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> New Story posted on the Website: >> >> ApptiveGrid - Digitize and Automatize Business Processes >> https://www.pharo.org/success/ApptiveGrid.html >> >> >> Marcus >

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Marcus Denker

Yes, that is a group. But I want to check how to post âas Pharoâ and not with my private account.. > On 27 Feb 2024, at 12:32, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > There is already a LinkedIn account for Pharo https://www.linkedin.com/groups/2558378/ > > On Feb 27 2024, at 11:38 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Twitter and Facebook are posted today (posts are in the queue). > > I have on the TODO to create am official Pharo page? I think for LinkedIn. > > Marcus > > On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Cool. I think we need to share such success stories with the world through social media under the Pharo account. > Just put the link of the story on LinkedIn and share the link here so we can like and share. > > Cheers, > Noury > On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > New Story posted on the Website: > > ApptiveGrid - Digitize and Automatize Business Processes > https://www.pharo.org/success/ApptiveGrid.html > > > Marcus

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Noury Bouraqadi

There is already a LinkedIn account for Pharo https://www.linkedin.com/groups/2558378/ On Feb 27 2024, at 11:38 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Twitter and Facebook are posted today (posts are in the queue). > > I have on the TODO to create am official Pharo page? I think for LinkedIn. > > Marcus > > > On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Cool. I think we need to share such success stories with the world through social media under the Pharo account. > > Just put the link of the story on LinkedIn and share the link here so we can like and share. > > > > Cheers, > > Noury > > On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > New Story posted on the Website: > > > > > > ApptiveGrid - Digitize and Automatize Business Processes > > > https://www.pharo.org/success/ApptiveGrid.html > > > > > > > > > Marcus

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Marcus Denker

Twitter and Facebook are posted today (posts are in the queue). I have on the TODO to create am official Pharo page? I think for LinkedIn. Marcus > On 27 Feb 2024, at 10:40, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Cool. I think we need to share such success stories with the world through social media under the Pharo account. > Just put the link of the story on LinkedIn and share the link here so we can like and share. > > Cheers, > Noury > On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > New Story posted on the Website: > > ApptiveGrid - Digitize and Automatize Business Processes > https://www.pharo.org/success/ApptiveGrid.html > > > Marcus

Feb. 27, 2024

Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Noury Bouraqadi

Cool. I think we need to share such success stories with the world through social media under the Pharo account. Just put the link of the story on LinkedIn and share the link here so we can like and share. Cheers, Noury On Feb 26 2024, at 5:49 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > New Story posted on the Website: > > ApptiveGrid - Digitize and Automatize Business Processes > https://www.pharo.org/success/ApptiveGrid.html > > > Marcus

Feb. 27, 2024

[Success Story] ApptiveGrid - Digitize and Automatize Business Processes

by Marcus Denker

New Story posted on the Website: ApptiveGrid - Digitize and Automatize Business Processes https://www.pharo.org/success/ApptiveGrid.html Marcus

Feb. 26, 2024

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

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

by Marcus Denker

# Pharo11 - Tolerate halt when handling a OSWindowEvent #16095 https://github.com/pharo-project/pharo/pull/16095 # Networking - Improved error handling around sending data in Socket/SocketStream (fixes #15614) #15984 https://github.com/pharo-project/pharo/pull/15984 # Tools - New settings browser #681 https://github.com/pharo-spec/NewTools/pull/681 - File Dialog: Add dynamic preview #682 https://github.com/pharo-spec/NewTools/pull/682 - Add DoIt in background and a toolbar button to cancel the current exeâ¦ #672 https://github.com/pharo-spec/NewTools/pull/672 # Graphics - Add #scale and #formSet:at:sourceRect:rule: to Canvas hierarchies and #blendAlphaScaled for Form #16090 https://github.com/pharo-project/pharo/pull/16090 - Make ScalingCanvas avoid converting a Form in a FormSet for lookup in the FormMapping #16089 https://github.com/pharo-project/pharo/pull/16089 - Tolerate halt when handling a OSWindowEvent #16088 https://github.com/pharo-project/pharo/pull/16088 # Refactoring Eingine - Refactor: extract method transformation build transformations #16125 https://github.com/pharo-project/pharo/pull/16125 - Cleanup: push down instance variable breaking changes #16113 https://github.com/pharo-project/pharo/pull/16113 - Refactor: make pull up class variable same as pull up instance variable #16112 https://github.com/pharo-project/pharo/pull/16112 - Refactor: remove method new architecture #16107 https://github.com/pharo-project/pharo/pull/16107 - Refactor: remove preconditions from extract method's buildTransformations #16102 https://github.com/pharo-project/pharo/pull/16102 - Refactor: remove unused swap method refactoring #16101 https://github.com/pharo-project/pharo/pull/16101 - Refactor: preconditions of add method and migrate to new architecture #16098 https://github.com/pharo-project/pharo/pull/16098 - RB: Just renamed two classes #16097 https://github.com/pharo-project/pharo/pull/16097 # Bootstrap - Avoid merged tags without abbrev parameter for vm download in bootstrap script #16124 https://github.com/pharo-project/pharo/pull/16124 - Avoid merged tags for vm download in bootstrap script #16121 https://github.com/pharo-project/pharo/pull/16121 - Update bootstrap process to refer to Pharo12 #16021 https://github.com/pharo-project/pharo/pull/16021 # Cleanup - 15965-CI-Failing-tests-on-the-CI-ReleaseTeststestThatThereAreNoSelectorsRemainingThatAreSentButNotImplemented #16115 https://github.com/pharo-project/pharo/pull/16115 - 16053-RGMethodDefinitionstoreOn-should-not-be-an-extension #16116 https://github.com/pharo-project/pharo/pull/16116 - 16057-Cleanup-use-cascaded-nextPutAll-in-LocaleIDstoreOn #16100 https://github.com/pharo-project/pharo/pull/16100 - Array>>#displayString should be part of Kernel and not an override from NewTools #16069 https://github.com/pharo-project/pharo/pull/16069 - Display methods should be in "displaying" protocol #16058 https://github.com/pharo-project/pharo/pull/16058

Feb. 9, 2024

Open PhD position on debugging at Inria Lille

by Steven Costiou

Hello, we have a PhD position opening at Lille, France. See all details here: https://recrutement.inria.fr/public/classic/fr/offres/2024-07154 Steven. _Summary of the research proposal:_ ### Application development inevitably introduces bugs. Often, it's not clear why a code change introduced a bug. To find this cause-and-effect relationship and debug more efficiently, developers can sometimes rely on the existence of a previous version of the code without the bug. Yet, traditional debugging tools are not designed for this kind of work, making it a tedious operation. In this thesis, we propose an approach that enables us to understand and to debug an application in a LIVE SYSTEM, such as Pharo or Python, by comparing two executions with different results: one execution succeeds and the other fails. Based on this hypothesis, we propose in this thesis to answer the following challenges: - How to detect divergence, i.e. different behavior between two executions of a program? - How can we reduce the cost in time, memory and energy consumption of detecting divergence(s) on long executions? - What are the criteria for deciding whether a divergence is normal or unauthorized? - What about detecting multiple divergences in the same program? - What abstractions are needed to compare two executions of a program and detect divergences? To meet these challenges, in addition to a precise state-of-the-art on debugging techniques, the PhD student will study concrete cases of program execution and propose a tool to be integrated into Pharo.

Feb. 8, 2024

Open Call: Object-Centric Breakpoints experiment

by Steven Costiou

Dear Community, as part of a research project in the EVREF team, we are looking for people to participate to an empirical experiment on object-centric breakpoints - a debugging tool present in Pharo 9. Many people from the community already participated, and we thank them very much ð We are still looking for participants, we need 40 people to do the experiment! Please help us, in return it helps us understand better our tools and their impact and therefore build better tools for the Pharo community! For those who want to know a bit more, see my original email below. For those who just want to jump at the experiment, you can go there https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd Thanks in advance ð Steven. --- We would like to invite you to participate to our experimental study on Object-Centric Breakpoints. This study aims to evaluate and to understand how Object-Centric Breakpoints impacts the debugging activity. This experiment takes place in **Pharo 9**. In this experiment, we ask you to solve 2 debugging tasks, one with standard Pharo tools and one other with Object-Centric Breakpoints. Between the two tasks, you will have to follow a tutorialand warmup tasks to learn how to use the tool. **How to Participate:** All instructions are here, please read them carefully: https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd **About the Experiment:** The experiment last between 40 minutes and 2 hours. Participants should have experience with Pharo development and debugging. We recommend having more than 6 months experience in Pharo and debugging in general. You will gain insights into the Object-Centric Breakpoints approach and contribute to advancements in debugging research. Help us to build better debugging tools that help you debug! **Some constraints:** - You are not allowed to load external tools and baselines, but you can use anything that is in the base image - Please do the experiment in one shot if possible without interruptions - The experiment sends anonymous data to our inria server, please make sure that you have a valid internet connection - Please try to use the object-centric breakpoints when the experimental framework asks you to **Notes:** Participation is voluntary, and everything is anonymous. You can abandon the experiment at any point (and your data will be discarded). For any question, you can contact us: steven.costiou(a)inria.fr and valentin.bourcier(a)inria.fr Thank you for considering participating in our study. Your contribution will be valuable in advancing the field of debugging and helping us understand what tools we need to build for Pharo. Sincerely, Steven and Valentin, EVREF team, Inria

Feb. 2, 2024

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

by Marcus Denker

# Fixes - Fixes for browsing a package from a repository using Calypso #16009 https://github.com/pharo-project/pharo/pull/16009 - add a missing method ClyOldMessageBrowserAdapter #16083 https://github.com/pharo-project/pharo/pull/16083 - Fix String method causing multiple problems #16081 https://github.com/pharo-project/pharo/pull/16081 - SycBrowseClassCommand fix for Browse to class in method editor #16066 https://github.com/pharo-project/pharo/pull/16066 - Deprecations from SUnit testcases should be raised #16036 https://github.com/pharo-project/pharo/pull/16036 - Fixing object class initialize #16033 https://github.com/pharo-project/pharo/pull/16033 - adding an ifEmpty guard in RubTextSegmentMorph>>#computeStraightVertices to prevent a random CI crash #16016 https://github.com/pharo-project/pharo/pull/16016 # Enhancements - Use newtools for progressbars #16075 https://github.com/pharo-project/pharo/pull/16075 - Expand the dependency analyzer roots by default #16074 https://github.com/pharo-project/pharo/pull/16074 - Rework MorphTreeMorph, MorphTreeNodeMorph and SimpleHierarchicalListMorph to remove sends of #treeExpandedForm and #treeUnexpandedForm #16043 https://github.com/pharo-project/pharo/pull/16043 - Make FTBasicTreeListItem use a FormSet for the expand/collapse toggle #16037 https://github.com/pharo-project/pharo/pull/16037 - Move the call of the Deprecation>>transform to the Deprecation>>defaultAction #16040 https://github.com/pharo-project/pharo/pull/16040 # Refactoring Engine - Cleanup: RBMetaclass>>#realName: #16061 https://github.com/pharo-project/pharo/pull/16061 - Cleanup: small refactoring cleanups #16048 https://github.com/pharo-project/pharo/pull/16048 - Refactor: remaining preconditions #16044 https://github.com/pharo-project/pharo/pull/16044 - Refactor: rename preconditions of pacakge refactoring #16028 https://github.com/pharo-project/pharo/pull/16028 - Refactor: another pass on cleaning and splitting preconditions #16026 https://github.com/pharo-project/pharo/pull/16026 - Refactor: VariableRefactoring doesn't override preconditions #16023 https://github.com/pharo-project/pharo/pull/16023 - Refactor: change method name preconditions #16022 https://github.com/pharo-project/pharo/pull/16022 - Refactor refactoring preconditions #16020 https://github.com/pharo-project/pharo/pull/16020 # Cleanups - Change #notNil into #isNotNil in Fuel test packages #16071 https://github.com/pharo-project/pharo/pull/16071 - Cleanup: Fix lint in MetaLinkAnonymousClassBuilderTest>>#testCompileCâ¦ #16063 https://github.com/pharo-project/pharo/pull/16063 - Replaced aCollection asOrderedCollection copy to OrderedCollection withAll: aCollection #16032 https://github.com/pharo-project/pharo/pull/16032 - Add two tests for the class StringTest #16031 https://github.com/pharo-project/pharo/pull/16031 - Fix #16024 remove dead code #16025 https://github.com/pharo-project/pharo/pull/16025

Feb. 2, 2024

Re: About removing class side initialization

by Guillermo Polito

> El 31 ene 2024, a las 15:36, Marcus Denker <marcus.denker(a)inria.fr> escribiÃ³: > > For both #isAbstract and #initialize, one can understand both as cases where we have to use behavior for something that should actually be a kind o declarative property of the objects. > > - isAbstract > > This is a property of the class. > > - initialize > > This is a property of the Variable. Itâs really unfortunate to have to fall back on code execution for that. What the initalize does is to say There is out there indeed code that uses class side initialize methods to initialize class variables to constants. But that is not the only case. Some class side initalizes have complex initializations. Some are used to register the loaded class to some registration mechanism. > >> On 31 Jan 2024, at 15:03, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> This is indeed an issue I'd like to see solved. >> Class initialization is just an instance of a more general isssue. >> In SUnit, defining abstract classes is dirty. The code often looks like this >> MyTestClass class>>#isAbstract >> ^self == MyTestClass >> In PharoJS we face the issue of class specific methods. Upon transpiling to JS, we want to perform some actions for some classes and not their subclasses. >> A possible solution is to introduce class specific properties through an extra-layer of metaclasses. Yes, I agree. I would like to have two levels of âMetaclassesâ. Actually, one metaclass that is the traditional metaclass defining the class behavior. One âcompanionâ object where we can define domain concerns. The companion object should respect the double hierarchy, but it will not class anymore with the meta-behaviour in the class! We will be able to freely program there without mistakenly overriding critical behavior from classes :). And we will be able to define metaclasses with really specific behavior for a single class in the hierarchy chain. G

Feb. 1, 2024