May 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #305: fix-profiling-menu-entries
by ci-pharo-ci-jenkins2＠inria.fr May 20, 2020

May 20, 2020

There is a new Pharo build available! The status of the build #305 was: SUCCESS. The Pull Request #6380 was integrated: "fix-profiling-menu-entries" Pull request url: https://github.com/pharo-project/pharo/pull/6380 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #304: merge-spec2-0-6
by ci-pharo-ci-jenkins2＠inria.fr May 20, 2020

May 20, 2020

There is a new Pharo build available! The status of the build #304 was: FAILURE. The Pull Request #6324 was integrated: "merge-spec2-0-6" Pull request url: https://github.com/pharo-project/pharo/pull/6324 Issue Url: https://github.com/pharo-project/pharo/issues/merge Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #303: Fix Cairo bindings for PDF and SVG generation
by ci-pharo-ci-jenkins2＠inria.fr May 20, 2020

May 20, 2020

There is a new Pharo build available! The status of the build #303 was: FAILURE. The Pull Request #6376 was integrated: "Fix Cairo bindings for PDF and SVG generation" Pull request url: https://github.com/pharo-project/pharo/pull/6376 Issue Url: https://github.com/pharo-project/pharo/issues/6374 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #302: Removing slice and issue support
by ci-pharo-ci-jenkins2＠inria.fr May 19, 2020

May 19, 2020

There is a new Pharo build available! The status of the build #302 was: FAILURE. The Pull Request #6370 was integrated: "Removing slice and issue support" Pull request url: https://github.com/pharo-project/pharo/pull/6370 Issue Url: https://github.com/pharo-project/pharo/issues/removing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #301: unload-enlumineur-ui
by ci-pharo-ci-jenkins2＠inria.fr May 19, 2020

May 19, 2020

There is a new Pharo build available! The status of the build #301 was: FAILURE. The Pull Request #6364 was integrated: "unload-enlumineur-ui" Pull request url: https://github.com/pharo-project/pharo/pull/6364 Issue Url: https://github.com/pharo-project/pharo/issues/unload Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #300: FixCompilerSettings
by ci-pharo-ci-jenkins2＠inria.fr May 19, 2020

May 19, 2020

There is a new Pharo build available! The status of the build #300 was: FAILURE. The Pull Request #6358 was integrated: "FixCompilerSettings" Pull request url: https://github.com/pharo-project/pharo/pull/6358 Issue Url: https://github.com/pharo-project/pharo/issues/FixCompilerSettings Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Squeak and Pharo speed differences
by Shaping May 19, 2020

May 19, 2020

Hi all. Squeak 5.3: Time millisecondsToRun: [ 100000 factorial ] 6250 Pharo 8: Time millisecondsToRun: [ 100000 factorial ] 7736 Why the difference? Squeak 5.3 release notes describe arithmetic improvements. Nice. I crunch very big numbers, and these improvements therefore have value. Why would they not be included in OSVM (forked or not) and the basic class-set for both Squeak and Pharo? Playing with Squeak 5.3, Iâve noticed that the GUI is snappier. Browser ergonomics are better too (for me at least), but that can be fixed/tuned in either environ to suit the developer. (Still thatâs some work I prefer not to do.) Pharo GUIs are now generally slower, except for the Launcher, which is delightfully quick because it is written in Spec2. I presume that all Pharo GUIs will eventually (ETA?) be written in Spec2 and that Pharo will then be quick in all its GUIs. The obvious question is: Will Squeak be improving GUI look/behavior and speed with Spec2? If not, can I load Spec2 into Squeak so that I can do new GUI work there? Both Squeak and Pharo have slow text selection. Pick any word in any pane, and double click it to select it. When I do this, I sense a 75 to 100 ms latency between the end of the double click and the selection highlight appearing on the word. I thought Iâd entered a wormhole. So I did the same experiment in VW 8.3.2, VS Code, and Notepad, and all three showed undetectable latencies. This matters to me. Iâm trying to port from VW to Pharo or Squeak (for a really long time now), and canât push myself past the text-selection delay problem. Can text-selection speed be improved to the level of VWâs? Can someone sketch the algo used and/or point me to the right class/methods. The Squeak debugging experience step-to-step is much quicker. The latencies in Pharo after button- release are very long. I estimate 100 to 150 ms. Thatâs too long for me to work productively. I lose my mental thread with many of those delays, and have to restart the thought. Itâs a serious problem, caused mostly by acclimation to no detectable latency for many years (Dolphin and VW have quick GUIs). Is speeding up the Pharo debugger with Spec2 a priority? I canât think of a better GUI-related priority for Pharo. Not speed-related: - How can I load additional fonts into Squeak? Pharo does this with the font dialogâs Update button. - Where in the Squeak and Pharo images can I change mouse-selection behavior to be leading-edge? Some of the Squeak panes have this; others donât. I want leading-edge action in all panes, and wish the feature were in Preferences/Settings. Shaping

4 16

[ANN] Smalltalkhub Readonly Migration tuesday 8hs - server maintenance / migration
by Guillermo Polito May 18, 2020

May 18, 2020

Hi all, We wanted to announce that, as announced previously, Smalltalkhub is going read only from tomorrow, 8h central Europe time. This means the service could be down for a couple of hours until the sync of data is done. Keep tuned, Guille and Christophe in behalf of the RMoD team

1 0

Re: [Pharo-dev] [Vm-dev] Squeak and Pharo speed differences
by Ronie Salgado May 18, 2020

May 18, 2020

Hi Shaping, About the latency, it may be because of the default idle time. Try running the following: ProcessorScheduler idleTime: 1000 > By the release of Pharo 7 the idle time was increased to 50 ms in order to reduce the CPU usage on the cloud and reduce costs. If I remember correctly Ben Coman did a PR that changes the way the delays are scheduled in order to select the most appropriate time for sleeping, but since the PR was to close to a Pharo release, it was decided to not be included for safeness reasons. We should resurrect that change soon because the default latency is really bad. Best regards, Ronie El dom., 17 may. 2020 a las 7:03, Robert (<robert.withers(a)pm.me>) escribiÃ³: > > > Hi Shaping, I can't comment on parallelizing the VM. I was waiting to hear > from you regarding 'CapabilitiesLocal' and its ref-cap state transition > model. > On 5/16/20 11:29 PM, Shaping wrote: > > Hi Shaping, > > Hi Robert. (Weâll get back to the parallelizing any day nowâ¦) > > On 5/16/20 8:47 AM, Shaping wrote: > > Can you tell me about those efforts? I know the VM is one, maybe the > biggest. What else do Squeak folks work on? > > I also understand why the developers of the new Pharo preferences tree > did not like to invest the same effort in Squeak. What incentive would they > have? > > > > Make all features (GUIs/frameworks) loadable into a new, mostly empty > image. > > > > Andso, here we have the biggest challenge to doing such sharing. You say > all features should be loadable into either image. The issue is that Pharo > has driven forwards in creating new load formats, such as Tonel. I tried to > load up the Tonel format, but failed. > > > > Who oversees stuff like this? > > Specifically, why donât we now make Tonel avaibable on Squeak, with the > objective of equalizing access to source code, so that we can use one image > ultimatelyâa nice steady gradual drift toward one image, so that no one is > in too much pain at any one point in time. > > Why wasnât this done when Tonel was first created? The Pharo dev probably > didnât see it as good use of dev time. I kindly suggest that this > attitude change for all contributors to both Smalltalks. > > How long is the list of format-related code/frameworks that need to be > equalized, so that Squeak and Pharo can always load the same things? > > I couldn't get distracted from my core work. > > Sure, I feel the same. I imaging that most of us do. > > NO EFFORTS have been made to have Squeak able to load such formats, and > the Pharo folks have deprecated the existing Montecello load format, > > In my Pharo 9 I have a bit these bits: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfAida'; > > load. > > (Smalltalk at: #ConfigurationOfAida) load. > > > > Metacello new > > baseline:'Seaside3'; > > repository: 'github://SeasideSt/Seaside:master/repository'; > > load > > In Squeak I can now ensureRecentMetacello, which I was not able to before. > > Installer ensureRecentMetacello. > > Metacello new > baseline: 'MagicMouse'; > repository: 'filetree:///home/quotar/tribe/MagicMouse/packages'; > load > > However, I still choke on the Metacello #baseline:; #repository:. #load. > It prints to the Transcript > > gofer repository error: 'GoferRepositoryError: > UndefinedObject>>isAlphaNumeric'...ignoring > ...FAILED->BaselineOfMagicMouse > > I get a debugger on > MetacelloFetchingMCSpecLoader>>#retryingResolvePackageSpecReferences: > packageSpec gofer: gofer > > The Gofer is pointing to a > MCFileTreeRepository(filetree:///home/quotar/tribe/MagicMouse/packages) as > its only repo. The packageSpec is thus: > > spec > name: 'BaselineOfMagicMouse'; > repository: 'filetree:///home/quotar/tribe/MagicMouse/packages'. > > At one time I had found what caused the #isAlphaNumeric error (I think an > empty stream). The point is that I cannot load with Metacello in Squeak. > > Here is code I use in Squeak to load Cryptography and ParrotTalk and SSL > and Raven. This works in Squeak but not in Pharo. > > Installer ss > project: 'Cryptography'; install: 'ProCrypto-1-1-1'; > project: 'Cryptography'; install: 'ProCryptoTests-1-1-1'; > project: 'Cryptography'; install: 'CapabilitiesLocal'; > project: 'Oceanside'; install: 'ston-config-map'; > project: 'Cryptography'; install: 'SSLLoader; > project: 'Cryptography'; install: 'Raven'. > > Packages #1, #2, #4, and #5 are all Monticello configuration maps (.mcm), > thus unloadable in Pharo... > > > > *If there is genuine respect for the value of Squeak and Pharo on both > sides * > > Good question! We shall see. The feeling to me is a couple of stiff french > fingers being sent Squeak's way. There is probably a french word for that.. > > K, r > -- > > Kindly, > Robert > >

3 2

[Mm10s] 2020-05-18
by Esteban Lorenzano May 18, 2020

May 18, 2020

Short list today ;) ### Last week: * [NewTools-Playground] polishing details and get it ready to test internally (which now is the case :P) * Documenting transmissions sub-framework. * Spent a lot of time preparing integration of Spec2 0.6 into P9. ### This week (starting 2020-05-18): - Finish 0.6 merge. - Start working with NewTools-Inspector - verify some errors in UFFI - Gtk backend: verify some problems with low-level events

2 1