May 2023 - Pharo-users - lists.pharo.org

Re: It's been a while since I've used Pharo, and I'm having trouble with multibyte input on linux.

by stephane ducasse

Thanks Tomohiro. S > On 19 May 2023, at 00:33, Tomohiro Oda <tomohiro.tomo.oda(a)gmail.com> wrote: > > Peter, > > Please try setting the env vars SDL_IM_MODULE=fcitx. > I haven't tried korean inputs, but I used a japanese input on > linux/pharo with a trick. (cf > https://github.com/tomooda/PharoIM/issues/11#issuecomment-1042512413 ) > > If you want to use Pharo 10 with input method, please install > https://github.com/tomooda/PharoIM . > If you use Pharo 11, you don't need PharoIM. > --- > tomo > > 2023å¹´5æ19æ¥(é) 1:44 peter yoo <onionmixer(a)gmail.com>: >> >> Until PHARO 9.0, I had no problem with XIM input on LINUX. >> >> After a long time, I heard about PHARO 11 and tested it and it doesn't accept XIM input. I tested it and it doesn't accept XIM input on PHARO 10 either. >> >> * ubuntu 22.04 >> * linux >> * fcitx xim >> * korean input >> >> I'm using this combination, and I'm using pharo-launcher. >> >> Maybe the community can give me a hint? >> >> -- >> http://lookandwalk.com http://looknw.com | http://onionmixer.net >> peter yoo(Jonghwa Yoo). ROK

May 18, 2023

Re: It's been a while since I've used Pharo, and I'm having trouble with multibyte input on linux.

by Tomohiro Oda

Peter, Please try setting the env vars SDL_IM_MODULE=fcitx. I haven't tried korean inputs, but I used a japanese input on linux/pharo with a trick. (cf https://github.com/tomooda/PharoIM/issues/11#issuecomment-1042512413 ) If you want to use Pharo 10 with input method, please install https://github.com/tomooda/PharoIM . If you use Pharo 11, you don't need PharoIM. --- tomo 2023å¹´5æ19æ¥(é) 1:44 peter yoo <onionmixer(a)gmail.com>: > > Until PHARO 9.0, I had no problem with XIM input on LINUX. > > After a long time, I heard about PHARO 11 and tested it and it doesn't accept XIM input. I tested it and it doesn't accept XIM input on PHARO 10 either. > > * ubuntu 22.04 > * linux > * fcitx xim > * korean input > > I'm using this combination, and I'm using pharo-launcher. > > Maybe the community can give me a hint? > > -- > http://lookandwalk.com http://looknw.com | http://onionmixer.net > peter yoo(Jonghwa Yoo). ROK

May 18, 2023

Re: It's been a while since I've used Pharo, and I'm having trouble with multibyte input on linux.

by stephane ducasse

Hi peter What is xim? What you should know is that Pharo event / input now is based on SDL 20. S > On 18 May 2023, at 18:44, peter yoo <onionmixer(a)gmail.com> wrote: > > Until PHARO 9.0, I had no problem with XIM input on LINUX. > > After a long time, I heard about PHARO 11 and tested it and it doesn't accept XIM input. I tested it and it doesn't accept XIM input on PHARO 10 either. > > * ubuntu 22.04 > * linux > * fcitx xim > * korean input > > I'm using this combination, and I'm using pharo-launcher. > > Maybe the community can give me a hint? > > -- > http://lookandwalk.com <http://lookandwalk.com/> http://looknw.com <http://looknw.com/> | http://onionmixer.net <http://onionmixer.net/> > peter yoo(Jonghwa Yoo). ROK

May 18, 2023

It's been a while since I've used Pharo, and I'm having trouble with multibyte input on linux.

by peter yoo

Until PHARO 9.0, I had no problem with XIM input on LINUX. After a long time, I heard about PHARO 11 and tested it and it doesn't accept XIM input. I tested it and it doesn't accept XIM input on PHARO 10 either. * ubuntu 22.04 * linux * fcitx xim * korean input I'm using this combination, and I'm using pharo-launcher. Maybe the community can give me a hint? -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

May 18, 2023

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

by Marcus Denker

We released Pharo11 this week! see https://www.pharo.org/news/pharo11-released.html # Pharo 11 - Fix welcomebrowser version #13691 https://github.com/pharo-project/pharo/pull/13691 - Backport fixe #13663: Enabling the setting âShow lines numbers for all browsers #13665 https://github.com/pharo-project/pharo/pull/13665 - fix iceberg version for Pharo 11 #13655 https://github.com/pharo-project/pharo/pull/13655 - fix a bug with cmd+g usage #517 https://github.com/pharo-spec/NewTools/pull/517 - change spotter selection paste default #519 https://github.com/pharo-spec/NewTools/pull/519 # Pharo 12 ## Fixes - Improve some error logging #13689 https://github.com/pharo-project/pharo/pull/13689 - Enabling the setting âShow lines numbers for all browsersâ only shows line numbers for the first method selected in a class #13663 https://github.com/pharo-project/pharo/issues/13663 ## Variables - Allow-Slots-Shadow-PseudoVariables #13704 https://github.com/pharo-project/pharo/pull/13704 - Simplify ReservedVariable: #styleNameIn and remove #nameIsReserved: #13701 https://github.com/pharo-project/pharo/pull/13701 - ReservedVariable: No need for Singleton #13688 https://github.com/pharo-project/pharo/pull/13688 - Added thisProcess pseudovariable using existing bytecode. #13661 https://github.com/pharo-project/pharo/pull/13661 ## SystemOrganizer / RPackage - Remove dead code in RPackageOrganizer default instance #13660 https://github.com/pharo-project/pharo/pull/13660 - Reduces the references to RPackageOrganizer class>>default #13666 https://github.com/pharo-project/pharo/pull/13666 - Move system organizer to RPackage and remove references #13677 https://github.com/pharo-project/pharo/pull/13677 - Remove SystemOrganizer #13690 https://github.com/pharo-project/pharo/pull/13690 - Use Smalltalk organization in DependencyAnalyzer #13671 https://github.com/pharo-project/pharo/pull/13671 ## Protocols / Categories - Do not classify silently methods #13650 https://github.com/pharo-project/pharo/pull/13650 - Start protocol announcements testing + add feature to Announcer #13649 https://github.com/pharo-project/pharo/pull/13649 - Deprecate ProtocolRenamed #13659 https://github.com/pharo-project/pharo/pull/13659 - Small cleanup on protocol cleaning #13642 https://github.com/pharo-project/pharo/pull/13642 - Rename Protocol class>>#name: into #named: #13670 https://github.com/pharo-project/pharo/pull/13670 - Use real protocol in recategorization mecanism #13669 https://github.com/pharo-project/pharo/pull/13669 - Introduce ClassDescription>>#protocolNames and start using it #13658 https://github.com/pharo-project/pharo/pull/13658 - Add some tests on protocol announcements #13706 https://github.com/pharo-project/pharo/pull/13706 - Removal of nonexisting protocol should not announce anything #13702 https://github.com/pharo-project/pharo/pull/13702 ## Code Completion - Completion autoclose menu #13647 https://github.com/pharo-project/pharo/pull/13647 - Completion: improve completion on super #13679 https://github.com/pharo-project/pharo/pull/13679 - Completion: replacement put caret at the right place #13683 https://github.com/pharo-project/pharo/pull/13683 - Completion mini fixes #13696 https://github.com/pharo-project/pharo/pull/13696 - Basic type analysis for better completion #13687 https://github.com/pharo-project/pharo/pull/13687 - More type analysis #13697 https://github.com/pharo-project/pharo/pull/13697 - CompletionEngine do not automatically open empty completion menus #13705 https://github.com/pharo-project/pharo/pull/13705 - NECPreferences remove leftover of captureNavigationKeys #13703 https://github.com/pharo-project/pharo/pull/13703 - Completion: better update #13700 https://github.com/pharo-project/pharo/pull/13700 - Completion browse with Ctrl-B #13699 https://github.com/pharo-project/pharo/pull/13699 ## Cleanups - Clean some code using better condition branches #13668 https://github.com/pharo-project/pharo/pull/13668 - Remove some duplication in image cleaner #13676 https://github.com/pharo-project/pharo/pull/13676 - Message: rename ivar "args" to "arguments #13654 https://github.com/pharo-project/pharo/pull/13654 - Cleanup: Metacello-Platform #13682 https://github.com/pharo-project/pharo/pull/13682 - remove MetacelloPharo30Platform from 01-loadMetacello.st #13684 https://github.com/pharo-project/pharo/pull/13684 - Clean monticello class definition management #13680 https://github.com/pharo-project/pharo/pull/13680

May 15, 2023

Re: [ANN] Pharo 11 Released !

by igouy2＠yahoo.com

fwiw https://pharo.org/download âPharo stable VM for Windowsâ http://files.pharo.org/get-files/100/pharo-vm-Windows-x86_64-stable.zip Using: Microsoft Edge Version 113.0.1774.42 (Official build) (64-bit) shows: pharo-vm-Windows-x86_64-stable.zip can't be downloaded securely Figuring out how to reset Microsoft Edge to allow insecure content from https://pharo.org/download was quite a struggle. With: pharo64.zip pharo-vm-Windows-x86_64-stable.zip unzipped into the same directory: >Pharo.exe Pharo10-SNAPSHOT-64bit-179ef65.image opens and fails with: \[Post-mortem\] PrimitiveFailed: primitive #createDirectory: in WindowsStore failed Windows 10 Home 22H2

May 13, 2023

[ANN] docker-pharo-runtime v11.0.0-2023-05-12 [v11.0.0 [2023-05-12]] released!

by Buenos Aires Smalltalk

May 12, 2023

Re: [ANN] Pharo 11 Released !

by Norbert Hartl

Hurray! Congats to all of you for the hard work once more to bring it to life. And I like the picture that does not lie about us not having HiDPI ð Now I need to upgrade all of my stuff again !! norbert > Am 11.05.2023 um 13:39 schrieb Esteban Lorenzano <estebanlm(a)netc.eu>: > > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > Some highlights of this amazing version: > Highlights > > Tools > Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. > Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. > The is a new implementation of rewrite tools and improved refactoring support. > There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. > New Tools presented in Calypso (the System Browser) and additional extended Inspectors. > All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. > System > Extended Full Blocks and Constant Clock closures support. > Additional Inlining and optimizations > Bug Fixes and Clean up. > Ephemeron Finalization support. > Virtual machine > Ephemerons Production Ready. > Initial support for Single-Instruction Multiple-Data (SIMD). > Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). > Clean Ups: Remove lots of old code, notably old experiments, and dead code. > Development Effort > > This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation

May 12, 2023

Re: [Pharo-dev] Pharo contribution Jenkins end of service

by Guillermo Polito

Thanks Christophe! > El 11 may. 2023, a las 11:32, Christophe Demarey <christophe.demarey(a)inria.fr> escribiÃ³: > > Hi all, > > Some years ago, we provided a Jenkins instance to check the health / quality of projects that are not in Pharo core but important for the community: > https://ci.inria.fr/pharo-contribution/ <https://ci.inria.fr/pharo-contribution/> > > Since, we moved to GitHub and GitHub actions are mainly used to achieve the same goal. Therefore there is no more reason to keep this service. Thatâs why we decided to stop the Pharo contribution Jenkins on 12th June 2023. > If you need to save some data (job artefacts, job setup), let us know. The server is now up but it has not been updated since a while and can stop working from time to time. > > On 12th June 2023, we will shutdown the server and all data will be removed. > > The Pharo team.

May 12, 2023

Re: Pharo being featured in Exercism's Mind Shifting May

by Tim Mackinnon

Those are some nice soundbites - and pleased to see they capture the spirit of Pharo (and Smalltalk). I was heartened in the second link to see that he picked up on the ability to define code from DNU (something we tried to show in the early exercism launch - although having not kept up with it, I don't know if that remains true - potentially if thats what the speaker picked up on), Thanks for keeping the project alive David! On Tue, 2 May 2023, at 8:09 AM, bajger(a)gmail.com wrote: > Hi Sean! > > Sorry, I didnât realize link points to private conversation. Anyway, here is result - links to video segments related to Pharo (extending to what Offray already wrote): > > Introducing Pharo: https://youtu.be/RpbpnmTfd8w?t=790 > > Unique features of Pharo: https://youtu.be/RpbpnmTfd8w?t=3059 > > > > Cheers! > > David >

May 11, 2023