Re: [Pharo-users] nested json problem

2018-11-05 Thread Roelof Wobben
Problem has solved. I had the instance variable to   instance := self new. instead of instance := self basicNew. Roelof Op 5-11-2018 om 22:50 schreef Sven Van Caekenberghe: On 5 Nov 2018, at 22:41, Roelof Wobben wrote: I use this code to try to read things: json paintingCollection

Re: [Pharo-users] nested json problem

2018-11-05 Thread Sven Van Caekenberghe
> On 5 Nov 2018, at 22:41, Roelof Wobben wrote: > > I use this code to try to read things: > > json paintingCollection | > json := (NeoJSONReader fromString: (ZnEasy get: ' > https://www.rijksmuseum.nl/api/nl/collection?key=14OGzuak=json=schilderij=True > ') contents). > paintingCollection

Re: [Pharo-users] nested json problem

2018-11-05 Thread Roelof Wobben
I use this code to try to read things: json paintingCollection | json := (NeoJSONReader fromString: (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection?key=14OGzuak=json=schilderij=True') contents). paintingCollection := PaintingCollection fromJSON: json.

Re: [Pharo-users] nested json problem

2018-11-05 Thread Erik Stel
Roelof, What does not work in your code? How do you call PaintingCollection>>fromJSON: ? >From what I see this code could work if used like (replace URL with actual URL): -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] nested json problem

2018-11-05 Thread Sven Van Caekenberghe
Hi/Dag Roelof, In a first approach I would not start by trying to map to actual domain objects (you can do that later), I would start by using NeoJSONObject, which is quite flexible and user friendly. Consider the following example: (NeoJSONObject fromString: '{ "elapsedMilliseconds": 164,

[Pharo-users] nested json problem

2018-11-05 Thread Roelof Wobben
Hello, I try to use the rijksmuseum api. This gives json back for 10 paintings and the json looks like this : { "elapsedMilliseconds": 164, "count": 359, "artObjects": [ { "links": { "self":

[Pharo-users] [ANN] Pharo v7.0.0-rc1 released!

2018-11-05 Thread Esteban Lorenzano
Greetings! I’m announcing today we reach Pharo 7.0.0-rc1! This is the first step to release a definitive version, and while we will continue integrating bug fixes, API change Pull Requests will be delayed until the open of Pharo 8.0.0 development. Now, you would wonder what is the ChangeLog

[Pharo-users] [ANN] Iceberg v1.3.1

2018-11-05 Thread Cyril Ferlicot
Hello! This week we are releasing the version v1.3 of Iceberg. (https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.0 +https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.1) This version will be available after we merge this PR: https://github.com/pharo-project/pharo/pull/1951 This

Re: [Pharo-users] git repos cloned into unexpected directory

2018-11-05 Thread Arturo Zambrano
Thanks Alistair. That solves the problem. Cheers Arturo On Fri, Nov 2, 2018 at 2:41 PM Alistair Grant wrote: > Hi Arturo, > > On Fri, 2 Nov 2018 at 12:49, Arturo Zambrano > wrote: > > > > Hi! > > I'm getting the following strange behavior using Iceberg in Pharo7 . > > > > My setup is like