Nested Sortables?

[toanjo]

Hi! Great work with this project, it's really good.

I was wondering if nested sortables are a possibility? For example, if I have a list of parent items and child items and I would like to sort the parents between each other or sort their children.

I am using React and have experimented with creating two different sortable objects but haven't been able to make it work as they conflict with one another. Is this not possible at this point or is it my mistake?

Thanks!

[tsov]

Thanks for asking! We are planning to build a NestedSortable module or bake nesting into the existing Sortable module, but this is planned for post stable release. No ETA for this yet unfortunately

Related: #56

[saluton-mundo]

This would be awesome, currently using an adapted version of the retired(?) https://github.com/angular-ui-tree/angular-ui-tree . Happy to help with the logic if you'd like

[Lewiscowles1986]

You have the handle property, so this does support nested drag & drop currently in the event that the parent list at-least has a handle property corresponding to a non-sortable sub-element.

The only problem I'm having is setting this to work nested is when I add another group for sub-items to be transferable between upper level lists. Like a KanBan.

https://codepen.io/Lewiscowles1986/pen/YvgPgP

I did think about adding the selector for the last list, but then the append action is off too. It's just a quick evaluation to see if this is capable of replacing jQuery UI sortable (it's so close).

[fdietze]

Nesting is already possible with the current Sortable:

https://jsfiddle.net/zodqmx09/6/

[Lewiscowles1986]

It's possible, but a bit of a dead end if you can only sort static elements, not receive new ones. Some form of mutation observer is probably needed.

[fdietze]

You can create and patch the elements with a virtual dom library (like e.g. snabbdom). I just built a nested kanban-board with this technique.

[Lewiscowles1986]

are there tomes of the internet containing the incantations to work such magic?

[fdietze]

I'm sorry, I don't understand what you intend to say...

[beefchimi]

You can create and patch the elements with a virtual dom library (like e.g. snabbdom). I just built a nested kanban-board with this technique.

@fdietze that sounds really cool! You don't happen to have a repo / example you could point to by chance?

[Lewiscowles1986]

It's certainly the last time (this week) I'll try asking anything in a funny way.

@fdietze what @beefchimi just said.

[fdietze]

@Lewiscowles1986 I apologize for not getting the joke. I'm not a native english speaker. Please don't stop making humor because of language barriers. 😉

The kanban board I built is very wired with my project written in Scala, so this would probably not be a helpful example. But I'll try to explain it in more detail here instead:

• Create one Sortable instance for the whole kanban-board.
• To display a nested kanban board, you obviously have to store your data in a tree.
• You can traverse this tree recursively and create virtual dom. For inner nodes of the tree you create (sub-)columns which contain more sub-trees. For the leafs you create cards. Create the dom with the necessary classes to make Sortable work.
• Store ids or references to your nodes in the tree in data-attributes.
• In Snabbdom you can use insert hooks to add the containers to the Sortable instance. In React this would be done via lifecycle hooks. Add each (sub-)column as a container.
• Listen to sortable:sorted of the Sortable instance to react to dropped elements. From this event you can extract the ids of the element, the source and the target container from their data attributes. Use these ids to change your tree data structure.
• Re-render your kanban-board with your updated tree.

Just ask, if a step is unclear.

[Lewiscowles1986]

Hi @fdietze,

I think what I'm doing is probably incompatible with that. For one at the moment I'm not backing anything anywhere so tree structure really doesn't matter (If it's a tree it's a darn special one). I have an example of this working without virtualdom, it just has bugs, it's probably the listening to the sortable:sorted of the Sortable instance that will resolve them. Right now I remove the listeners before adding the sortable and then re-add sortable. that's obviously not ideal should I take it further.

The strange thing is that it works when I have just one instance of Sortable, however I also want to be able to change column order. I think I'll end up just adding nav-button overlay to each to ease the burden of drag-and-drop. It'll achieve the same end result without too much technical debt and up-front decision making.

• Up down buttons for sibling exchange (easy)
• left right buttons for column-list exchange (easy)
• maybe a state for ad-hoc movements.

I started because I'm using WeKan at work. It's heavy for what it is and I'd prefer to store in markdown with a small helper to detect kanban layout. That way it's lightweight and doesn't need a formal storage. One person can be in-charge of full-edits to a board. YMMV

[molfar]

All these examples does not work as expected. Waiting for native nested support very much.

[Spone]

Me too! How can we help?