Hi, I'm attempting again to grok how to write a new version of
JsonItemWriter, et.c. But I think I need to download the whole thing,s ince
I only have a version of usling at the moment.
I've tried to look in the docs for a checkout and build process, but
couldn't find one. COuld someone point me o
On Jan 21, 2008 3:41 PM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...I've tried to look in the docs for a checkout and build process, but
> couldn't find one. COuld someone point me out to some info on this?...
Install a Java 5 JVM and Maven (I use 2.0.7).
Checkout with an svn client from
ht
On Jan 21, 2008 3:55 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> ...Checkout with an svn client from
> http://svn.apache.org/repos/asf/incubator/sling/trunk/...
Note that the launchpad stuff is broken in the current HEAD revision
(see SLING-154), if you want to try it before we fix that
Hmm. I should know by now what Launchpad does, but am I right in assuming
that that means that esp parsing while be disabled as well?
Cheers,
PS
On Jan 21, 2008 6:06 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> On Jan 21, 2008 3:55 PM, Bertrand Delacretaz <[EMAIL PROTECTED]>
> wrote:
>
>
On Jan 21, 2008 6:14 PM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...Hmm. I should know by now what Launchpad does, but am I right in assuming
> that that means that esp parsing while be disabled as well?...
Not sure what you mean - the Launchpad works very similarly to
microsling-core, but ins
Thanks for you links. I must admit to being even more disoriented than that,
I'm afraid :)
I'm currently focusing on how to on either side convert the generated json
that describes a hierarchy of JCR nodes to be truly 'json' compliant, so
that I can just plug it in the Dojo Tree in bunkai.
But I h
Hi Peter,
On Jan 22, 2008 8:00 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...I did manage to checj out and build Sling alst night, and after a while
> realized that the faulty json stuff is probably due to the fact that
> javax.jcr.Property does not return tru when a property isMultiple(). O
Hi Bertrand,
The json that would be nice to have is something like this;
{
label: 'name',
identifier: 'name',
items:
[
{ name:'Fruit', type:'category'},
{ name:'Cinammon', type: 'category',
children:
[
{ name:'Cinammon Roll', type:'poptart'
Hi Peter,
(replied to the JSON part in a renamed thread to separate matters)
>... What I meant with not finding the source code to the JCR Property class was
> that i did a grep . -exec "javax.jcr.Property" {} \; -print and every
> file listed was one referering to it, not defining it, except
OK. Thanks, I'll have to debug anyway, to see where the oddities lie. it
really should create an array :)
Cheers,
PS
On Jan 22, 2008 10:30 AM, Bertrand Delacretaz <[EMAIL PROTECTED]>
wrote:
> On Jan 22, 2008 10:19 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
>
> > ...I wanted to look in the cla
Thanks!
But hmm. Maybe not, but I wanted to look in the class "javax.jcr.Property",
because it defines if a property is multiple or not (leading to the
generation of an array). However, I think that one could implement that
oneself. It's just that I have been coding in js only for nearly half a
ye
On Jan 22, 2008 10:19 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...I wanted to look in the class "javax.jcr.Property",
> because it defines if a property is multiple or not (leading to the
> generation of an array)
Ok - in the case of Sling we're only dealing with the Property
interface
Hi,
(renaming the thread to attract attention of our JSON folks)
On Jan 22, 2008 9:47 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...The json that would be nice to have is something like this;
>
> {
> label: 'name',
> identifier: 'name',
> items:
> [
> { name:'Fruit',
On Jan 22, 2008 10:08 AM, Bertrand Delacretaz <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> (renaming the thread to attract attention of our JSON folks)
>
Good idea. Thanks.
>
> On Jan 22, 2008 9:47 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> > ...The json that would be nice to have is something lik
hi,
i like the current "json node export" format since it seems to me more
natural (in respect to jcr).
regards,
philipp
On 1/22/08, Peter Svensson <[EMAIL PROTECTED]> wrote:
> On Jan 22, 2008 10:08 AM, Bertrand Delacretaz <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> >
> > (renaming the thread to att
On Jan 22, 2008 10:31 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...I personally prefer to just have object within objects. it's
> just that I have to translate the thing to a format that Dojo's Tree widget
> can consume
Ok, so IIUC Sling's default JSON format is ok, but you'd need a
diff
Yes, actually, I personally prefer to just have object within objects. it's
just that I have to translate the thing to a format that Dojo's Tree widget
can consume. So in that respect it makes more sense to translate it locally,
instead of changing the output from the server. Maybe to be able to ha
hi guys,
On Jan 22, 2008 9:47 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> DOJOTree vs. generic json tree
You are bringing up very good point.
First of all I think the default serialization should not include
"jcr:primaryType" (and other system props) and I still think that this
is something
Hmm. Good point. My reference page has been this;
http://www.json.org/js.html, and also teh RFC;
http://www.ietf.org/rfc/rfc4627.txt?number=4627 When reading that more
closely, they (or actually he - it's Douglas Crockford :) do actually
mention escaping of characters;
---
2.5. Strings
The
> > ...I personally believe that we should support a simple way for people to
> > get to different views of the same json (like the DOJO tree structure).
> > Now, I am not sure if we need to do that on the server side...
> That can be done on the client, sure, but I think we should support
> some u
On Jan 22, 2008 11:46 AM, David Nuescheler <[EMAIL PROTECTED]> wrote:
> > Bertrand:
> > Agreed, the convention would then be to use the last selector
> > (0,1,infinity) for the recursion level, and the selector before that
> > for the JSON "flavor".
> given our current resolving i think we actual
On Jan 22, 2008 11:04 AM, Peter Svensson <[EMAIL PROTECTED]> wrote:
> ...My reference page has been this;
> http://www.json.org/js.html, and also teh RFC;
> http://www.ietf.org/rfc/rfc4627.txt?number=4627 When reading that more
> closely, they (or actually he - it's Douglas Crockford :) do actuall
On Jan 22, 2008 11:04 AM, David Nuescheler <[EMAIL PROTECTED]> wrote:
> ...I personally believe that we should support a simple way for people to
> get to different views of the same json (like the DOJO tree structure).
> Now, I am not sure if we need to do that on the server side...
That can be
Hi,
I don't know enough about system particulars to recommend what to do, but
from a 'user' perspective, it would have been great to be able to have
several kinds of json renderings, to provide for different libraries. I bet
that YUI and Ext have different choices, for instance.
My first idea, wa
And, yes, that's also what I'm thinking. It doesn't matter in json what the
contents of a string is, as long as it doesn't mess with the json structure
itself (which it can do now).
The 'meaning' of a property value is application domain specific anyway, so
I think we can choose any encoding type
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 t
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 genera
hi guys,
i am still somewhat confused why we are looking into the whole
escaping issue. was there an actual issue at hand?
so far i have not experienced any issue with the current "escaping"
and i really would stay away from something like url escaping... i simply
don't see a need.
am i mistaken?
Hi,
Well, I think that the need for escaping chars exist because json is itself
just text, and if a proeprty value contains a lot of here and there for
instance, it will bork the value and also the client-side javascript
parsing.
This is normally no problem for simple values, when using Slin
Hi Everyone,
I'm just catching up with the discussion and think that we should make
sure to use properly escaped quotation marks, backslashes and
apostropes (which can be easily implemented using a Reader) instead of
relying on urlencode. The more portable and standard-compliant
solution
hi,
i agree with lars and david that there is no question how the escaping
is done. http://www.json.org/ defines this very clearly:
http://www.json.org/string.gif
when writing json through a standardized json-writer and reading it
with a standardized reader, there should not be any problem.
regar
Right, this was one of the big revelations when working with Cocoon's
Flowscript and it works here as well.
On 22.01.2008, at 22:14, Tobias Bocanegra wrote:
btw: in esp, it should be as simple as calling: object.toSource()
--
Lars Trieloff
[EMAIL PROTECTED]
http://weblogs.goshaky.com/weblo
On Jan 22, 2008 6:33 PM, Lars Trieloff <[EMAIL PROTECTED]> wrote:
> ...I'm just catching up with the discussion and think that we should make
> sure to use properly escaped quotation marks, backslashes and
> apostropes...
That should already be the case - I've just added some addition tests
to Js
33 matches
Mail list logo
