- Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #27: 22736-Clean-PharoWelcomePage
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #27 was: SUCCESS. The Pull Request #2047 was integrated: "22736-Clean-PharoWelcomePage" Pull request url: https://github.com/pharo-project/pharo/pull/2047 Issue Url: https://pharo.fogbugz.com/f/cases/22736 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Playground "remote publish" feedback from discord
by Ben Coman Dec. 11, 2018

Dec. 11, 2018

On discord a user provided some feedback... when you post anything to ws.stfx.eu - e.g. here: http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. However, there is no class called "ZnWorkspace" in Pharo 6.1 so this should probably be updated. "Remote publish" button is located fairly prominently in the top right corner of Pharo Playground window so Pharo beginners will probably see it fairly soon after they start experimenting and try clicking on it. The text should be updated so the instructions actually work. Also the footer of the page says copyright is 2013, and it would look better to newcomers if the copyright date was more recent. ---------- cheers -ben

2 6

Pharo FIleSystem Compatibility with Gemstone's FileSystemGs
by Reg Krock Dec. 11, 2018

Dec. 11, 2018

Hi, I am working on making changes to FileSystemGs to make it work in Gemstone. Who is or the the persons to talk to about changes on the Pharo side. Areas of exploration to date have been: Replacement of File with GsFile - in Gemstone we want to use the native file class. Introduction of a FileMode class hierarchy to replace the passing of they symbols #read and #write. Added the proof of concept of FileMode with subclasses to be passed instead of #write and #read. The classes which have been introduced are: FileMode FileAppendMode FileAppendAndReadMode FileAppendAndReadBinaryMode FileAppendBinaryMode FileReadMode FileReadBinaryMode FileReadWriteMode FileReadWriteMode FileReadWriteBinaryMode FileReadWriteTruncatedMode FileReadWriteTruncatedBinaryMode FileWriteMode FileWriteBinaryMode These classes return the appropriate mode string, (ex: âw+â) and know if the file is writable.Example of change - the text in blue shows the change. Exiting format: (filesystem open: aFileReference path writable: #write) Proposed format: (filesystem open: aFileReference path writable: self store readWriteTruncatedMode) The #readWriteTruncatedMode method would return an instance of FileReadWriteTruncatedMode If a form of this proposal were to be adopted, then the appropriate methods should be renamed to have mode. As an example, #open:writeable: would become #open:mode: Thanks for your help. Reg

1 0

[Pharo 7.0] Build #26: 22741 Cleanups for SystemVersionTest (lint)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 11, 2018

Dec. 11, 2018

There is a new Pharo build available! The status of the build #26 was: FAILURE. The Pull Request #2050 was integrated: "22741 Cleanups for SystemVersionTest (lint)" Pull request url: https://github.com/pharo-project/pharo/pull/2050 Issue Url: https://pharo.fogbugz.com/f/cases/22741 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Tonel>>sourceDir
by Ben Coman Dec. 11, 2018

Dec. 11, 2018

For Exercism we are using Tonel in Pharo 6.1. We are getting an error "Instance of TonelWriter did not understand #sourceDir:" but the same code works fine on Pharo 7. The 6.1 image had been updated to latest Iceberg per https://github.com/pharo-vcs/iceberg#for-pharo-61, so I used ICeberg to updated to latest "master" of pharo-vcs/tonel but no avail. In Pharo 7 I see TonelWriter>>sourceDir in protocol "accessing" but if I search for "sourceDir" in the pharo-vcs/tonel repo it doesn't find it... https://github.com/pharo-vcs/tonel/search?q=sourcedir&unscoped_q=sourcedir I'm having trouble understanding where the #sourceDir method comes from in Pharo 7. Which repo/branch can I load that from into another system? cheers -ben

4 7

[Pharo 7.0] Build #25: 22735-ZipArchive-classisZipArchive-is-broken-in-P7
by ci-pharo-ci-jenkins2＠inria.fr Dec. 10, 2018

Dec. 10, 2018

There is a new Pharo build available! The status of the build #25 was: SUCCESS. The Pull Request #2046 was integrated: "22735-ZipArchive-classisZipArchive-is-broken-in-P7" Pull request url: https://github.com/pharo-project/pharo/pull/2046 Issue Url: https://pharo.fogbugz.com/f/cases/22735 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: halos
by John Kimber Dec. 10, 2018

Dec. 10, 2018

shift-control click works for me on 1384. HTH, john -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Esteban's ChangeLog week of 3 December 2018
by estebanlm＠gmail.com Dec. 10, 2018

Dec. 10, 2018

Hello! This is my weekly ChangeLog, from 3 December 2018 to 9 December 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=3/12/2018&to=9/12/2018 ChangeLog ========= 6 December 2018: ---------------- * I made a small [PR](https://github.com/pharo-ide/Calypso/pull/375) on Calypso to better expose the contextual spotter that helps to find available Calypso commands. 5 December 2018: ---------------- * Ok, finally I finished next stop on automation of releases, which made us to change the default development branch (to "Pharo7.0" for the moment). This will allow us to keep different active "development" branches. One thing I would like to achieve eventually is to keep: * A current development version (it will be Pharo8.0 soon). * A maintained stable version (Pharo7.0 and potential Pharo7.1, etc.). * A Long term support (LTS) version that will continue incorporating critic systems. So well, this are the steps to arrive there :) cheers! Esteban

1 0

Calypso equivalent <nautilusGlobalPackageMenu>
by Ben Coman Dec. 9, 2018

Dec. 9, 2018

What is the Calypso equivalent of <nautilusGlobalPackageMenu> ? I need to add an extra menu item to the Packages context menu. cheers -ben

2 1

Release candidate version numbers
by Ben Coman Dec. 9, 2018

Dec. 9, 2018

In PharoLauncher under "Pharo 7 (development version)" opening template Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit then System > System Report shows... Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 Bit) but under "Official distributions" I see Pharo 7.0 - 32bit (development version) then System > System Report shows... Pharo-7.0.0+rc1.build.24.sha.41c89eb7dd9f362ca1ba874f1d9a42602396e002 (32 Bit) Why using such a different and small number "24", and a long way from 1433 ? cheers -ben

2 2