1) Users are defining information into simple form where is will be easier to allow them to create hierarchy... About nestedSortable as long as it is well supported by the owner of the project no problem about the js plugin used.
2) Bill Karwin lecture convinces me that it was the cleaner way of doing thing. Also, my data are already structured that way. The relation between node are not going to move that much (not move at all once establish), it may happen that when node will be created there will be mistake that will need to be corrected, but then no change will happen (that may have no consequence on the programmation since the moving of subnode are be required anyway). Thanks Richard On Thu, Sep 20, 2012 at 2:00 PM, Vasile Ermicioi <[email protected]> wrote: > may I ask a few questions > > 1) (a suggestion) > why do you need multiselect if jstree already support drag drop? > http://www.jstree.com/documentation/dnd# > and I didn't see a better way to manipulate hierarchical data than what it > offers > an alternative is nestedSortable > http://mjsarfatti.com/sandbox/nestedSortable/ but when you want to move a > node with a lot of children it has poor performance > > > 2) (interested because I did research some time ago on that field) > why did you chose closure data model? > > -- > > > > --
