I'm right now developing a taxonomy system and I was in need of a tree that would be stored at server with UI at client - I think quite common requirement, right? I've done it already before for various trees, e.g. my FileTreePanel.
I've been too lazy to write the same code again and again so I put all basic operations into extension: Ext.ux.tree.RemoteTreePanel. The extension doesn't change appearance or behavior of the standard Ext.tree.TreePanel too much but it implements the following logic:
1. User makes a change of the tree (create node, rename node, delete node, D&D node)
2. Request is sent to server to execute, save this change.
3.a) Update GUI on success
3.b) Revert GUI to previous state on failure + display error message delivered from server.
All your comments, bug reports or ideas for improvements are welcome.
Note: I cannot publish the backend of the example so it makes no sense to ask me for it. Of course, you are free to analyze what is sent to the server and what comes back and to implement your own server solution.
Thanks for reply.
Yes, preordered tree (nested as I mentioned) is also my choice.
By adjucency model I simply ment parent/ child relationship maintained through parent_id only.
I am thinking about this MU issue, but then I wonder if this is realy something I should spend much time on... this may rarely happen and I guess simple error message and refresh would do. Would you agree?