If you end up altering Sortables, I expect Thomas Fuchs would be interested in your patch.
As you're married to the drag/dop, may I suggest the following: If order in the list doesn't matter, don't use Sortables at all; make each li spawn a root-level Draggable on click, and make the two list (ul) tags Droppable. This will get around the scroll problems, and the script will be faster as there are fewer Droppables to iterate through. (The slowdown for Sortables is more pronounced as the lists get longer, because each list item is also a droppable.) Best of luck. TAG On May 2, 2007, at 9:48 AM, Matt wrote: > Thanks TAG, I appreciate the response. I did search around before > posting, apologies to all for regurgitating a known feature. > > Also thanks for the work around suggestions, but we tried to push > those options during the design phase. So they'll get what they asked > for! > > On May 1, 2:20 pm, Tom Gregory <[EMAIL PROTECTED]> wrote: >> This issue comes up every month or so. >> >> What you're experiencing is a "feature" with Sortables >> implementation, caused by the CSS spec. The draggable is a child of >> the list, which is scrollable. Thus, the drabble must necessarily be >> bound to the same scroll region as its parent. When you drag over to >> the new list, you're altering it parent to be the new list. If you >> want to try and hack scriptaculous to get around this, the you'll >> need to make the draggable a child of some element higher in the >> hierarchy than the list. >> >> There are some better ways to get the functionality you want w/o >> drag/ >> drop anyway. The simplest is to just use select boxes, with >> directional arrows in the middle (you can also have the list items >> respond to double-click events). If you're wanting something more >> fancy, do a styled list with arrows to the right of each list item. >> Then all the user has to do is click to move the item over, rather >> than drag. It's significantly more efficient if order doesn't >> matter, especially when moving multiple items back and forth. >> >> TAG --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
