feat(ui5-list): enable drag and drop for multiple items

[dobrinyonkov]

TBD

[aborjinik]

Why does it have to be so specific to the List? I would have expected something that every component could also benefit from, especially since the multi-drag ghost is quite a generic concept.

[aborjinik]

Thanks for your efforts on the table component but I must say I still find the current code integration for dragging multiple items overly complex. Before moving further, I suggest to discuss this in the smaller sync we have on Tuesdays and Thursdays. If this topic has already been covered, sorry I sometimes miss sessions due to parallel meetings.

IMHO, instead of introducing something like a movingItemsCount property on the component itself, we could expose an API e.g. DragRegistry.setMovingItemsCount(dragstartEvent, count/text) (if the dragstart event is not already stored by the DragRegistry)

This approach leaves the drag ghost handling to consumers via native dragstart event as would be expected in vanilla drag & drop implementations.

Let me know what you think, as mentioned we can discuss this in the sync meeting.

[dobrinyonkov]

Thanks for your efforts on the table component but I must say I still find the current code integration for dragging multiple items overly complex. Before moving further, I suggest to discuss this in the smaller sync we have on Tuesdays and Thursdays. If this topic has already been covered, sorry I sometimes miss sessions due to parallel meetings.

IMHO, instead of introducing something like a movingItemsCount property on the component itself, we could expose an API e.g. DragRegistry.setMovingItemsCount(dragstartEvent, count/text) (if the dragstart event is not already stored by the DragRegistry)

This approach leaves the drag ghost handling to consumers via native dragstart event as would be expected in vanilla drag & drop implementations.

Let me know what you think, as mentioned we can discuss this in the sync meeting.

Thanks @aborjinik for this feedback! We've discussed this a few times during the sync meetings and decided to go with that approach. However, I will look into your suggestion and bring the topic once again for discussion. :)