Re: [Pharo-users] NeoJSON and polymorphism

2017-09-26 Thread Sven Van Caekenberghe
> On 25 Sep 2017, at 17:14, Juraj Kubelka wrote: > > Hi Sven, > > thank you! > > In the NeoJSON repository, you likely want to merge > Neo-JSON-Core-SvenVanCaekenberghe.43 and 44. And the same for the test cases. I did, thanks ! >> On Sep 24, 2017, at 06:05, Sven

Re: [Pharo-users] NeoJSON and polymorphism

2017-09-25 Thread Juraj Kubelka
Hi Sven, thank you! In the NeoJSON repository, you likely want to merge Neo-JSON-Core-SvenVanCaekenberghe.43 and 44. And the same for the test cases. > On Sep 24, 2017, at 06:05, Sven Van Caekenberghe wrote: > > Hi Juraj, > > This would be a simpler form of the type/class

Re: [Pharo-users] NeoJSON and polymorphism

2017-09-24 Thread Stephane Ducasse
Sven do you think that it is worth to create a new section with the xample and the solution in the book? On Sun, Sep 24, 2017 at 11:05 AM, Sven Van Caekenberghe wrote: > Hi Juraj, > > This would be a simpler form of the type/class tags that are often used in > JSON encoding. Since

Re: [Pharo-users] NeoJSON and polymorphism

2017-09-24 Thread Sven Van Caekenberghe
Hi Juraj, This would be a simpler form of the type/class tags that are often used in JSON encoding. Since there are many ways to do this, there cannot be one solution. NeoJSON mapping was not designed to cover these cases. Nor is JSON meant to do this. STON is one (rather elegant if I may say

[Pharo-users] NeoJSON and polymorphism

2017-09-21 Thread Juraj Kubelka
Hi, By studying the NeoJSON book chapter (Pharo Enterprise), I do not understand how to modify the following example: -=-=-=-=-=-=-=- "Let us say that we have an Attachment class..." Object subclass: #Attachment instanceVariableNames: 'url fileName' classVariableNames: ''