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

glamorous toolkit alpha.2

by Tudor Girba

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."

Oct. 31, 2018

Re: [Pharo-dev] [ANN] The STON Specification

by David T. Lewis

This is very clear and well written. Dave > Hi, > > Since there can never be enough documentation I finally took some time to > write a more formal description of STON as a data format. > > https://github.com/svenvc/ston/blob/master/ston-spec.md > > The idea is to let this stabilise a bit and to then update the two other > documents describing STON, where necessary: > > https://github.com/svenvc/ston/blob/master/ston-paper.md > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > Also, the latest changes in STON have to make their way to the Pharo image > as well. > > https://github.com/svenvc/ston > > All feedback is welcome. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Oct. 31, 2018

[ANN] The STON Specification

by Sven Van Caekenberghe

Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Oct. 31, 2018

Re: [Pharo-dev] ClyMethodGroup>>#fileOut dead code ?

by Denis Kudriashov

Hi Sven. It is not dead. It is here to file out any method group including normal protocols. It was copied from SystemOrganizer>>fileOutCategory:. Now it needs to be fixed in Pharo 7 and it would be nice to have it in better form ÑÑ, 31 Ð¾ÐºÑ. 2018 Ð³. Ð² 15:39, Sven Van Caekenberghe <sven(a)stfx.eu>: > 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 >

Oct. 31, 2018

Source/changes file suffixes constants

by Sven Van Caekenberghe

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

Oct. 31, 2018

Re: [Pharo-dev] About #zipped / #unzipped

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/pull/1947 > On 26 Oct 2018, at 22:28, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > +1 > > On Tue, Oct 23, 2018 at 10:50 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 18 Oct 2018, at 20:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> 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 ? >>> >> >> Yes, to me this sounds interestingâ¦ I think compression is indeed better done on the level of bytes then on Strings. >> >> >> Marcus >> >> >

Oct. 31, 2018

ClyMethodGroup>>#fileOut dead code ?

by Sven Van Caekenberghe

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

Oct. 31, 2018

[Pharo 7.0-dev] Build #1358: 22608-Deprecate-FileDialog-methods-that-open-streams

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

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…

Oct. 31, 2018

[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

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…

Oct. 31, 2018

[Pharo 7.0-dev] Build #1356: Adding class OCCompilerDynamicASTPlugin (and its test class), allowiâ¦

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

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…

Oct. 31, 2018