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

[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

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

[Davide Varvello via Pharo-users]

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.duca...@inria.fr](mailto:stephane.duca...@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- 
> > > 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.

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

[Davide Varvello via Pharo-users]

Hi Steph,

I see, I hoped as Pharo 8 and M1 were born in 2020 that Pharo8 was supported

Davide