January 2023 - Pharo-dev - lists.pharo.org

[ANN] Pharo Mastodon

by Marcus Denker

Yes, not really news: Since Jan 4, 2018 we have a mastodon account. Esteban created that very early on, for now it re-shares the @pharoproject twitter account. https://mastodon.social/@pharoproject <https://mastodon.social/@pharoproject> I have finally updated https://www.pharo.org/community to link to it. Marcus

Jan. 20, 2023

This week (3/2023) on the Pharo Issue Tracker

by Marcus Denker

Features ======== - Add ifCutOn:doWithCutAndUncuts: #12374 https://github.com/pharo-project/pharo/pull/12374 - Lint rule warning for Calypso to warn unconditional recursion #12389 https://github.com/pharo-project/pharo/pull/12389 - Add #normalizeCamelCase and test #12373 https://github.com/pharo-project/pharo/pull/12373 - Add Generator class>>onDo: #12395 https://github.com/pharo-project/pharo/pull/12395 Fixes ===== - Variables: Fix Prrinting and Fluid Class definition that uses ClassVariable #12333 https://github.com/pharo-project/pharo/pull/12333 - Spotter is broken> DNU #tools #12397 https://github.com/pharo-project/pharo/pull/12397 - fixes #1659 IceCredentialStore did not understand #repositoryModel #1661 https://github.com/pharo-vcs/iceberg/pull/1661 - Issue 1275: Notify scroll changes #1344 https://github.com/pharo-spec/Spec/pull/1344 - fix tags access #1660 https://github.com/pharo-vcs/iceberg/pull/1660 Cleanup ======= - Move SmallInteger class>>#guideToDivision comment to class comment. #12391 https://github.com/pharo-project/pharo/pull/12391 - avoid hardcoding smalltalk everywhere and just factor out some use foâ¦ #449 https://github.com/pharo-spec/NewTools/pull/449 - Refactoring/categorizing unexposed refactorings #12370 https://github.com/pharo-project/pharo/pull/12370 - 20x cleanups of the kind Cleanup: Condense FFI-Kernel package #12328 https://github.com/pharo-project/pharo/pull/12328 - extract return from ifTrue:ifFalse: expression and whitespaces at the eol #12332 https://github.com/pharo-project/pharo/pull/12332 - extract return from ifTrue:ifFalse: expression #12177 https://github.com/pharo-project/pharo/pull/12177

Jan. 20, 2023

Fwd: Iceberg in github action

by Pierre Misse Chanabier

Hi, After quite a bit of work and investigating, we are finally able to use iceberg scripting in smalltalkci :) https://github.com/hpi-swa/smalltalkCI/pull/582 I'm using it in my Polyphemus repository if you want an example (https://github.com/hogoww/Polyphemus/actions) Cheers, Pierre

Jan. 14, 2023

This week (2/2023) on the Pharo Issue Tracker

by Marcus Denker

42 PRs merged, 40 Issues closed Features ======= - RubTextEditor/TextEditor: Make ctrl+backspace delete the previous word #12096 https://github.com/pharo-project/pharo/pull/12096 - Add source and target labels to SpChooserPresenter ( #1341) #1342 https://github.com/pharo-spec/Spec/pull/1342 Git/Iceberg ============ - add a manual way to add/remove tags #1657 https://github.com/pharo-vcs/iceberg/pull/1657 - add default tag "system" to bootstrap registered projects #12303 https://github.com/pharo-project/pharo/pull/12303 - fix bad categorizations #1655 https://github.com/pharo-vcs/iceberg/pull/1655 - Adapt to latest spec2 pass2 #1632 https://github.com/pharo-vcs/iceberg/pull/1632 Refactoring Engine ================== - Cleaning RB issues #12151 https://github.com/pharo-project/pharo/pull/12151 - Refactorings cleanup #12256 https://github.com/pharo-project/pharo/pull/12256 Fixes ===== - Fix refactoring using old class def #12195 https://github.com/pharo-project/pharo/pull/12195 - remove ByteLayout from FFIBackend and children #12225 https://github.com/pharo-project/pharo/pull/12225 - 12289-Refactoring-Tests-are-failling-when-using-Fluid-syntax #12290 https://github.com/pharo-project/pharo/pull/12290 - Fix hasSelector:specialSelectorIndex: on FFI methods that are compiled #12305 https://github.com/pharo-project/pharo/pull/12305 - 12300-Compiler-is-slow-with-string-literals-containing-exclamation-marks #12306 https://github.com/pharo-project/pharo/pull/12306 Cleanups ======== - 18 whitespace cleanups like Cleanup: Condense CodeImport packages #12229 https://github.com/pharo-project/pharo/pull/12229 - 5 remove return out of isTrue:ifFalse: lke extract return from ifTrue:ifFalse: expression in Number floor #12292 https://github.com/pharo-project/pharo/pull/12292 - remove #Numeric from source code. #12265 https://github.com/pharo-project/pharo/pull/12265 - 12307 remove gt pragma #12308 https://github.com/pharo-project/pharo/pull/12308 - Unncessary class RBMissingOpenerErrorNode #12313 https://github.com/pharo-project/pharo/pull/12313 - Class RBShortAssignmentToken is not needed anymore #12315 https://github.com/pharo-project/pharo/pull/12315 Comments ======== - Improving layoutFrame comments and add examples (fixes #12259) #12260 https://github.com/pharo-project/pharo/pull/12260 - extract comments as runnable example in Number>>#// #12263 https://github.com/pharo-project/pharo/pull/12263 - use isInstanceSide message in example #12270 https://github.com/pharo-project/pharo/pull/12270

Jan. 13, 2023

[Website] some fixes: links to mailinglist and newsletter

by Marcus Denker

Hi, A small update to https://www.pharo.org/community I fixed the links to the mailinglist and the newsletter subcription. (there are real âaboutâ pages.. I guess I was not the only one complaining that this is neededâ¦) https://lists.pharo.org/list/pharo-dev.lists.pharo.org https://lists.pharo.org/list/pharo-users.lists.pharo.org <https://lists.pharo.org/list/pharo-users.lists.pharo.org> (this closes https://github.com/pharo-project/pharo-site/issues/13) Marcus

Jan. 12, 2023

IWST proceedings online

by stephane ducasse

Hi guys Iâm happy to sahre with you this EXCELLENT news. The proceedings of IWST 22 are now online https://ceur-ws.org/Vol-3325/ï¿¼ in a nice collection. I would like to warmly thank all the authors, loic and vincent for their great job. Soon we will send around the call for paper for 2023! S

Jan. 11, 2023

Re: Linux OBS builds updated

by Pavel Krivanek

Hi, Ãºt 10. 1. 2023 v 12:06 odesÃlatel Guillermo Polito < guillermopolito(a)gmail.com> napsal: > Hi Pavel, > > thanks for looking into this. > > Why not adding those mappings in the table so they are mapped by `self > mapSpecialCharacter: keysym sym` ? > This method does not take into account NumLock status and just converts the character. But we may consider creating some table for it instead of just a row of ifs. Originally, I expected to need to convert only four keys, so the table would be a slower overkill, but now it may make sense. But maybe it may make sense to create an even more general table that would handle the conversion of any key, including various modifiers. Let's move the conversation to the PR discussion: https://github.com/pharo-project/pharo/pull/12258 -- Pavel > > G > > El 6 ene. 2023, a las 08:53, Pavel Krivanek <pavel.krivanek(a)gmail.com> > escribiÃ³: > > Hi, > > that is interesting issue. I have here a notebook with Numpad where I can > reproduce it. Pharo is getting information from SDL2 and there nothing > really seems to tell us that the incomming event is PgDown or similar key. > > If I log incomming events in OSSDL2BackendWindow>>#visitKeyDownEvent:, I'm > getting these values: > > Num 3 > a SDL_KeyDownEventan Array(835757 a SDL_Keysym#(4096 91 1073741915) 768 1 > 1) > Num PgDown > a SDL_KeyDownEventan Array(860624 a SDL_Keysym#(0 91 1073741915) 768 1 1) > PgDown > a SDL_KeyDownEventan Array(886723 a SDL_Keysym#(0 78 1073741902) 768 1 1) > > (ignore the first number, the values in SDL_Keysym are mod, scancode, sym) > > So the information about the key event only differs in the Num Lock > modifier. It is way too low-level. I see now the only solution - to the the > ugly manual conversion, You may try to install the attached *.st file (drag > it on Pharo window and then choose to install). > > I will open an issue. > > Cheers, > -- Pavel > > > > Ät 5. 1. 2023 v 17:18 odesÃlatel Aik-Siong Koh <askoh(a)askoh.com> napsal: > >> Thanks for help. >> I have an OMEN 17" notebook. >> The keyboard has NumPad with Num Lock. >> Superimposed on the numbers are Home, End, PgUp, etc. >> When Num Lock is on, 1,2,3,4... works everywhere in Windows and apps. >> When Num Lock is off, Home, End, PgUp, etc. work in Windows and every app >> except in Pharo (9, 10 or 11). >> In Pharo, pressing the Home key does nothing at all. >> >> FYI. Above the Numpad are two keys: (HOME / PG UP) and (END / PG DN) >> They work in Pharo with the FN key to get HOME and END. >> >> I hope this helps. >> >> Aik-Siong Koh >> >> >> Pavel Krivanek wrote: >> >> Hi, in Schmidt, we use Pharo 11 on Windows and Home and End keys work for >> us. Tested in the code editor and Calypso lists. Do you miss it in some >> special context, or does it not work for you at all? Do you use some >> different input methods? Or keyboard layouts are the boring European ones. >> >> -- Pavel >> >> st 4. 1. 2023 v 16:09 odesÃlatel Aik-Siong Koh <askoh(a)askoh.com> napsal: >> >>> I do use Pharo Launcher. >>> I really miss Home and End keys in Pharo right now. >>> Are there very few users of Pharo in Windows? >>> Aik-Siong >>> >>> Esteban Lorenzano wrote: >>> >>> yes, but for windows the recommended way is to use the pharo launcher >>> installer : https://files.pharo.org/pharo-launcher/windows >>> or, if you want to download the standalone VM: >>> http://files.pharo.org/get-files/100/pharo-vm-Windows-x86_64-stable.zip >>> Esteban >>> >>> On Jan 4 2023, at 3:25 pm, Aik-Siong Koh <askoh(a)askoh.com> >>> <askoh(a)askoh.com> wrote: >>> >>> >>> Does Windows get as good support as Linux or Mac? >>> I am waiting for the Home and End key to work on Windows. >>> Thanks, >>> Aik-Siong Koh >>> >>> Esteban Lorenzano wrote: >>> >>> >>> Hi, >>> >>> I updated linux OBS builds to get it up to date with distro changes : >>> >>> Added: >>> >>> - Fedora 37 >>> - Ubuntu 22.10 >>> - OpenSUSE Leap 15.3 >>> - OpenSUSE Leap 15.4 >>> >>> Fixed: >>> >>> - Arch (Manjaro) >>> - OpenSUSE Tumbleweed >>> >>> Removed (Obsoletes): >>> >>> - OpenSUSE Leap 15.1 >>> - OpenSUSE Leap 15.2 >>> - Fedora 32 >>> - Fedora 33 >>> >>> You can test all the new/fixed as correspond: >>> https://software.opensuse.org//download.html?project=devel%3Alanguages%3Aph… >>> Enjoy, >>> Esteban >>> >>> >>> >> <OSSDL2BackendWindow-visitKeyDownEvent...st> > > >

Jan. 11, 2023

Re: Linux OBS builds updated

by Guillermo Polito

Hi Pavel, thanks for looking into this. Why not adding those mappings in the table so they are mapped by `self mapSpecialCharacter: keysym sym` ? G > El 6 ene. 2023, a las 08:53, Pavel Krivanek <pavel.krivanek(a)gmail.com> escribiÃ³: > > Hi, > > that is interesting issue. I have here a notebook with Numpad where I can reproduce it. Pharo is getting information from SDL2 and there nothing really seems to tell us that the incomming event is PgDown or similar key. > > If I log incomming events in OSSDL2BackendWindow>>#visitKeyDownEvent:, I'm getting these values: > > Num 3 > a SDL_KeyDownEventan Array(835757 a SDL_Keysym#(4096 91 1073741915) 768 1 1) > Num PgDown > a SDL_KeyDownEventan Array(860624 a SDL_Keysym#(0 91 1073741915) 768 1 1) > PgDown > a SDL_KeyDownEventan Array(886723 a SDL_Keysym#(0 78 1073741902) 768 1 1) > > (ignore the first number, the values in SDL_Keysym are mod, scancode, sym) > > So the information about the key event only differs in the Num Lock modifier. It is way too low-level. I see now the only solution - to the the ugly manual conversion, You may try to install the attached *.st file (drag it on Pharo window and then choose to install). > > I will open an issue. > > Cheers, > -- Pavel > > > > Ät 5. 1. 2023 v 17:18 odesÃlatel Aik-Siong Koh <askoh(a)askoh.com <mailto:askoh@askoh.com>> napsal: > Thanks for help. > I have an OMEN 17" notebook. > The keyboard has NumPad with Num Lock. > Superimposed on the numbers are Home, End, PgUp, etc. > When Num Lock is on, 1,2,3,4... works everywhere in Windows and apps. > When Num Lock is off, Home, End, PgUp, etc. work in Windows and every app except in Pharo (9, 10 or 11). > In Pharo, pressing the Home key does nothing at all. > > FYI. Above the Numpad are two keys: (HOME / PG UP) and (END / PG DN) > They work in Pharo with the FN key to get HOME and END. > > I hope this helps. > > Aik-Siong Koh > > > Pavel Krivanek wrote: >> Hi, in Schmidt, we use Pharo 11 on Windows and Home and End keys work for us. Tested in the code editor and Calypso lists. Do you miss it in some special context, or does it not work for you at all? Do you use some different input methods? Or keyboard layouts are the boring European ones. >> >> -- Pavel >> >> st 4. 1. 2023 v 16:09 odesÃlatel Aik-Siong Koh <askoh(a)askoh.com <mailto:askoh@askoh.com>> napsal: >> I do use Pharo Launcher. >> I really miss Home and End keys in Pharo right now. >> Are there very few users of Pharo in Windows? >> Aik-Siong >> >> Esteban Lorenzano wrote: >>> yes, but for windows the recommended way is to use the pharo launcher installer : https://files.pharo.org/pharo-launcher/windows <https://files.pharo.org/pharo-launcher/windows> >>> or, if you want to download the standalone VM: http://files.pharo.org/get-files/100/pharo-vm-Windows-x86_64-stable.zip <http://files.pharo.org/get-files/100/pharo-vm-Windows-x86_64-stable.zip> >>> Esteban >>> >>> On Jan 4 2023, at 3:25 pm, Aik-Siong Koh <askoh(a)askoh.com> <mailto:askoh@askoh.com> wrote: >>> >>> Does Windows get as good support as Linux or Mac? >>> I am waiting for the Home and End key to work on Windows. >>> Thanks, >>> Aik-Siong Koh >>> >>> Esteban Lorenzano wrote: >>> >>> Hi, >>> >>> I updated linux OBS builds to get it up to date with distro changes : >>> >>> Added: >>> Fedora 37 >>> Ubuntu 22.10 >>> OpenSUSE Leap 15.3 >>> OpenSUSE Leap 15.4 >>> Fixed: >>> Arch (Manjaro) >>> OpenSUSE Tumbleweed >>> Removed (Obsoletes): >>> OpenSUSE Leap 15.1 >>> OpenSUSE Leap 15.2 >>> Fedora 32 >>> Fedora 33 >>> You can test all the new/fixed as correspond: https://software.opensuse.org//download.html?project=devel%3Alanguages%3Aph… <https://software.opensuse.org//download.html?project=devel%3Alanguages%3Aph…> >>> Enjoy, >>> Esteban >> > > <OSSDL2BackendWindow-visitKeyDownEvent...st>

Jan. 10, 2023

Draft Phep on new Finalization

by Guillermo Polito

Hi all, Iâve drafted a phep proposal for the new finalization mechanism, so we can discuss it here! https://github.com/pharo-project/pheps/pull/14 <https://github.com/pharo-project/pheps/pull/14> A proposal describing a new finalization mechanism for Pharo with the following properties: â¢ API independent from its implementation â¢ Avoids memory leaks This document describes both a finalization API as a Pharo library and an efficient virtual machine implementation through Ephemerons. Cheers, G

Jan. 9, 2023

Re: This week (1/2023) on the Pharo Issue Tracker

by Noury Bouraqadi

The new year comes with more new improvements. Thank you Marcus and all the contributors. Best wishes for 2023! Noury On Jan 6 2023, at 11:17 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: > I archive the weekly logs here: > > https://github.com/pharo-project/pharo-changelogs/tree/master/weekly (https://link.getmailspring.com/link/E6FC5EC9-9F41-49C6-AB11-94DC6C756EE1@ge…) > > (started with 36/2022, it would be nice to add archive the older mailsâ¦) > > Marcus > > > On 6 Jan 2023, at 11:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > We merged 32 PRs and closed 16 issues this week > > Features > > ========= > > > > - Slots: For experiments, add Setting for unrestricted definitions #12113 > > https://github.com/pharo-project/pharo/pull/12113 > > > > - Introduce release test to check that "selectors send but not implemented" cases do not grow #12117 > > https://github.com/pharo-project/pharo/pull/12117 > > > > - New rule to remove unnecessary separators and dots #12167 > > https://github.com/pharo-project/pharo/pull/12167 > > > > - Potential Magritte extensions to be harvested to improve collection #12179 > > https://github.com/pharo-project/pharo/pull/12179 > > > > > > Fixes > > ===== > > > > - DoubleLinkedList newFrom: does not work correctly #12164 > > https://github.com/pharo-project/pharo/pull/12164 > > > > - Formatter adds unnecessary empty line before (first) method comment #12178 > > https://github.com/pharo-project/pharo/pull/12178 > > > > - Recursion found #12182 > > https://github.com/pharo-project/pharo/pull/12182 > > > > - fix Set class comment #12222 > > https://github.com/pharo-project/pharo/pull/12222 > > > > - RBMakeClassAbstractTransformation-no-whitespace #12209 > > https://github.com/pharo-project/pharo/pull/12209 > > > > - fix TFProcessLocalWorker with callbacks #12207 > > https://github.com/pharo-project/pharo/pull/12207 > > > > - ReCompactSourceCodeCritic should change origin method - not methodClass #12202 > > https://github.com/pharo-project/pharo/pull/12202 > > > > - 12157-BadHasherhash-should-return-a-value #12199 > > https://github.com/pharo-project/pharo/pull/12199 > > > > - 12191-RBAddMethodChange-moves-all-uncategorized-to-accessing #12192 > > https://github.com/pharo-project/pharo/pull/12192 > > > > Cleanup > > ======= > > > > - Move SearchFacade to MonticelloGUI #12144 > > https://github.com/pharo-project/pharo/pull/12144 > > > > - 11634-Unimplemented-message-send-in-FT2FaceemboldenOutline #12103 > > https://github.com/pharo-project/pharo/pull/12103 > > > > - extract return statement from ifTrue:ifFalse: expression. fix: #12155 #12156 > > https://github.com/pharo-project/pharo/pull/12156 > > > > - Cleanup: fix lints for morphic classes on class side #initialize (SECOND ATTEMPT) #12160 > > https://github.com/pharo-project/pharo/pull/12160 > > > > - Cleanup: more instance side #initialize categorization cleanups (SECOND ATTEMPT) #12227 > > https://github.com/pharo-project/pharo/pull/12227 > > > > - Many (12) whitespace cleanups PR like: Cleanup: Condense AST- packages #12185 > > https://github.com/pharo-project/pharo/pull/12185 > > > > > > >

Jan. 6, 2023