- Pharo-dev - lists.pharo.org

[ANN] Pharo 10 released!
by Esteban Lorenzano April 6, 2022

April 6, 2022

Dear Pharo users and dynamic language lovers: We have released Pharo version 10 (https://pharo.org/) ! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Pharo 10 was a short iteration where we focused mainly on stability and enhancement of the environment : Massive system cleanup gained speed removed dead code removed old/deprecated frameworks (Glamour, GTTools, Spec1) All Remaining tools written using the deprecated frameworks have been rewritten: Dependency Analyser, Critique Browser, and many other small utilities. Modularisation has made a leap, creating correct baselines (project descriptions) for many internal systems, making possible the work and deployment of minimal images. Removing support for the old Bytecode sets and embedded blocks simplified the compiler and language core. As a result, our image size has been reduced by 10% (from 66MB to 58MB) The VM has also improved in several areas: better async I/O support, socket handling, FFI ABI, Even being a short iteration, we have closed a massive amount of issues: around 600 issues and 700 pull requests. A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo100Chang…. While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 10 image was contributed by more than 80 people. Pharo is more than code. It is an exciting project involving a great community. We thank all the contributors to this release: Aaron Bieber, Ackerley Tng, Alban Benmouffek, Alejandra Cossio, Aless Hosry, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Arturo Zambrano, Asbathou Biyalou-Sama, Axel Marlard, Bastien Degardins, Ben Coman, Bernardo Contreras, Bernhard Pieber, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Christophe Demarey, Clotilde Toullec, Connor Skennerton, Cyril Ferlicot, Dave Mason, David Wickes, Denis Kudriashov, Eric Gade, Erik Stel, Esteban Lorenzano, Evelyn Cusi Lopez, Ezequiel R. Aguerre, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu, Jan Bliznicenko, Jaromir Matas, Kasper Ãsterbye, Kausthub Thekke Madathil, Konrad Hinsen, Kurt Kilpela, Luz Paz, Marco Rimoldi, Marcus Denker, MartÃn Dias, Massimo Nocentini, Max Leske, Maximilian-ignacio Willembrinck Santander, Miguel Campero, Milton Mamani Torres, Nahuel Palumbo, Norbert Hartl, Norm Green, Nour Djihan, Noury Bouraqadi, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Pierre Misse-Chanabier, Quentin Ducasse, Raffaello Giulietti, Rakshit, Renaud de Villemeur, Rob Sayers, Roland Bernard, Ronie Salgado, Santiago Bragagnolo, Sean DeNigris, Sebastian Jordan Montt, Soufyane Labsari, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Theo Rogliano, Thomas Dupriez, ThÃ©o Lanord, Torsten Bergmann, Vincent Blondeau. (If you contributed to Pharo 10 development in any way and we missed your name, please send us an email and we will add you). Enjoy! The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download (https://pharo.org/download) Learn Pharo: http://pharo.org/documentation (https://pharo.org/documentation)

6 6

Re: [ANN] Pharo 10 released!
by Serge Stinckwich April 6, 2022

April 6, 2022

You can look at the change, I have done here: https://github.com/KendrickOrg/kendrick/commit/1fe47c7cb4eebd1a676ffea186c2… Regards, On Wed, 6 Apr 2022 at 11:21, o lu <oluoluolu(a)gmail.com> wrote: > On 4/5/22 21:06, Serge Stinckwich wrote: > > Sorry, my fault ... forget to add a baseline for Pharo10. > > I'm learning: tell me how you did this. > > Again congratulations on all the work done for this new release! > > Regards, > > On Wed, 6 Apr 2022 at 08:42, Serge Stinckwich <serge.stinckwich(a)gmail.com> > wrote: > >> Dear all, >> >> congratulations on the new release ! Nice to see smaller iterations for >> the release. >> >> I try to load one of my packages with: >> >> Metacello new >> repository: 'github://KendrickOrg/kendrick'; >> baseline: 'Kendrick'; >> onWarningLog ; >> load >> >> >> Was loading without any issue on Pharo 9 and now in Pharo 10 there is an error: >> >> Error: Name not found: Kendrick >> >> Something changed in package loading? >> >> Regards, >> >> -- > Serge Stinckwic > âhâ > https://twitter.com/SergeStinckwich > â > > > -- Serge Stinckwic âhâ https://twitter.com/SergeStinckwich â

1 0

Re: [ANN] Pharo 10 released!
by o lu April 6, 2022

April 6, 2022

On 4/5/22 23:21, o lu wrote: (Sending again, sorry if you get it twice!) > On 4/5/22 21:06, Serge Stinckwich wrote: >> Sorry, my fault ... forget to add a baseline for Pharo10. > > I'm learning: tell me how you did this. > >> Again congratulations on all the work done for this new release! >> >> Regards, >> >> On Wed, 6 Apr 2022 at 08:42, Serge Stinckwich >> <serge.stinckwich(a)gmail.com> wrote: >> >> Dear all, >> >> congratulations on the new release ! Nice to see smaller >> iterations for the release. >> >> I try to load one of my packages with: >> >> Metacello new >> repository: 'github://KendrickOrg/kendrick'; >> baseline: 'Kendrick'; >> onWarningLog ; >> load >> >> Was loading without any issue on Pharo 9 and now in Pharo 10 there is an error: >> >> Error: Name not found: Kendrick >> >> Something changed in package loading? >> >> Regards, >> >> -- >> Serge Stinckwic >> âhâ >> https://twitter.com/SergeStinckwich >> >> â > >

1 0

This week (13/2022) on the Pharo Issue Tracker
by Marcus Denker April 1, 2022

April 1, 2022

We 18 merged PRs, closed 12 issues. Fixes ====== - Do a small wait after SDL window is created #11082 https://github.com/pharo-project/pharo/pull/11082 - Fix halo gesture - workaround #11067 https://github.com/pharo-project/pharo/pull/11067 - Reverting method rename refactoring double confirmation #11076 https://github.com/pharo-project/pharo/pull/11076 - fix DNU in VTermTestRunner #11072 https://github.com/pharo-project/pharo/pull/11072 - 11068-Lots-of-tests-failing-on-the-CI #11073 https://github.com/pharo-project/pharo/pull/11073 - Fixing broken tests from PR #11060 #11069 https://github.com/pharo-project/pharo/pull/11069 - Fixing shortcuts for Debugging, Reflective and Breakpoint commands #11059 https://github.com/pharo-project/pharo/pull/11059 - Fix screen scale factor base dpi #11056 https://github.com/pharo-project/pharo/pull/11056 - 10777 scope of refactorings do not work anymore #11060 https://github.com/pharo-project/pharo/pull/11060 - 11007 isPrime does not work for large numbers #11030 https://github.com/pharo-project/pharo/pull/11030 - [quickCleanup] fix random typo in a Calypso menu #11058 https://github.com/pharo-project/pharo/pull/11058 - Created accessor method for Interval>>stop #11055 https://github.com/pharo-project/pharo/pull/11055 Documentation ============ - Updating readme: setting bootstrap script architecture to 64 bits #11066 https://github.com/pharo-project/pharo/pull/11066 - [shortFix] add missing asBag in comment tests #11057 https://github.com/pharo-project/pharo/pull/11057 Release ======= - update pharo changelog to Pharo 10 #11081 https://github.com/pharo-project/pharo/pull/11081 - Fix iceberg version to 2.0.6 for release #11079 https://github.com/pharo-project/pharo/pull/11079 - use NewTools 0.7.0 and Spec 1.1.1 #11078 https://github.com/pharo-project/pharo/pull/11078 Cleanup ======= - Cleanup: protocol "dispatching-cleanup" -> "dispatching - cleanup" #11038 https://github.com/pharo-project/pharo/pull/11038 - Full sync from Zinc repository #10955 https://github.com/pharo-project/pharo/pull/10955

1 0

any ideas why we need to have Point >> bitShiftPoint: bits?
by stephane ducasse March 29, 2022

March 29, 2022

Point >> bitShiftPoint: bits x := x bitShift: bits. y := y bitShift: bits S

1 0

Re: [Esug-list] [PDFtalk] Porting to non-namespace Smalltalks
by stephane ducasse March 26, 2022

March 26, 2022

Hi guys > > I started to port Values to Pharo. > If you want to give an hand my current effort is here. > > https://github.com/Ducasse/PharoValues <https://github.com/Ducasse/PharoValues> > > should migrate license and other stuff too. > > S > >> On 1 Mar 2022, at 19:08, christian.haider(a)smalltalked-visuals.com <mailto:christian.haider@smalltalked-visuals.com> wrote: >> >> Hi all, >> >> PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. >> Now, there is interest from companies in a port to Squeak and VA Smalltalk. >> >> The project[3] has started and we are making good progress. >> The first step: porting the Values package. >> This is easy, because there are no namespace issues. >> >> The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. >> >> Then PDFtalk with all its components, except for the UI, can be ported. >> >> The porting approach is different to the traditional way of loading and fixing. >> The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. >> The approach is documented in [4]. >> >> I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. >> >> Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. >> >> I would like to invite Smalltalkers from all dialects to take part in this project. >> The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. >> Therefore, each port to one Smalltalk will help the port to other Smalltalks. >> >> Any takers? >> >> Happy hacking, >> Christian >> >> >> [1] https://wiki.pdftalk.de/doku.php?id=start <https://wiki.pdftalk.de/doku.php?id=start> >> [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone <https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone> >> [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout <https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout> >> [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> >> [5] https://github.com/PortingPDFtalk <https://github.com/PortingPDFtalk> >> [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog <https://wiki.pdftalk.de/doku.php?id=valuesportinglog>_______________________________________________ >> Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> >> To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org> > >

1 0

Default selection when compiling a method
by pmissech March 25, 2022

March 25, 2022

Hello, We have worked today with Iona on https://github.com/pharo-project/pharo/issues/11052. Basically the hierarchy is reversed by default, which we don't like. We proposed a PR to change the default behavior. The issue we want to share with you today is the following. You select a method that is installed in a class different from your current class in the Calyspo browser. You want to change it. Upon compiling your changes, Calypso asks for where the method should be installed. We are wondering whether we should have a default selection in the Class list. Two cases that we thought of: (1) When selecting a subclassResponsibility, We would like to pre select the current class to install the new method. (2) When selecting a random method from the hierarchy, we tend to think that the class in which the method is implemented should be selected by default. Â Â Â When working on your own projects, this makes sense to us. Â Â Â When navigating through other projects/core packages, it would make less sense. We tend to think that we should select the current class every time. (basically case (1)) But what do you think ? Have a nice day Pierre & Iona

1 0

This week (12/2022) on the Pharo Issue Tracker MD Marcus Denker
by Marcus Denker March 25, 2022

March 25, 2022

We merged 15 PRs and closed 14 issues this week. Fixes ===== - fix row background color loss when hovering a table with alternated color configured #11020 https://github.com/pharo-project/pharo/pull/11020 - Fix Cmd-t again #11022 https://github.com/pharo-project/pharo/pull/11022 - this change enables click + control, and click + alt in morphic #11032 https://github.com/pharo-project/pharo/pull/11032 - 11007 isPrime does not work for large numbers #11030 https://github.com/pharo-project/pharo/pull/11030 - Fix for specific failure of isPrime for certain squares introduced byâ¦ #11047 https://github.com/pharo-project/pharo/pull/11047 - use fixed spec version (for release) #11014 https://github.com/pharo-project/pharo/pull/11014 - Change UserInterrupt detection to use character codes rather than scaâ¦ #11004 https://github.com/pharo-project/pharo/pull/11004 Documentation ============= - ClassDefinitionPrinter-Comments #11005 https://github.com/pharo-project/pharo/pull/11005 Speed ===== - 11018 SmallInteger isPrime is inefficient #11043 https://github.com/pharo-project/pharo/pull/11043 Cleanup ======= - Renamed protocol name from accesing to accessing #10967 https://github.com/pharo-project/pharo/pull/10967 - Align a few categories in Zinc with the rest of system #11029 https://github.com/pharo-project/pharo/pull/11029 - Cleanup: protocol "activating" -> "activation" #11034 https://github.com/pharo-project/pharo/pull/11034 - Cleanup: protocol "activation hooks" -> "activation - hooks" #11036 https://github.com/pharo-project/pharo/pull/11036 - Cleanup: align protocols in UITheme #11040 https://github.com/pharo-project/pharo/pull/11040 - Cleanup waiting protocols in Monitor #11042 https://github.com/pharo-project/pharo/pull/11042 Pharo9 ====== - Backport Fix #11001: Stateful Traits: Adding One Corrupts Existing Instances #11016 https://github.com/pharo-project/pharo/pull/11016

1 0

Positions at lifeware :)
by stephane ducasse March 21, 2022

March 21, 2022

1 0

Extension Traits/Slots
by sean＠clipperadams.com March 19, 2022

March 19, 2022

Has this ever been considered? We can add methods from a package different than the host class and thereby avoid dirtying its package, but what if we could do the same for traits and slots?

2 1