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

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

by Marcus Denker

# This week (34/2023) on the Pharo Issue Tracker Due to Holiday season not much happend, but both the Refactorig and RPackage improvements continued to see some actions. # Refactoring Engine - Fix: enable push down method for concrete classes #14500 https://github.com/pharo-project/pharo/pull/14500 - Cleanup: rename primitive execute #14506 https://github.com/pharo-project/pharo/pull/14506 # RPackage - Packages: Introduce new API in MCOrganizationDefinition #14509 https://github.com/pharo-project/pharo/pull/14509 - RPackage: Simplify actions of method modifications #14510 https://github.com/pharo-project/pharo/pull/14510 - RPackage: Simplify class import #14507 https://github.com/pharo-project/pharo/pull/14507 - RPackage: Clean bootstrap initialization #14462 https://github.com/pharo-project/pharo/pull/14462 - RPackage: Fix some flacky tests #14487 https://github.com/pharo-project/pharo/pull/14487 - Save real classes in RPackage #14501 https://github.com/pharo-project/pharo/pull/14501 # Cleanup - Simplify FixedFaceFont by removing âdisplaySelectorâ #14508 https://github.com/pharo-project/pharo/pull/14508 - Removing references to text editor #14496 https://github.com/pharo-project/pharo/pull/14496

Aug. 25, 2023

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

by Marcus Denker

# Pharo 11 - [P11] Adding a nice error for loadSymbol #14452 https://github.com/pharo-project/pharo/pull/14452 # Features - Add #enumerationsDo: and #enumerationsOfSize: #13952 https://github.com/pharo-project/pharo/pull/13952 # Fixes - Fix BrowseIt for Classes https://github.com/pharo-project/pharo/pull/14481 https://github.com/pharo-project/pharo/pull/14482 https://github.com/pharo-spec/Spec/pull/1439 https://github.com/pharo-spec/Spec/pull/1438 - Remove events for the existing ChangesLog when installing NoChangesLog #14477 https://github.com/pharo-project/pharo/pull/14477 - Fix bug in #rubParagraph:bounds:color: in PluggableCanvas #14479 https://github.com/pharo-project/pharo/pull/14479 - Make methods in the UITheme hierarchy take the display scale factor into account #14464 https://github.com/pharo-project/pharo/pull/14464 # RPackage Cleanup - RPackage: Fix failing tests #14494 https://github.com/pharo-project/pharo/pull/14494 - RPackage: Make Gofer cleanup use Package API #14488 https://github.com/pharo-project/pharo/pull/14488 - Use new API of ClassFactoryForTestCase #1432 https://github.com/pharo-spec/Spec/pull/1432 # Refactoring Engine - Refactoring: Use less categories in RBMoveClassTransformation #14492 https://github.com/pharo-project/pharo/pull/14492 - Fix: make class abstract #14469 https://github.com/pharo-project/pharo/pull/14469 - Make Remove instance variables works well on a list using a new compoâ¦ #14475 https://github.com/pharo-project/pharo/pull/14475 - Creating less blocks instead of using simple temporaries. #14478 https://github.com/pharo-project/pharo/pull/14478 - Cleanup: rename all conditions to preconditions #14484 https://github.com/pharo-project/pharo/pull/14484 - Refactor: move-to-class-side uses composite refactoring #14489 https://github.com/pharo-project/pharo/pull/14489 - Refactorings: Remove category environment #14493 https://github.com/pharo-project/pharo/pull/14493

Aug. 18, 2023

Embedding FAUST in Pharo - meet the FAUST team in Lyon

by Sebastian Jordan Montano

Here is a message from Domenico: I tried to sent an email about this to the Pharo mailing list, but I am not sure it was forwarded. so: as ESUG in Lyon this year, I was chatting with some people of the FAUST (https://faust.grame.fr/) team at GRAME (https://www.grame.fr/) about my live coding with Pharo, the music with Pharo and if we could find a way to embed the Faust compiler in Pharo (https://faustdoc.grame.fr/manual/embedding/) one of the guys of the team would like to meet me during ESUG most probably with the director scientifiche Yann Orlarey. I told him that maybe the best thing is to join us for our usual beer-after-conference, maybe on Tuesday or on Thursday. if anybody wants to participate at the informal meeting, please express a preference about the day and time :). last but not least, GRAME is now part of INRIA,( https://team.inria.fr/emeraude/) looking forward for your reply, Pharo + FAUST could be a really cool thing. p.s. they would like to listen at to my talk on Monday morning but I guess this is a question for the esug-mailing list

Aug. 17, 2023

AST vs. Bytecode Interpreters

by Steffen MÃ¤rcker

Hi folks! Today I found this interesting paper via Stefan Marr on the performance differences of ast vs. bytecode interpreters (for meta compilation): https://stefan-marr.de/downloads/oopsla23-larose-et-al-ast-vs-bytecode-inte… It was a really interesting read. I do not remember seeing this on the list. If it was, please apologize double posting. Cheers! Steffen

Aug. 15, 2023

Re: Personal wiki / information manager

by Siemen Baader

On Fri, Jul 14, 2023 at 4:21â¯AM <sean(a)clipperadams.com> wrote: > TheProjectProject <https://github.com/seandenigris/The-Project-Project> > is the GTD component of my Dynabook project > <https://github.com/seandenigris/Dynabook>. Behind it is about 20 years > of work incorporating ideas from countless productivity disciplines - GTD, > Steven Covey, Landmark Educationâs Mission Control spin off, etcâ¦ > Very interesting, I'll check it out! And yes, I agree - it is very helpful to be able to extend and also automate a productivity system with any concept from one's life. Very cool that you have extended it with Corey's 7 habits. I have meeting announcements that I'd like to automate across email and SoMe channels, and recipes, meal planning, online grocery ordering and bulk cooking. The Dynabook approach sort of legitimates the approach of evolving such a system yourself as empowering literacy, rather than using a patchwork of specialized end user applications. I get the impression that Lisp folks do have an ASCII inspired Dynabook universe with Emacs and OrgMode. We could ask Nicolas Petton.. I found his Pharo projects to be extremely creative and well-engineered. Now he is using GTD & OrgMode and maintaining Emacs. [3] My own Dynabook system has a Pharo backend and internal Pharo DSL and AJAX web app frontend based on Iliad. The latter to allow collaboration with non-pharo end users on certain projects. I'm interested in adding instrumental interaction [1] to the web frontend to provide context appropriate editing tools in a feasible way, along with the context appropriate views HTML gives me quite nicely (similar to the inspectors in the GToolkit philosophy). A big project and certainly more to talk about... Do you have a mobile workflow too? I use mobile a lot - for now with OrgMode and the beOrg mobile app. I also have a wearable computer with a Raspberry Pi, Vufine [2] and Twiddler one hand keyboard which has some advantages over mobile because I can type faster and maintain a view of the world through the HUD. The Twiddler is quite efficient for text/emacs-style editing and emacs runs quite well on the Pi, so I'm still interested in some sort of OrgMode compatibility to remain pragmatic & productive on these journeys. Sorry for my late response BTW, summer time... I really appreciate TheProjectProject and the thoughts behind it. cheers Siemen 1: https://www.lri.fr/~mbl/INSTR/eintroduction.html 2: https://www.theverge.com/circuitbreaker/2017/7/27/16035508/diy-wearable-com… 3: https://emacs.cafe/emacs/orgmode/gtd/2017/06/30/orgmode-gtd.html

Aug. 12, 2023

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

by Marcus Denker

# Pharo 11 - [P11] Traits has to install method when is generated code #14155 https://github.com/pharo-project/pharo/pull/14155 - [P11] Update Spec #14446 https://github.com/pharo-project/pharo/pull/14446 - 14141-BlockClosureisClean-regression-from-Pharo-10-to-11 #14448 https://github.com/pharo-project/pharo/pull/14448 - [backport] SpMorphicBackendForTest>>#doubleClickFirstRowAndColumn: #1431 https://github.com/pharo-spec/Spec/pull/1431 - Backport display scale factor improvements to Pharo 11 #1429 https://github.com/pharo-spec/Spec/pull/1429 # Fixes - Extend Behavior>>handleFailingBasicNew: #14196 https://github.com/pharo-project/pharo/pull/14196 - Change #destinationPath in ThemeIcons to use the local directory instead of the working directory #14450 https://github.com/pharo-project/pharo/pull/14450 - Improve load symbol error #14453 https://github.com/pharo-project/pharo/pull/14453 - Kernel: Unify method addition #14467 https://github.com/pharo-project/pharo/pull/14467 - Spec Little fixes on tests #1434 https://github.com/pharo-spec/Spec/pull/1434 # UI Scaling - Make methods in classes in the category âCalypso-Browser-UIâ take the display scale factor into account #14457 https://github.com/pharo-project/pharo/pull/14457 - Make methods in classes in the category âCalypso-Browser-Toolbarâ take the display scale factor into account #14456 https://github.com/pharo-project/pharo/pull/14456 - Make methods in classes in the category âCalypso-Browser-Tableâ take the display scale factor into account #14458 https://github.com/pharo-project/pharo/pull/14458 - Make #inspectionColors in UITheme take the display scale factor into account #576 https://github.com/pharo-spec/NewTools/pull/576 - Make #defaultExtent and #preferredExtent in playground presenters take the display scale factor into account #577 https://github.com/pharo-spec/NewTools/pull/577 - Make methods in SpMorphicButtonBarAdapter take the display scale factor into account #1436 https://github.com/pharo-spec/Spec/pull/1436 # Refactoring Engine - Ressurrect remove method refactoring #14470 https://github.com/pharo-project/pharo/pull/14470 - add class comments + tests to rbnamespace to show how selection is acâ¦ #14444 https://github.com/pharo-project/pharo/pull/14444 - Refactor: add method refactoring #14445 https://github.com/pharo-project/pharo/pull/14445 # RPackage Cleanup - Use classes in the class mapping of RPackageOrganizer #14391 https://github.com/pharo-project/pharo/pull/14391 - RPackage: Cleanings in tag #14447 https://github.com/pharo-project/pharo/pull/14447 - RPackage: Use real classes for extension caches #14454 https://github.com/pharo-project/pharo/pull/14454 - RPackage: Clean package demotion and tag promotion #14463 https://github.com/pharo-project/pharo/pull/14463 - RPackage: Improve coherence of names in RPackageTraitTest #14465 https://github.com/pharo-project/pharo/pull/14465 - RPackage: Clean some tests #14466 https://github.com/pharo-project/pharo/pull/14466 - Do not use RPackage organizer #569 https://github.com/pharo-spec/NewTools/pull/569 # Git / Iceberg - Do not use RPackage organizer #1719 https://github.com/pharo-vcs/iceberg/pull/1719 - Prevent the browsing of a removed element #1720 https://github.com/pharo-vcs/iceberg/pull/1720

Aug. 11, 2023

Re: Pharo in Docker.

by Esteban Lorenzano

Aug. 9, 2023

Re: Pharo in Docker.

by Guillermo Polito

Hi @Philippe, this is too few info to help, but maybe you can try the following: - are you sure the image inside the container and outside are the same version? => what if you use the same version outside the docker file? - the issue happens because of a deprecation exception, what if you disable them through the settings (there is a programmatic way to do it)? G > El 1 jul. 2023, a las 09:28, pvdh(a)pt.lu escribiÃ³: > > Hello, > > I am trying to run TinyBlog and Pharo in a Docker container. It run, but it crashes after a while with the following log: > > pva@dd8:~/docker/PharoTinyBlogDocker$ docker logs --tail 1000 b5172118c19f > ZnZincServerAdaptor > DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MAContainerComponent>>#isReadonly called from TBSMagritteFormRenderer>>#renderElement: has been deprecated. Use #isReadOnly instead. > DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MADescriptionComponent>>#isReadonly called from TBSMagritteCheckboxComponent>>#renderEditorOn: has been deprecated. Use #isReadOnly instead. > SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or expression expected' > ========================================================= > 1: `@receiver readonly: > _^_ > SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or expression expected' > ========================================================= > 1: `@receiver readonly: > _^_ > ZnZincServerAdaptor > I have tried to fix the problem in a regular image and it does not behave the same. > > Is there a way to debug graphically the Pharo located in the docker file ? I did not find any resources on the net concerning this kind of configuration. > > Thanks in advance for your help, > > Philippe Vanderheyden > > > > > > > -- > Cordialement, > Philippe > > Philippe Vanderheyden > Rue Maria Teresa, 15 > L-8448 Steinfort > T: 77 07 66 > G: 621 365 901 > <pvdh.vcf>

Aug. 9, 2023

This week (29-31/2023) on the Pharo Issue Tracker

by Marcus Denker

# This week (29-31/2023) on the Pharo Issue Tracker This is one log for three weeks (29-31) # Pharo 11 - backport Pharo11: Fix doubleClick on tab and on text selection. #14287 https://github.com/pharo-project/pharo/pull/14287 - Backport fixed tests #14409 https://github.com/pharo-project/pharo/pull/14409 - Backport fix GitHub rate limit #14411 https://github.com/pharo-project/pharo/pull/14411 - Backport display scale factor improvements to Pharo 11 #14351 https://github.com/pharo-project/pharo/pull/14351 - Backport scale 2.0 icons support to Pharo 11 #14352 https://github.com/pharo-project/pharo/pull/14352 # Features - Added coverage highlighting in DrTest #14379 https://github.com/pharo-project/pharo/pull/14379 - Push tag API in the class builder #14394 https://github.com/pharo-project/pharo/pull/14394 # Fixes - Changed finder behavior to not depend on copies #14163 https://github.com/pharo-project/pharo/pull/14163 - rapid click on two different items in a list gets interpreted as a double-click on the first item #14346 https://github.com/pharo-project/pharo/pull/14346 - Hermes: HEMethod needs to handle Protocol now instead of String #14386 https://github.com/pharo-project/pharo/pull/14386 - Fix bug of method returning a text as source code #14375 https://github.com/pharo-project/pharo/pull/14375 - Iterate over a copy of the actionMap in Object>>removeActionsSatisfying: (fixes #14317) #14325 https://github.com/pharo-project/pharo/pull/14325 - Class are created with the wrong environment #14329 https://github.com/pharo-project/pharo/pull/14329 - Ensure copied references in filesystem are resolved before copy #14341 https://github.com/pharo-project/pharo/pull/14341 - safer UUID comparison #14344 https://github.com/pharo-project/pharo/pull/14344 - safer morph access in NECMenuMorph>>#mouseDown: #14356 https://github.com/pharo-project/pharo/pull/14356 - [P12] Traits has to install method when is generated code #14156 https://github.com/pharo-project/pharo/pull/14156 - Replaced the random generator from Pharo. #14230 https://github.com/pharo-project/pharo/pull/14230 - Enhance roassal with version v1.02 #14373 https://github.com/pharo-project/pharo/pull/14373 - optionInlineNone suppresses #optionInlineX at CompilationContext level (fixes #14323) #14397 https://github.com/pharo-project/pharo/pull/14397 # RPackage Cleanup - Reduce usage of RPackage organizer #14370 https://github.com/pharo-project/pharo/pull/14370 - Do not rename category through announcements #14332 https://github.com/pharo-project/pharo/pull/14332 - Improve CompiledMethod>>#isExtension #14295 https://github.com/pharo-project/pharo/pull/14295 - Remove brittle method in RPackage #14292 https://github.com/pharo-project/pharo/pull/14292 - Use better package API in Monticello #14306 https://github.com/pharo-project/pharo/pull/14306 - Update package API of slot tests #14311 https://github.com/pharo-project/pharo/pull/14311 - Improve package cleaning API #14312 https://github.com/pharo-project/pharo/pull/14312 - Do not use deprecated API to create the default package #14316 https://github.com/pharo-project/pharo/pull/14316 - Improve package API used by Calypso #14321 https://github.com/pharo-project/pharo/pull/14321 - Make sure packages created with protocols are announced #14320 https://github.com/pharo-project/pharo/pull/14320 - Improve coherence of RPackage tests #14333 https://github.com/pharo-project/pharo/pull/14333 - Deprecate ensureExistAndRegisterPackageNamed: #14337 https://github.com/pharo-project/pharo/pull/14337 - SImplify class addition in RPackage #14347 https://github.com/pharo-project/pharo/pull/14347 - Deprectaed #definedClassesDo: #14350 https://github.com/pharo-project/pharo/pull/14350/files - Simplify class removal in packages #14359 https://github.com/pharo-project/pharo/pull/14359 - Simplify some classes management in RPackage #14358 https://github.com/pharo-project/pharo/pull/14358 - Do not remove classes from packages using the name #14363 https://github.com/pharo-project/pharo/pull/14363 - Clean method removal of RPackage #14360 https://github.com/pharo-project/pharo/pull/14360 - Forbid to have an extension method in the package owning the class #14354 https://github.com/pharo-project/pharo/pull/14354 - Speed up in package management #14366 https://github.com/pharo-project/pharo/pull/14366 - Do not remove classes through announcement #14388 https://github.com/pharo-project/pharo/pull/14388 - Simplify API of RPackage #14377 https://github.com/pharo-project/pharo/pull/14377 - Do not use global environment in RPackage #14368 https://github.com/pharo-project/pharo/pull/14368 - Simplify class addition assuming classes are created empty #14364 https://github.com/pharo-project/pharo/pull/14364 - Fix remaining announcement subscribtion #14405 https://github.com/pharo-project/pharo/pull/14405 - Package: React to class renaming without announcement #14407 https://github.com/pharo-project/pharo/pull/14407 - Use real classes in #classDefinedSelectors #14410 https://github.com/pharo-project/pharo/pull/14410 - RPackage:â¯Save package defined selectors with class instance #14416 https://github.com/pharo-project/pharo/pull/14416 - Use PackageTagAdded instead of CategoryAdded #14424 https://github.com/pharo-project/pharo/pull/14424 - Package: Remove methods without announcement #14420 https://github.com/pharo-project/pharo/pull/14420 - Package: Save extension selectors under real classes #14419 https://github.com/pharo-project/pharo/pull/14419 - RPackageTag should store real classes #14434 https://github.com/pharo-project/pharo/pull/14434 - RPackage: Factorize import code #14436 https://github.com/pharo-project/pharo/pull/14436 - RPackage: Simplify some code in RPackageOrganizer #14437 https://github.com/pharo-project/pharo/pull/14437 - RPackage: Improve creation of package during demotion to tag #14440 https://github.com/pharo-project/pharo/pull/14440 # Categories / Protocols - Fix bug with reset protocol of Calypso #14376 https://github.com/pharo-project/pharo/pull/14376 - Remove usage of categories in Fuel #14315 https://github.com/pharo-project/pharo/pull/14315 - Do not remove categories through announcements #14307 https://github.com/pharo-project/pharo/pull/14307 - Adapt check in RBAddMethodChange>>protocols: now that the argument may be a first-class Protocol (fixes #14324) #14327 https://github.com/pharo-project/pharo/pull/14327 - Use "protocol" vocabulary in MCTestCase #14322 https://github.com/pharo-project/pharo/pull/14322 - TestRunner should not rely on category announcements #14430 https://github.com/pharo-project/pharo/pull/14430 - Deprecate CategoryRemoved and CategoryRenamed #14438 https://github.com/pharo-project/pharo/pull/14438 # Epicea Souce Logging - Epicea:â¯Migrate category addition and removal to package tag API #14427 https://github.com/pharo-project/pharo/pull/14427 - Disable Epicea in tests #14017 https://github.com/pharo-project/pharo/pull/14017 - Introduce Class>>packageName and simplify Epicea #14408 https://github.com/pharo-project/pharo/pull/14408 - Epicea: Finish refactoring about packages and tags in Epicea #14428 https://github.com/pharo-project/pharo/pull/14428 # Refactoring Engine - Rename generateCompositeChangesFor: to generateChangesFor: #14304 https://github.com/pharo-project/pharo/pull/14304 - Cleanup transformation/refactoring hierarchy #14349 https://github.com/pharo-project/pharo/pull/14349 - Removing the use options in transformation. All test green #14382 https://github.com/pharo-project/pharo/pull/14382 - Enh/extract method transformation #14396 https://github.com/pharo-project/pharo/pull/14396 - Fixing shared variable remove #14402 https://github.com/pharo-project/pharo/pull/14402 - Fix RBCondition test #14413 https://github.com/pharo-project/pharo/pull/14413 - fixing deprecancies introduced by miss refactoring #14412 https://github.com/pharo-project/pharo/pull/14412 - Refactor: unify refactoring and transformation execution api #14374 https://github.com/pharo-project/pharo/pull/14374 - [Refactor] unified refactoring/transformation execution API #14432 https://github.com/pharo-project/pharo/pull/14432 # Tests - Improve flacky test #14425 https://github.com/pharo-project/pharo/pull/14425 - Remove the need of ClassFactoryWithOrganization #14393 https://github.com/pharo-project/pharo/pull/14393 - Make ClassFactoryForTestCase follow changes on class definition #14398 https://github.com/pharo-project/pharo/pull/14398 - Fix fuel tests #14392 https://github.com/pharo-project/pharo/pull/14392 # Simplifications - Improve ClassDescription API of package tags #14342 https://github.com/pharo-project/pharo/pull/14342 - Simplify class builder environment management #14330 https://github.com/pharo-project/pharo/pull/14330 - Use ClassFactoryForTestCase instead of FLClassFactoryForTestCase #14404 https://github.com/pharo-project/pharo/pull/14404 # Cleanups - remove rootsOfTheWorld that was buggy and unused. #14442 https://github.com/pharo-project/pharo/pull/14442 - Small cleanups in Announcement package #14297 https://github.com/pharo-project/pharo/pull/14297 - Replace 'controling' protocol with 'controlling' #14313 https://github.com/pharo-project/pharo/pull/14313 - Fix protocols of methods in extension of their own package #14357 https://github.com/pharo-project/pharo/pull/14357 - Remove unused parameter #14389 https://github.com/pharo-project/pharo/pull/14389 # Documentation - Update regex doc #14328 https://github.com/pharo-project/pharo/pull/14328 - Fix regex doc #14331 https://github.com/pharo-project/pharo/pull/14331

Aug. 7, 2023

Re: How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by varvello＠yahoo.com

Guillermo Polito wrote: > Pharo8 is pretty old :) Hi Gulliermo, Have you any stats on what are the most used Pharo version? > The best I can propose is that you try compiling the VM without the JIT compiler. > That will not give you optimum performances, but acceptable ones compared to Rosetta. > > Iâd suggest you try to compile using the branch pharo-9. Thatâs probably the oldest branch that is easy to build using cmake. > > If the pharo-9 branch does not work for your image, then maybe you should check the branches (see the branches v8.x.x). > > For installation/build instructions, please follow the readme instructions. If you find any issues, tell us, maybe there are cheap workarounds or fixes :). Thank you for your hints. I try to move the codebase to Pharo9, if it is too cumbersome then I try to compile the VM without JIT. Cheers Davide > Hope that helps, > Guille > > > El 6 ago. 2023, a las 22:07, stephane ducasse [stephane.ducasse@inria.fr](mailto:stephane.ducasse@inria.fr) escribiÃ³: > > > > > On 4 Aug 2023, at 20:24, Davide Varvello via Pharo-users [pharo-users@lists.pharo.org](mailto:pharo-users@lists.pharo.org) wrote: > > > > > > Hi Guys, > > > I want to use my old Pharo 8 image on an Apple Silicon (ARM64). I downloaded the stable VM for apple silicon http://files.pharo.org/get-files/110/pharo-vm-Darwin- <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>arm64 <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>-stable.zip <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip> but it isn't working with my pharo8 image. > > > > > > My old VM is working, of course, but I suppose it's because of Rosetta... and the performance is not optimal. > > > > > > Any other solution? > > > > I do not think that we have a solution. Iâm sorry but we decided that we cannot garantee that old Pharo version can run on Apple Silicon > > just because of engineering effort. > > With Pharo we are always trying not to trade the past for the future but this is difficult. > > > > S.

Aug. 7, 2023