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

Where to discuss strategies and tools for a comeback of Smalltalk using Scratch as entrance
by Bernhard HÃ¶fner Nov. 2, 2018

Nov. 2, 2018

> Hello Group. I like to discuss about the subject and have also some ideas. But I want to ask first for the proper list within the forum. I heard that there is a discussion ongoing and want to participate. > > I will send this question to Squeak and Pharo usegroup and to the Phratch-developer. I assume that there is a common discussion about the subject. Hopefully there is no need to open on each platform an individual thread. > > Regards, Bernhard

2 2

Source/changes file suffixes constants
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, Current FileStream holds (in the protocol 'file reader services') some constants regarding source/changes file suffixes. Where should we move these to (as FileStream is deprecated) ? There is a class SourceFile, there is PharoFilesOpener, neither seems to fit that well. Suggestions ? Sven

2 2

ClyMethodGroup>>#fileOut dead code ?
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, ClyMethodGroup>>#fileOut seems like dead code (it sends #trailer to a WriteStream which DNUs). It also uses the deprecated FileStream. Can it be removed ? Sven

3 2

glamorous toolkit alpha.2
by Tudor Girba Oct. 31, 2018

Oct. 31, 2018

Hi, Glamorous Toolkit has evolved quite a bit over the past months, and we now would like to announce that we reached alpha.2 version. It runs on top of Pharo 7: feenk.com/gt There quite a number of new things. Some highlights are: - We added extensive documentation for GT, Bloc and Brick. By running "GtWorld openTourâ you essentially transform the image into an elaborate wiki. - We worked on Coder, a new set of tools that are dedicated for affecting code. For example, in the picture below we see an editor on embedded examples that can be edited and run independently. And this one shows how we can visualize and edit the result of querying. Just a note: To make Coder work the way we want, we extended Brick with several widgets, and enhanced significantly the linear and grid layouts. - We added the first version of xdoc in order to serialize the Playground every time you evaluate something. As always, we are looking forward to your feedback. Have fun, The feenk team -- www.feenk.com -- www.feenk.com "Every thing should have the right to be different."

1 0

About #zipped / #unzipped
by Sven Van Caekenberghe Oct. 31, 2018

Oct. 31, 2018

Hi, Given https://pharo.fogbugz.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSys… [where we need more help !!] I found String>>#zipped to be one of the users of the deprecated RWBinaryOrTextStream. Although this usage is easy enough to fix, I think the current #zipped / #unzipped on String is broken. (note also that there are no real users of these methods) Right now it seems cool that the following is an identity. 'foobar' zipped unzipped. However, the result of zipping something is actual something binary (a collection of opaque bytes). Thinking of it, the input is actually also bytes, not unencoded characters. Of course, the current methods are broken, as can be seen from a more complex (wide) string. 'Ã©lÃ¨ves FranÃ§aises @ 10 â¬' zipped unzipped. >>> <something very weird> The error results from some implicit/wrong character encoding being used. The right way to do this is to explicitly encode/decode the string. (GZipReadStream on: (ByteArray streamContents: [ :out | (GZipWriteStream on: out) nextPutAll: 'Ã©lÃ¨ves FranÃ§aises Ã 10 â¬' utf8Encoded; close ])) upToEnd utf8Decoded. >From this it would follow that #zipped / #unzipped would make more sense on ByteArray. So that the above identity would become. 'Ã©lÃ¨ves FranÃ§aises Ã 10 â¬' utf8Encoded zipped unzipped utf8Decoded. This change of signature would be comparable to what we recently did with #base64Encoded / #base64Decoded What do you think ? Sven

3 3

[Pharo 7.0-dev] Build #1358: 22608-Deprecate-FileDialog-methods-that-open-streams
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1358 was: FAILURE. The Pull Request #1941 was integrated: "22608-Deprecate-FileDialog-methods-that-open-streams" Pull request url: https://github.com/pharo-project/pharo/pull/1941 Issue Url: https://pharo.fogbugz.com/f/cases/22608 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1357: Added a guard in LinkedList>>sort: that directly returns self if the â¦
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1357 was: SUCCESS. The Pull Request #1921 was integrated: "Added a guard in LinkedList>>sort: that directly returns self if the â¦" Pull request url: https://github.com/pharo-project/pharo/pull/1921 Issue Url: https://pharo.fogbugz.com/f/cases/22587 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1356: Adding class OCCompilerDynamicASTPlugin (and its test class), allowiâ¦
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1356 was: FAILURE. The Pull Request #1920 was integrated: " Adding class OCCompilerDynamicASTPlugin (and its test class), allowiâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1920 Issue Url: https://pharo.fogbugz.com/f/cases/DynamicCompilerPlugins Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1355: 22466-Add-readWriteStream-and-readWriteStreamDo-in-FileSystem
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1355 was: FAILURE. The Pull Request #1924 was integrated: "22466-Add-readWriteStream-and-readWriteStreamDo-in-FileSystem" Pull request url: https://github.com/pharo-project/pharo/pull/1924 Issue Url: https://pharo.fogbugz.com/f/cases/22466 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1354: 22617-MemoryFileWriteStreamclose-doesnt-flush
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

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

1 0