Currently I store the child order information in the child properties. This means the child hold a ‘sort’ property which shows how to to sort this node into the list of children nodes.
This strategy shows a lot of problems. First of all if I try to change the order I have to change all child nodes. This could end in a access denied problem if I do not have access to one of the child nodes. Second if I move the child node a stare ‘sort’ parameter will maybe disturb the new order information.
Therefore the best and mostly not used strategy is to store the order information at the paren node. If you are able to write the parent node, you are able to reorder the children of the node. And you are not forced to change these ones.
I should implement it in cherry web soon in this way!