On Wed, Sep 16, 2009 at 16:18, Jonathan Cook <[email protected]> wrote: > Might be better to wrap the entire object and avoid the pollution with the > "special" property: > > [ {name: "A", value: { ... }, {name: "B", value: { ... } ]
I think this doesn't work for ExtJs, because it expects objects = records that contain all the data already (assuming the properties of the node match that data). > Or better yet, write a function to do this client side which your JSON > object is passed to before you use the client lib on it: Good idea, since there might be other client-side libraries that expect their special format, I'd try and see if you can plug in a converter on the client side before changing sling. I think a different built-in rendering makes only sense if it is somewhat generic - eg. at least 2 use cases ;-) BTW, you could still add the custom list json renderer in a custom bundle - it doesn't have to be in the Sling code base, right? Regards, Alex -- Alexander Klimetschek [email protected]
