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

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Denis Kudriashov

Hi Guille. What you think to add helpfull converting methods? aStream buffered. aStream encodedWith: 'utf8'. aStream utf8Encoded. "because it is very common case". aStream decodedFrom: 'utf8'. aStream utf8Decoded. "because it is very common case". aStream withLineEnding: String cr. aStream withPlatformLineEnding. (all methods will return new streams) 2018-03-19 17:19 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > 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 <+33%206%2052%2070%2066%2013> >

March 19, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Cyril Ferlicot D.

Le 19/03/2018 Ã 18:49, Stephan Eggermont a Ã©crit : > Then why bother releasing? > Hi, For people using Pharo 7 to not get the same bugs for more than 1 year, to get the new functionalities and to be able to detect new bugs introduced in releases. > Stephan > > > > > -- Cyril Ferlicot https://ferlicot.fr

March 19, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Stephan Eggermont

Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-03-19 9:16 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > >> Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >>> 2018-03-17 17:01 GMT+01:00 Stephan Eggermont >> <stephan(a)stack.nl>: >>> >>>> Denis Kudriashov <dionisiydk(a)gmail.com> >>>> wrote: >>>>> >>>>> No. Each build just loads specified version. I do not need to create >> new >>>>> version for new build. >>>>> But I think I still not understand you >>>> >>>> That specified version will no longer work in a newer pharo build. Pharo >>>> changes, making it necessary for your dependencies to change. Will you >> make >>>> a new release each time one of your dependencies needs to change? >>>> >>> >>> I do not put dependencies of projects which are part of standard Pharo >>> image. So Pharo updates do not affect my baselines >> >> And your dependencies are not impacted by standard pharo changes? >> > > It can be impacted of course. But it is normal process for alpha Pharo 7. > And Pharo 6 is fixed, so I do not care. Then why bother releasing? Stephan

March 19, 2018

New Files in Pharo - Migration Guide, How To's and examples

by Guillermo Polito

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

March 19, 2018

[Pharo 7.0-dev] Build #704: Fix #21602. Choose line ending convention in ZnCrPortableWriteStream.

by ci-pharo-ci-jenkins2＠inria.fr

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…

March 19, 2018

[Pharo 7.0-dev] Build #703: 21619-Integrate-new-Calypso-version-0110

by ci-pharo-ci-jenkins2＠inria.fr

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…

March 19, 2018

Re: [Pharo-dev] Ctrl+W in tabbed windows (GT inspector, browser/Calypso)

by Esteban A. Maringolo

2018-03-19 7:08 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > On 19 March 2018 at 17:07, Petr Fischer <petr.fischer(a)me.com> wrote: >> 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? > > > Actually I never knew that shortcut, but I will now. > I see it works that way in both Chrome and InternetExplorer and web browsers > are a good benchmark. It's the sibling of Ctrl+Tab and Ctrl+Shift+Tab to move forward or backward in a list of tabs. I use it a lot. Esteban A. Maringolo

March 19, 2018

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

by Guillermo Polito

On Mon, Mar 19, 2018 at 2:13 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Guille, > > On 19 March 2018 at 13:59, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi! > > > > On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > > > > [SNIP] > >> > >> > >> > >> https://pharo.fogbugz.com/f/cases/21615/Separate- > bootstrap-process-in-to-distinct-stages > >> > >> https://github.com/pharo-project/pharo/pull/1127 > >> > >> This does the first step of breaking the bootstrap process in to > >> distinct phases and moving all the downloads to the start (e.g. > >> allowing a test VM to be substituted for the build stage). > > > > > > Nice! thanks! > > > >> > >> > >> Once this is integrated I can submit a PR that modifies Jenkinsfile to > >> use the new shell scripts, removing code duplication. > > > > > > Question: Why not in this same PR? > > Because I'm not at all familiar with Jenkins, so am a bit nervous > about changing it. Smaller changes will be easier to work on if > something goes wrong. :-) > > Ah, but if you do something wrong the build will fail. In any case, as soon as you want to dive into changing the JenkinsFile, send me a private mail. I probably have to give you permissions in Jenkins (otherwise jenkins ignores changes in the JenkinsFile for security reasons). > Cheers, > Alistair > > > > >> On 16 March 2018 at 14:38, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > >> > Hi, > >> > sorry my mistake when updating the scripts. As the bootstrap.sh > is > >> > not > >> > executed during the Jenkins process it has not been validated (locally > >> > I'm > >> > not using that script, because is trying to download each time the VM > >> > and > >> > the bootstraping process image) > >> > >> There are also scripts to snapshot and restore the bootstrap state, > >> avoiding the need to do the multiple downloads. > >> > >> Just to be clear again: This is intended to complement and help with > >> the goal of moving the bootstrap process to pure Pharo code. Each of > >> the shell scripts can eventually be replaced by a call to the > >> equivalent Pharo code. > >> > > > > :) > > > >> > >> > >> Thanks! > >> Alistair > >> > > > > > > > > -- > > > > > > > > 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 > > > > > > Web: http://guillep.github.io > > > > Phone: +33 06 52 70 66 13 > > -- 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

March 19, 2018

Re: [Pharo-dev] Ctrl+W in tabbed windows (GT inspector, browser/Calypso)

by Petr Fischer

> Ok. I see. > > It is not scenario which I used. > Now I fixed it in dev version Wow that's fast! Next time I will use github issues for it (probably the preferred way). Thanks. > 2018-03-19 13:32 GMT+01:00 Petr Fischer <petr.fischer(a)me.com>: > > > It's completely weird: > > > > 1) first Ctrl+W closes the "content" of the tab > > 2) second Ctrl+W closes whole tabbed window > > > > Look at thos video: https://youtu.be/MUcYNGnDAR8 > > > > pf > > > > > Hi. > > > > > > Are you sure that Calypso closes full window instead of single tab? > > > Because I use it all the time and it works for me in the way you > > described. > > > > > > 2018-03-19 10:07 GMT+01:00 Petr Fischer <petr.fischer(a)me.com>: > > > > > > > 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 > > > > > > > > > > > >

March 19, 2018

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

by Alistair Grant

Hi Guille, On 19 March 2018 at 13:59, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > [SNIP] >> >> >> >> https://pharo.fogbugz.com/f/cases/21615/Separate-bootstrap-process-in-to-di… >> >> https://github.com/pharo-project/pharo/pull/1127 >> >> This does the first step of breaking the bootstrap process in to >> distinct phases and moving all the downloads to the start (e.g. >> allowing a test VM to be substituted for the build stage). > > > Nice! thanks! > >> >> >> Once this is integrated I can submit a PR that modifies Jenkinsfile to >> use the new shell scripts, removing code duplication. > > > Question: Why not in this same PR? Because I'm not at all familiar with Jenkins, so am a bit nervous about changing it. Smaller changes will be easier to work on if something goes wrong. :-) Cheers, Alistair >> On 16 March 2018 at 14:38, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: >> > Hi, >> > sorry my mistake when updating the scripts. As the bootstrap.sh is >> > not >> > executed during the Jenkins process it has not been validated (locally >> > I'm >> > not using that script, because is trying to download each time the VM >> > and >> > the bootstraping process image) >> >> There are also scripts to snapshot and restore the bootstrap state, >> avoiding the need to do the multiple downloads. >> >> Just to be clear again: This is intended to complement and help with >> the goal of moving the bootstrap process to pure Pharo code. Each of >> the shell scripts can eventually be replaced by a call to the >> equivalent Pharo code. >> > > :) > >> >> >> Thanks! >> Alistair >> > > > > -- > > > > 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 > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13

March 19, 2018