[
https://issues.apache.org/jira/browse/SLING-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572839#action_12572839
]
Felix Meschberger commented on SLING-280:
-----------------------------------------
Just a slight remark on the syntax: You say above (or before) without a
parameter would place at the beginning. While this sounds logical, it is not.
Converting this into clear text means something like "above nothing", which in
turn sounds more like bottom than top.
I would rather say, that before and after (rather than below and above) require
an argument. To place the new node in front of anything, we should use "front"
and to place the new node at the end we should use "tail" (or similar).
> ujax post serlvet should be able to insert new nodes at specified location
> --------------------------------------------------------------------------
>
> Key: SLING-280
> URL: https://issues.apache.org/jira/browse/SLING-280
> Project: Sling
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
>
> the current version only supports: ujax:order = 0, which orders a newly
> created node above it's siblings.
> suggest to implement the following variants:
> ujax:order= ("below" | "above" ) [name]
> example:
> /a
> /b
> /c
> ujax:order="above b" -> /a, /newnode, /b, /c
> ujax:order="above a" -> /newnode, /a, /b, /c
> ujax:order="above" -> /newnode, /a, /b, /c
> ujax:order="below b" -> /a,/b,/newnode,/c
> ujax:order="below c" -> /a,/b,/c,/newnode
> ujax:order="below" -> /a,/b,/c,/newnode
> Please note that JCR does not support the 'below' ordering and it's 'above'
> handling is different. but i think in scripting environment, where you loop
> over a list. the "below" makes sense, since you don't need to know the next
> list item when drawing the 'insert' form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
