December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo FIleSystem Compatibility with Gemstone's FileSystemGs
by Guillermo Polito Dec. 12, 2018

Dec. 12, 2018

Hi Reg, Thanks for your email, improving FileSystem is a cool thing ^^. On Tue, Dec 11, 2018 at 8:39 PM Reg Krock via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > 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. > Well, I don't know if there is a single maintainer. I think that myself, Alistair, Sven, and many others can answer to questions on different aspects of file system. Anyways, I'd suggest you just send your emails to this mailing list, the person concerned/interested will answer when possible ;) > > Areas of exploration to date have been: > > 1. Replacement of File with GsFile - in Gemstone we want to use the > native file class. > > How have you made it pluggable? This maybe requires the introduction of a backend or a separate store "GSFileSystemStore"? Does Gemstone require different kind of implementations for different platforms like linux/windows/osx or just a unix-like one is enough? > > 1. 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 > I like the introduction of objects :) What is the difference between the binary and non binary modes? How do you specify encoding for non binary ones? Or you assume ascii? Also, the fact that the "binary" aspect is repeated all over the hierarchy makes me think they could be composable aspects of a file mode. > > - 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) > Well, AFAIU, this is not public API (and it uses booleans to indicate "mode"). Usually end users would simply do: aFileReference writeStream. aFileReference binaryWriteStream. aFileReference readStream. aFileReference binaryReadStream. But yes, I like also to model modes such as truncated, append, "force new". > 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: > Well, we could keep the old API and build a higher level one on top, don't we? Do you have your code in a repository we could check? > Thanks for your help. > Thanks to you! Guille > Reg >

2 1

[ANN] Next Pharo Sprint: Dec 21
by Marcus Denker Dec. 12, 2018

Dec. 12, 2018

We will organize a Pharo sprint / Moose dojo Dec 21, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973628

1 0

[Pharo 7.0] Build #29: 22751-Improve-RFLiteralVariableNode-printing
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 #29 was: FAILURE. The Pull Request #2058 was integrated: "22751-Improve-RFLiteralVariableNode-printing" Pull request url: https://github.com/pharo-project/pharo/pull/2058 Issue Url: https://pharo.fogbugz.com/f/cases/22751 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #28: 22703-Block-execution-arguments-reification
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 #28 was: SUCCESS. The Pull Request #2059 was integrated: "22703-Block-execution-arguments-reification" Pull request url: https://github.com/pharo-project/pharo/pull/2059 Issue Url: https://pharo.fogbugz.com/f/cases/22703 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[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