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

[Pharo 7.0-dev] Build #705: 21618-Saving-code-as-file-tree-is-broken
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #705 was: FAILURE. The Pull Request #1132 was integrated: "21618-Saving-code-as-file-tree-is-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1132 Issue Url: https://pharo.fogbugz.com/f/cases/21618 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

New Files in Pharo - Migration Guide, How To's and examples
by Guillermo Polito March 20, 2018

March 20, 2018

Hi all, I've put some minutes summarizing the new APIs provided by the combination of the new File implementation and the Zn encoders. They all basically follow the decorator pattern to stack different responsibilities such as buffering, encoding, line ending convertions. Please, do not hesitate to give your feedback. Guille 1. Basic Files By default files are binary. Not buffered. (File named: 'name') readStream. (File named: 'name') readStreamDo: [ :stream | ... ]. (File named: 'name') writeStream. (File named: 'name') writeStreamDo: [ :stream | ... ]. 2. Encoding To add encoding, wrap a stream with a corresponding ZnCharacterRead/WriteStream. "Reading" utf8Encoded := ZnCharacterReadStream on: aBinaryStream encoding: 'utf8'. utf16Encoded := ZnCharacterReadStream on: aBinaryStream encoding: 'utf16'. "Writing" utf8Encoded := ZnCharacterWriteStream on: aBinaryStream encoding: 'utf8'. utf16Encoded := ZnCharacterWriteStream on: aBinaryStream encoding: 'utf16'. 3. Buffering To add buffering, wrap a stream with a corresponding ZnBufferedRead/WriteStream. bufferedReadStream := ZnBufferedReadStream on: aStream. bufferedWriteStream := ZnBufferedWriteStream on: aStream. It is in general better to buffer the reading on the binary file and apply the encoding on the buffer in memory than the other way around. See [file := Smalltalk sourcesFile fullName. (File named: file) readStreamDo: [ :binaryFile | (ZnCharacterReadStream on: (ZnBufferedReadStream on: binaryFile) encoding: 'utf8') upToEnd ]] timeToRun. "0:00:00:09.288" [file := Smalltalk sourcesFile fullName. (File named: file) readStreamDo: [ :binaryFile | (ZnBufferedReadStream on: (ZnCharacterReadStream on: binaryFile encoding: 'utf8')) upToEnd ]] timeToRun. "0:00:00:14.189" 4. File System By default, file system files are buffered and utf8 encoded to keep backwards compatibility. 'name' asFileReference readStreamDo: [ :bufferedUtf8Stream | ... ]. 'name' asFileReference writeStreamDo: [ :bufferedUtf8Stream | ... ]. FileStream also provides access to plain binary files using the #binaryRead/WriteStream messages. Binary streams are buffered by default also. 'name' asFileReference binaryReadStreamDo: [ :bufferedBinaryStream | ... ]. 'name' asFileReference binaryWriteStreamDo: [ :bufferedBinaryStream | ... ]. If you want a file with another encoding (to come in the PR https://github.com/pharo-project/pharo/pull/1134) you can specify it while obtaining the stream: 'name' asFileReference readStreamEncoded: 'utf16' do: [ :bufferedUtf16Stream | ... ]. 'name' asFileReference writeStreamEncoded: 'utf8' do: [ :bufferedUtf16Stream | ... ]. 5. Line Ending Conventions If you want to write files following a specific line ending convention, use the ZnNewLineWriterStream. This stream decorator will transform any line ending (cr, lf, crlf) into a defined line ending. By default it chooses the platform line ending convention. lineWriter := ZnNewLineWriterStream on: aStream. If you want to choose another line ending convention you can do: lineWriter forCr. lineWriter forLf. lineWriter forCrLf. lineWriter forPlatformLineEnding. -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

5 8

[Pharo 7] Help needed reviewing Pull requests
by Marcus Denker March 20, 2018

March 20, 2018

Hello, we need more people helping to review and tests Pull Requests. https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> Especially, it is very important to add a note if you think that something should be merged. Even if it is clear from the context. We need an explicit âthis is good to integrateâ. Marcus

1 0

Released versions in Pharo Bootstrap
by tesonep＠gmail.com March 19, 2018

March 19, 2018

Hello, i have seen in the latest version of Pharo baselines pointing to "floating" versions. A version that is not fixed. I want to know why this is like that? To me this is basically wrong, because basically this goes against the idea of having repeatable builds. Also using semantic versions with tags in Git is wrong, as tags should be immutable (that is why you have to use --force to update them, in Guille's words "If you have to force it, it is not good"). Cheers, -- Pablo Tesone. tesonep(a)gmail.com

12 49

[Pharo 7.0-dev] Build #704: Fix #21602. Choose line ending convention in ZnCrPortableWriteStream.
by ci-pharo-ci-jenkins2＠inria.fr March 19, 2018

March 19, 2018

There is a new Pharo build available! The status of the build #704 was: SUCCESS. The Pull Request #1116 was integrated: "Fix #21602. Choose line ending convention in ZnCrPortableWriteStream." Pull request url: https://github.com/pharo-project/pharo/pull/1116 Issue Url: https://pharo.fogbugz.com/f/cases/21602 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #703: 21619-Integrate-new-Calypso-version-0110
by ci-pharo-ci-jenkins2＠inria.fr March 19, 2018

March 19, 2018

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

1 0

Ctrl+W in tabbed windows (GT inspector, browser/Calypso)
by Petr Fischer March 19, 2018

March 19, 2018

Hello! I assume that Ctrl+W is a widely used keyboard shortcut for closing windows or a tab, if the window is "tabbed" (it works in web browsers, some desktops, Linux, IE, Mac OS X...). But when I start up some exploration session in GT inspector, I have several tabs opened in a second - then, after Ctrl+W, not the actual tab, but the whole window is immediately closed, gosh... Same situation in "window groups" (when you created tabbed window group from browser/Calypso) - Ctrl+W behaves weird. Is everyone in comfort with the idea that Ctrl+W should close the actual tab, and if there is no tab in the window (or actual tab is the last tab), then close the window? Tested in Pharo 5, 6 and 6.1. pf

5 8

pharo bootstrap is in inconsistent state
by Alistair Grant March 19, 2018

March 19, 2018

Hi Pablo & Everyone, The bootstrap process seems to be in an inconsistent state at the moment as the scripts in: - Jenkinsfile and - bootstrap/scripts/bootstrap.sh don't match. bootstrap/scripts/bootstrap.sh has an error in it: ./pharo Pharo.image eval "PBBootstrap fromCommandLine bootstrap" --quit fails because the "--quit" option is valid for the st handler (executing a smalltalk file), but isn't recognised by the eval handler. Can someone, Pablo?, confirm what the status is, what it should be and what the next steps are? :-) Thanks, Alistair

3 7

Idea to manager package comment in better way
by Denis Kudriashov March 19, 2018

March 19, 2018

Hi. I look at hierarchy of PackageManifest and I was wondering that all these classes are commented but most of packages which they describe are not. Also interesting that most of manifest comments are same. Then I found that package comment is managed as special class side method #description which is generated when you call "aPackage packageComment: 'test'". Now the idea: will not it be better to manage package comment as manifest class comment? Manifest is already responsible to describe the package. So it looks logical to have "manifest comment = package comment". Also it will simplify code and remove duplication of texts. In addition it will add extra place indicating that package needs to be commented because uncommented classes are marked in the browser. What you think?

3 5

Performances of source code search on latest Pharo
by Cyril Ferlicot March 18, 2018

March 18, 2018

HI, We have a regression on source code search performances in latest Pharo. I am on Windows 10. With Pharo 6.1 it takes a few seconds to look for a string in all the image source code. With the latest Pharo 7 it takes minutes. To reproduce: - Open a playground - Type something - Select the text, right click - Clic on "Code search..." -> "Method source with it" https://pharo.fogbugz.com/f/cases/21612/Performances-regression-on-source-c… -- Cyril Ferlicot https://ferlicot.fr

4 7