> > In my architecture, nodes point up to their parents. How do you maintain sibling order?
I've been settling on node "addresses" in metadata, it's a list of child indexes. It provides each node with a self contained description of where it lives, which I like. I haven't come across a more succinct way to do that. You access all > the nodes for a context, and they come with pointers to their parents, > and maybe the server can traverse that and give them to you in outline > order, or you can do that locally once the server just provides the > relevant nodes. > > >> At present, I don't see a good way forward. That's ok: I've got bugs to fix >> ;-) > > > :-) > > > Seth > > >> Edward >> >> -- >> You received this message because you are subscribed to the Google Groups >> "leo-editor" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/leo-editor?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/leo-editor?hl=en. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
