Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain multiple lists #70

Open
cmbirk opened this issue Jan 10, 2013 · 6 comments
Open

Maintain multiple lists #70

cmbirk opened this issue Jan 10, 2013 · 6 comments

Comments

@cmbirk
Copy link

cmbirk commented Jan 10, 2013

A feature idea would be to drag elements between or in/out of lists

@josephdpurcell
Copy link

I absolutely agree. If anyone else has implemented this, do share!

@mjsarfatti
Copy link
Owner

What do you mean with it?
You can already connect lists with other Sortables, even though not with
Draggables...

2013/1/12 Joseph D. Purcell notifications@github.com

I absolutely agree. If anyone else has implemented this, do share!


Reply to this email directly or view it on GitHubhttps://github.com//issues/70#issuecomment-12178053.

@adamgruber
Copy link

Does this work between Sortable and NestedSortable? I can only get it to work between two NestedSortables.

Also, although I can drag from one list to another it doesn't update the tree classes until you sort the tree. Need a way to update the tree structure after receiving an item.

@Spiderkeg
Copy link

I tried a test to have Sortables handling the root items, while nestedSortables was handling the respective groups of children under each of the root items. I got it mostly working. The root items could be sorted amongst each other, but not involved with the children. Likewise, the children could be passed amongst the various groups under the root items.

The problems I encountered were, when I moved all of the sub-items from a <ol> the tag closed, preventing me from moving any further sub-items to that spot. Maybe this could have been solved with the use of an option, but I wasn't able to figure that issue out.

There was another bug in which sub-items could be moved to above a root item, effectively becoming a root item itself. After that, all of the CSS was stripped from that particular item and it was stuck until a page reload.

@mjsarfatti
Copy link
Owner

This root items stuff needs some working on I see, but I don't have time at the moment. If anybody wants to give a hand he/she is welcome!

@mjsarfatti
Copy link
Owner

The protectRoot option is fixed. You can sort root items only between themselves, and children can never become root items (in version 2.0).

I haven't tested dragging between Sortable and nestedSortable yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants