- Pharo-users - lists.pharo.org

[ANN] Pharo Consortium New Bronze Member: SRA
by Marcus Denker May 7, 2022

May 7, 2022

The Pharo Consortium is very happy to announce that SRA has joined the Consortium as a Bronze Member. About - SRA: https://www.sra.co.jp/en/ - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association https://association.pharo.org

2 1

[ANN] Stargate-Consul v4.1.0 [v4.1.0] released!
by Buenos Aires Smalltalk May 4, 2022

May 4, 2022

1 0

[ANN] Stargate v8.2.0 [v8.2.0] released!
by Buenos Aires Smalltalk May 4, 2022

May 4, 2022

1 0

[ANN] Launchpad v4.4.0 [v4.4.0] released!
by Buenos Aires Smalltalk May 4, 2022

May 4, 2022

1 0

[ANN] Willow-Playground v9.1.2 [v9.1.2] released!
by Buenos Aires Smalltalk May 4, 2022

May 4, 2022

1 0

[ANN] Pharo Launcher 3.0.1 released!
by Christophe Demarey May 3, 2022

May 3, 2022

Hi all, Pharo Launcher 3.0.1 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. It fixes some issues reported on Pharo Launcher 3.0. Here is the changelog: Pharo Launcher v3.0.1 Bug fixes: #554 <https://github.com/pharo-project/pharo-launcher/issues/554> UI does not show up on Windows #551 <https://github.com/pharo-project/pharo-launcher/issues/551> Show folder button is broken in Windows 10 #550 <https://github.com/pharo-project/pharo-launcher/issues/550> About Box shows "untitled Window" #549 <https://github.com/pharo-project/pharo-launcher/issues/549> Better display of download error messages. #358 <https://github.com/pharo-project/pharo-launcher/issues/358> Restore proxy authentication settings. Regards, The Pharo team.

3 5

Pharo is unresponsive after forcing quit
by Stewart MacLean May 2, 2022

May 2, 2022

Hi, [Pharo 10 on Mac Monterey] Due to the multi-process nature of Bonjour that I'm attempting to interface to, I am crashing the system ALOT as it disappears down a black hole and I try to figure out the cause. However, I've noticed that most of the time when I restart Pharo it is unresponsive to clicks and I have to relaunch Pharo AGAIN! Argh....! The mouse moves but no one is at home. Right click brings up menus, but they don't respond. As I move the mouse, list items are highlighted. As this is a completely new OS process, I'm wondering what is causing this behaviour? Has anyone else experienced this, or have an explanation? Cheers, Stewart

5 7

Pharo Enterprise book HTML chapter links
by Sven Van Caekenberghe April 30, 2022

April 30, 2022

Hi, All the Chapter Topics links on https://books.pharo.org/enterprise-pharo/ (bottom left side) are broken. Is it still possible to link to individual chapters ? Can someone have a look, it would be a shame to let this bit rot. Thx, Sven PS: Looking at the other books it seems HTML reading is completely gone, what a shame. This used to work fine.

1 0

Loading from a git repository with Metacello on a running seaside image
by Emilio Oca April 30, 2022

April 30, 2022

Hi List I need some help with Metacello, and may be git too I would like to be able to, in a running headless image, load the last commit of a git repo Something like Metacello new baseline:'MyProject'; repository: 'github://myUser/MyProject:main/myProject'; load. works just once and may open some dialogs Something like this [ [ Metacello new baseline:'MyProject'; repository: 'github://myUser/MyProject:main/myProject'; onConflictUseIncoming; load. ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. Avoids the dialogs and alerts but the code is still not updated. My intention is to be able to 'refresh' a running seaside image with its latest development version from a git repo (avoiding to personally reach the server and rebuild the docker image) What am I missing? Best Emilio

4 10

A question about #beginsWith: and #endsWith:
by Richard O'Keefe April 29, 2022

April 29, 2022

I've just tracked down a nasty little problem porting some code to Pharo. As a result, I have added to the comments in my own versions of these methods. beginsWith: aSequence "Answer true if aSequence is a prefix of the receiver. This makes sense for all sequences. There is a compatibility issue concerning 'abc' beginsWith: '' + VisualWorks, Dolphin, astc, GNU ST (where the method is called #startsWith:) and VisualAge (where the method is called #wbBeginsWith:) agree than EVERY sequence begins with an empty prefix. - Squeak and Pharo agree that NO sequence begins with an empty sequence. # ST/X chooses compatibility with Squeak, heaving a big unhappy sigh, and adds #startsWith: to have something sensible to use. Now ST/X *thinks* it is compatible with VW, though it isn't, so I wonder if this was a bug that VW fixed and Squeak didn't? astc goes with the majority here. This is also compatible with Haskell, ML, and with StartsWith in C# and startsWith in Java." ^self beginsWith: aSequence ignoringCase: false endsWith: aSequence "Answer true if aSequence is a suffix of the receiver. This makes sense for all sequences. There is a compatibility issue concerning 'abc' endsWith: ''. + VisualWorks, Dolphin, astc, GNU ST, and VisualAge (where the method is called #wbEndsWith:) agree that EVERY sequence ends with an empty suffix. - Squeak and Pharo agree that NO sequence ends with an empty suffix. # ST/X chooses compatibility with the majority, apparently unaware that this makes #beginsWith: and #endsWith: inconsistent. astc goes with the majority here. This is also compatible with Haskell, ML, C#, and Java." ^self endsWith: aSequence ignoringCase: false Does anyone have any idea - why Squeak and Pharo are the odd ones out? - why anyone thought making #beginsWith: and #endsWith:, um, "quirky" was a good idea (it's pretty standard in books on the theory of strings to define "x is a prefix of y iff there is a z such that y = x concatenated with z") I was about to try to file a bug report for the first time, then realised that maybe other people don't think this IS a bug.

6 14