- Pharo-dev - lists.pharo.org

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

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

by Marcus Denker

I archive the weekly logs here: https://github.com/pharo-project/pharo-changelogs/tree/master/weekly (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

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

by Marcus Denker

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

Re: Linux OBS builds updated

by Pavel Krivanek

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 >> >> >> >

Jan. 6, 2023

Re: Linux OBS builds updated

by Aik-Siong Koh

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 >> 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> >> <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… >> Enjoy, >> Esteban >> >

Jan. 5, 2023

Re: Linux OBS builds updated

by Pavel Krivanek

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 > > >

Jan. 5, 2023

Re: Linux OBS builds updated

by Aik-Siong Koh

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> 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 >

Jan. 4, 2023