Ahem. :) I kind of assumed that the "sling:resourceType" property was magic, and anything inside it would something that could be rendered in a browser. Maybe not.
I think that one of the problems in learning Sling is that it seems to be infinitely configurable, so that you can add renderers for things on the fly, et.c. But if I say it this was; If there is some kind of basic type in Sling for content to be consumed in a browser, then that could reasonably be decalured to be of type urlencoded String. Would that be OK. Also, for my current project (Bunkai editor for Sling), I don't really need the content int he json structure, I only need the hierarchical structure, in array format already described, and some unique id/name that I can use later, when a treenode (in Dojo) is sleected, to get the actual content. Cheers, PS On Jan 22, 2008 12:07 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > On Jan 22, 2008 11:53 AM, Peter Svensson <[EMAIL PROTECTED]> wrote: > > > ...The 'meaning' of a property value is application domain specific > anyway, so > > I think we can choose any encoding type which is reasonably simple, as > long > > as it is documented clearly.... > > But how do you decide (in the general case, with the default JSON > renderer) which properties to escape() and which to send out > unescaped? > > And how do you tell the client (dont' say "configuration" please ;-) > which ones are escaped? > > -Bertrand >
