A Sortable is a special case combination of a Draggable and a Droppable. A Sortable may be dragged into another Sortable as long as both lists include the other in their "containment" property. But there is no equivalent to Draggable's revert in a Sortable.
In my work, I found that while you could drop a draggable onto a sortable, you couldn't get the dropped element to join the sortable explicitly. I took a run up this mountain a couple of months ago, and the best I was able to do was to make a set of draggables, wrap the sortable in a parent which I made droppable, and set revert to true on those draggables. On a successful drop, I would generate a new element, insert it into the sortable, re-initialize the sortable, and then the user would need to drag the new element into position within the list. What WLQ would like (what I would like, too) is something more direct. A set of draggable options that can be dragged into a sortable, revert back to their parent, and leave a clone behind in the position within the list where they were dropped. This is not possible as far as I've been able to do it. Getting the unique ID either from Prototype or MySQL is trivial, and not really the actual problem here. Walter On May 28, 2009, at 12:11 PM, Alex McAuley wrote: > > Also .. isnt there ghosting or "revert" on droppables to make the > elements > go back into the container of which they were dragged from .... If > so - this > removes half of the problem .. the only problem left is ordering the > second > list which is done on dropend or whatever the syntax is ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
