8 Aug
2011
8 Aug
'11
8:15 p.m.
Hi,
I'm experimenting with a JSON converter for objects with Magritte
descriptions. So far I've added the following to GRObject:
jsonOn: aStream
| description |
description := self description.
description children isEmpty ifFalse: [
| first |
first := true.
aStream nextPut: ${.
description do: [ :each |
first
ifTrue: [ first := false ]
ifFalse: [ aStream nextPut: $, ].
aStream
json: each label;
nextPut: $:;
json: (each accessor read: self) ].
aStream nextPut: $} ]
you can then generate JSON from an object, for example:
((PRPage named: 'examplePage') contents: '!!Hello', String crlf,
'Hello
""world"" check') asJson
gives:
'{"Name":"examplePage","Visibility":false,"Navigation
Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain
Text":"Hello\rHello world check","Environment":null,"Style
Sheet":null,"Shortcut Icon":null,"CSS Classes":null}'
The method fails with recursive structures, but otherwise is appears to work
well.
Does this look like a sensible approach? Has anyone else implemented
anything similar?
Thanks
Nick
8 Aug
8 Aug
10:55 p.m.
Hi,
There is something simular in the Magritte Add-ons repository: the
Magritte-Json package. It's definitely usefull functionality!
Jan.
On Mon, Aug 8, 2011 at 8:15 PM, Nick Ager <nick.ager(a)gmail.com> wrote:
Hi,
I'm experimenting with a JSON converter for objects with Magritte
descriptions. So far I've added the following to GRObject:
jsonOn: aStream
| description |
description := self description.
description children isEmpty ifFalse: [
| first |
first := true.
aStream nextPut: ${.
description do: [ :each |
first
ifTrue: [ first := false ]
ifFalse: [ aStream nextPut: $, ].
aStream
json: each label;
nextPut: $:;
json: (each accessor read: self) ].
aStream nextPut: $} ]
you can then generate JSON from an object, for example:
((PRPage named: 'examplePage') contents: '!!Hello', String crlf,
'Hello
""world"" check') asJson
gives:
'{"Name":"examplePage","Visibility":false,"Navigation
Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain
Text":"Hello\rHello world check","Environment":null,"Style
Sheet":null,"Shortcut Icon":null,"CSS Classes":null}'
The method fails with recursive structures, but otherwise is appears to
work well.
Does this look like a sensible approach? Has anyone else implemented
anything similar?
Thanks
Nick
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
9 Aug
9 Aug
6:58 a.m.
2011/8/8 Nick Ager <nick.ager(a)gmail.com>om>:
Hi,
I'm experimenting with a JSON converter for objects with Magritte
descriptions. So far I've added the following to GRObject:
jsonOn: aStream
| description |
description := self description.
description children isEmpty ifFalse: [
| first |
first := true.
aStream nextPut: ${.
description do: [ :each |
first
ifTrue: [ first := false ]
ifFalse: [ aStream nextPut: $, ].
aStream
json: each label;
nextPut: $:;
json: (each accessor read: self) ].
aStream nextPut: $} ]
you can then generate JSON from an object, for example:
((PRPage named: 'examplePage') contents: '!!Hello', String crlf,
'Hello
""world"" check') asJson
gives:
'{"Name":"examplePage","Visibility":false,"Navigation
Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain
Text":"Hello\rHello world check","Environment":null,"Style
Sheet":null,"Shortcut Icon":null,"CSS Classes":null}'
The method fails with recursive structures, but otherwise is appears to work
well.
Recursive structures don't work in JSON in general.
Does this look like a sensible approach? Has anyone
else implemented
anything similar?
There is Magritte-Json in [1]. It gives you more control, you can
override the name of a property and choose not to serialize certain
objects. I found this necessary when implementing certain predefined
APIs. It's a bit more "magritty" in the sense that is uses reader and
writer objects. Though it could certainly be improved on. You can find
examples in [2].
[1] http://source.lukas-renggli.ch/magritteaddons
[2] http://www.squeaksource.com/orion
Cheers
Philippe
12:12 p.m.
Hi Philippe,
There is Magritte-Json in [1]. It gives you more control, you can
override the name of a property and choose not to
serialize certain
objects. I found this necessary when implementing certain predefined
APIs. It's a bit more "magritty" in the sense that is uses reader and
writer objects. Though it could certainly be improved on. You can find
examples in [2].
[1] http://source.lukas-renggli.ch/magritteaddons
[2] http://www.squeaksource.com/orion
It looks good and more comprehensive than my effort.
It appears that objects have to be derived from MJObject in order to use the
Json conversion. Would there be a problem moving the #javascriptOn: method
from MJObject to an extension method on GRObject to allow more objects to
gain the Json conversion functionality? (I choose GRObject as WAObject,
PRObject & MAObject are all ultimately derived from GRObject).
The difference between #asJavascript (with it's
accompanying #javascriptOn:), asJson (with it's accompanying #jsonOn:)? It
appears that even though #asJavascript and #asJson have largely the same
effect, #asJson implements a Json compatible subset of #asJavascript. Would
it not make sense to use #asJson instead of #asJavascript and #jsonOn:
rather than #javascriptOn:, or have I missed something?
Cheers
Nick
6:48 p.m.
2011/8/9 Nick Ager <nick.ager(a)gmail.com>om>:
Hi Philippe,
Without being certain I don't think so. It should work with any class
that has the same methods.
There is Magritte-Json in [1]. It gives you more
control, you can
override the name of a property and choose not to serialize certain
objects. I found this necessary when implementing certain predefined
APIs. It's a bit more "magritty" in the sense that is uses reader and
writer objects. Though it could certainly be improved on. You can find
examples in [2].
[1] http://source.lukas-renggli.ch/magritteaddons
[2] http://www.squeaksource.com/orion
It looks good and more comprehensive than my effort.
It appears that objects have to be derived from MJObject in order to use the
Json conversion. Would there be a problem moving the #javascriptOn:
method
from MJObject to an extension method on GRObject to allow more objects to
gain the Json conversion functionality? (I choose GRObject as WAObject,
PRObject & MAObject are all ultimately derived from GRObject).
No.
The difference between #asJavascript (with it's
accompanying #javascriptOn:), asJson (with it's accompanying #jsonOn:)? It
appears that even though #asJavascript and #asJson have largely the same
effect, #asJson implements a Json compatible subset of #asJavascript. Would
it not make sense to use #asJson instead of #asJavascript and #jsonOn:
rather than #javascriptOn:,
Yes.
or have I missed something?
No.
Feel free to change your proposed changes. I might also make sense to
move over some of the orion tests.
I hope you don't have to change your slides now ;-) I'm sure you're
also aware of Magritte-XMLBinding in the same repository that does XML
data binding.
Cheers
Philippe
10 Aug
10 Aug
8:39 a.m.
Hi Philippe,
Feel free to change your proposed changes. I might
also make sense to
move over some of the orion tests.
I've checked in Magritte-Json-NickAger.10 and I've modified Orion, but
couldn't check it in (permission issue) so I've attached my changes.
Cheers
Nick
13 Aug
13 Aug
6:24 p.m.
Great the magritte json binding exists. I need it and thought I need to build it myself.
Can't wait to return from my vacation (ok, not really true) to test it.
I will use it together with the conumes (accept-...) feature you added to seaside-rest.
That's a nice example on how do multiformat web APIs.
Great stuff,
Norbert
Am 09.08.2011 um 06:58 schrieb Philippe Marschall <philippe.marschall(a)gmail.com>om>:
2011/8/8 Nick Ager <nick.ager(a)gmail.com>om>:
Hi,
I'm experimenting with a JSON converter for objects with Magritte
descriptions. So far I've added the following to GRObject:
jsonOn: aStream
| description |
description := self description.
description children isEmpty ifFalse: [
| first |
first := true.
aStream nextPut: ${.
description do: [ :each |
first
ifTrue: [ first := false ]
ifFalse: [ aStream nextPut: $, ].
aStream
json: each label;
nextPut: $:;
json: (each accessor read: self) ].
aStream nextPut: $} ]
you can then generate JSON from an object, for example:
((PRPage named: 'examplePage') contents: '!!Hello', String crlf,
'Hello
""world"" check') asJson
gives:
'{"Name":"examplePage","Visibility":false,"Navigation
Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain
Text":"Hello\rHello world check","Environment":null,"Style
Sheet":null,"Shortcut Icon":null,"CSS Classes":null}'
The method fails with recursive structures, but otherwise is appears to work
well.
Recursive structures don't work in JSON in general.
Does this look like a sensible approach? Has
anyone else implemented
anything similar?
There is Magritte-Json in [1]. It gives you more control, you can
override the name of a property and choose not to serialize certain
objects. I found this necessary when implementing certain predefined
APIs. It's a bit more "magritty" in the sense that is uses reader and
writer objects. Though it could certainly be improved on. You can find
examples in [2].
[1] http://source.lukas-renggli.ch/magritteaddons
[2] http://www.squeaksource.com/orion
Cheers
Philippe
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
4638
days inactive
4643
days old
6 comments
4 participants
participants (4)
-
Jan van de Sandt -
Nick Ager -
Norbert Hartl -
Philippe Marschall