- Pharo-dev - lists.pharo.org

STON updates/improvements
by Sven Van Caekenberghe Oct. 23, 2018

Oct. 23, 2018

Hi, I have consolidated all repositories where STON code lives so that they are now all in sync, and in sync with changes from Pharo 7. http://ss3.gemtalksystems.com/ss/STON/ http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ https://github.com/svenvc/ston There are 2 CI builds https://travis-ci.org/svenvc/ston https://ci.inria.fr/pharo-contribution/job/STON/ The project's format will remain FileTree (until Tonel is supported on other Smalltalk implementations). Last week I applied a couple of changes that I wanted to apply for a long time. Traits are no longer used in the implementation (which should help porting to other Smalltalk implementations). More specifically the following are used (again) - Class>>#stonOn: - ClassDescription>>#stonContainsSubObjects - Metaclass>>#stonName - Metaclass>>#stonOn: instead of - TClass>>#stonOn: - TClassDescription>>#stonContainsSubObjects - TApplyingOnClassSide>>#stonName - TApplyingOnClassSide>>#stonOn: use #instanceSide instead of #theNonMetaClass in MetaClass>>#stonOn: Reorganised the packages with sub tags. Add support for Fraction and ScaledDecimal literals (not in JSON mode). Previously a float conversion meant there was a loss of information. Change the representation of Date to include a timezone offset (since the current Date implementation is sensitive to this). 2018-10-11Z 2018-10-11+00:00 2018-10-11+02:00 A missing timezone offset is interpreted as being the local timezone offset. Add more special representations for common value style objects. One of STON's goals is to be a human readable and human editable representation of an object graph while remaining 100% correct (not losing information). The following were added for this reason: MimeType and URL using ZnMimeType and ZnUrl respectively as simplified values. MimeType['application/json'] URL['https://pharo.org'] Color Color[#red] Color{#red:1.0,#green:0.0,#blue:0.0,#alpha:0.4} FileReferences to the DiskFileSystem (effectively normal files) FILE['/tmp/foo.txt'] Here is an example of how much difference that makes. Given the following Dictionary { #background->Color red. #workdir->'/tmp/pharo/work/' asFileReference. #home->'https://pharo.org/experimental' asUrl. #datatype->'application/json' asMIMEType } asDictionary Which contains real objects as its values. was serialised by STON BEFORE the changes as { #datatype : ZnMimeType { #main : 'application', #sub : 'json' }, #background : Color { #rgb : 1072693248, #cachedDepth : 32, #cachedBitPattern : Bitmap [ 4294901760 ], #alpha : 255 }, #home : ZnUrl { #scheme : #https, #host : 'pharo.org', #segments : OrderedCollection [ 'experimental' ] }, #workdir : FileReference { #filesystem : FileSystem { #store : MacStore { #maxFileNameLength : 255 } }, #path : AbsolutePath [ 'tmp', 'pharo', 'work' ] } } which is 100% correct, but not very human friendly. Now, AFTER the changes, the STON serialisation looks as follows: { #datatype : MimeType [ 'application/json' ], #background : Color [ #red ], #home : URL [ 'https://pharo.org/experimental' ], #workdir : FILE [ '/tmp/pharo/work' ] } which is a huge improvement, IMO. What do you think ? Comments, feedback, remarks ? Any other suggestions for other object that could use this treatment ? Sven

5 11

[Pharo 7.0-dev] Build #1346: 22585 Tag ManifestSystemSupport and related classes in System-Support
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1346 was: FAILURE. The Pull Request #1931 was integrated: "22585 Tag ManifestSystemSupport and related classes in System-Support" Pull request url: https://github.com/pharo-project/pharo/pull/1931 Issue Url: https://pharo.fogbugz.com/f/cases/22585 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1345: 22598 Tag ManifestManifestTests and other classes in Manifest-Tests
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1345 was: FAILURE. The Pull Request #1934 was integrated: "22598 Tag ManifestManifestTests and other classes in Manifest-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1934 Issue Url: https://pharo.fogbugz.com/f/cases/22598 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1344: 22599 Tag ManifestPharoBootstrapInitialization and related classes
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1344 was: SUCCESS. The Pull Request #1935 was integrated: "22599 Tag ManifestPharoBootstrapInitialization and related classes" Pull request url: https://github.com/pharo-project/pharo/pull/1935 Issue Url: https://pharo.fogbugz.com/f/cases/22599 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1343: 22593-GZipReadStream-enhancement-Pharo-7-streams-and-tests
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1343 was: SUCCESS. The Pull Request #1929 was integrated: "22593-GZipReadStream-enhancement-Pharo-7-streams-and-tests" Pull request url: https://github.com/pharo-project/pharo/pull/1929 Issue Url: https://pharo.fogbugz.com/f/cases/22593 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1342: 22223 Categorize classes in System-Changes
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1342 was: FAILURE. The Pull Request #1930 was integrated: "22223 Categorize classes in System-Changes" Pull request url: https://github.com/pharo-project/pharo/pull/1930 Issue Url: https://pharo.fogbugz.com/f/cases/22223 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1341: 22591-MoticellowarnAboutLosingChangesTo-is-dead-code
by ci-pharo-ci-jenkins2＠inria.fr Oct. 22, 2018

Oct. 22, 2018

There is a new Pharo build available! The status of the build #1341 was: FAILURE. The Pull Request #1927 was integrated: "22591-MoticellowarnAboutLosingChangesTo-is-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/1927 Issue Url: https://pharo.fogbugz.com/f/cases/22591 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Oct 26
by Marcus Denker Oct. 22, 2018

Oct. 22, 2018

We will organize a Pharo sprint / Moose dojo Oct 26, 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-2973622

1 0

Pharo Memcached client
by Sven Van Caekenberghe Oct. 18, 2018

Oct. 18, 2018

Hi, I copied the (Pharo) Memcached client to https://github.com/svenvc/memcached where is lives in Tonel format with a Baseline and a working Travis CI build against an actual memcached server in the worker. More about memcached - https://en.wikipedia.org/wiki/Memcached - http://memcached.org Acknowledgements The original project can be found at http://www.squeaksource.com/memcached.html As far as I can see it was written by Philippe Marschall and Ramon Leon. I ported the codebase to Pharo. This repository is a recent copy with some cleanups. I intend to maintain this as I need it myself. The codebase should still maintain its original portability (minus the meta info, possibly). Sven

1 0

[Pharo 7.0-dev] Build #1340: 22575-GZipReadStream-classunzipto-results-in-an-Invalid-utf8-input-detected-error
by ci-pharo-ci-jenkins2＠inria.fr Oct. 18, 2018

Oct. 18, 2018

There is a new Pharo build available! The status of the build #1340 was: FAILURE. The Pull Request #1909 was integrated: "22575-GZipReadStream-classunzipto-results-in-an-Invalid-utf8-input-detected-error" Pull request url: https://github.com/pharo-project/pharo/pull/1909 Issue Url: https://pharo.fogbugz.com/f/cases/22575 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0