Multiple selection feature

[vaadin]

Multiple selection feature

[samiheikki]

Created a prototype for multi selection based on the conversation at this ticket.
PR: vaadin/vaadin-list-mixin#54

[heruan]

Vaadin definitely lacks a multi-select component. The only way to achieve this is using the grid, which is an overkill for a simple multi-select and doesn't always fit. Related issues:

• https://github.com/vaadin/vaadin-combo-box/issues/88
• https://github.com/vaadin/vaadin-select/issues/160

[jouni]

Vaadin definitely lacks a multi-select component.

Very much agreed. It’s more than sad IMO that one of the oldest issues for the whole component set is ”multi-select for combo box”.

The current plan is to work on a multi-selection component next quarter. We figured we’d start with combo box, as it has been there for a long time and we’ve seen the community and customers build their own versions of it already, so it seems the most requested one.

If you think we should start with list-box instead, please let us know.

[tamasnet]

+1

I realize this wasn't the philosophy vaadin-list-box was built on, but isn't single-selection a special case of multi-selection? 🤓

[jouni]

This has always been on the possible feature list and very likely needed.

The problem is then how we handle the selected property (and the possible value property). Does selected return an array when the multiple property is set? Not sure how nice that kind of API is, that we couple properties tightly together.

[yuriy-fix]

I think there is a way to do that. As multiple attribute in this case will introduce another way of selection functionality, we can introduce another property multiple-selected which will contain array of selected values. In the input part the items will be shown one by one with some delimiter (, | etc.)

[heruan]

Is this something we can expect out of beta? IIRC Grid also supports single/multi selection modes, List Box may handle this the same way.

[tomivirkki]

New features will need to wait for a minor release (after the stable is out). So this could be included in 1.1.0 earliest.

[oluwasayo]

Arrived here when looking for a Vaadin replacement for Swing JList ListSelectionModel

[BlackIsTheNewBlack]

Hello, +1 for the multiple selection feature

[robeden]

I could definitely see multi-selection making the (Flow, especially) API odd. Perhaps the best thing in that case would be "vaadin-multi-list-box" (or something) so the APIs wouldn't have to support both. In Vaadin 8, some of the APIs we quite strange from supporting both single and multiple selection.

But at the end of the day... the UI for this component with multiple selection is exactly what I want. 😄

[robeden]

@jouni - I think there’s room for both, so I have no objection to combo boxes. The only argument I’d make for this one is it seems quite a bit simpler (from a UX and implementation perspective) so it might take less time to complete.

[heruan]

Correct me if I'm wrong, @jouni: vaadin-list-box is used by vaadin-select, so this and vaadin/vaadin-select#160 are basically the same issue?

Talking about priorities, I think that if multi selection isn't implementent in both component during a short time frame, users might choose the wrong component just beacuase it has the feature (and the other not yet).

Multi selection is more a crossing-cut concern than a single-component feature and I'd like to see a common pattern used among Vaadin components.

[jouni]

but isn't single-selection a special case of multi-selection?

Yes, it is. Not sure why we did it like that with grid but then went the other way with list box.

Does anyone have opinions about the API? The suggestion in the description of using an additional multiple seems alright to me. Then the only trouble I see is in the value property, how that should be parsed into a valid selection (as it’s a string).

[yuriy-fix]

@jouni, we can follow the same logic as with selectedOptions and have separate property for multi-selection.

[jouni]

Correct me if I'm wrong, @jouni: vaadin-list-box is used by vaadin-select, so this and vaadin/vaadin-select#160 are basically the same issue?

Basically, yes.

Multi selection is more a crossing-cut concern than a single-component feature and I'd like to see a common pattern used among Vaadin components.

Yes, that should be the target, that all components that manipulate some selection would have the same API.

Talking about priorities, I think that if multi selection isn't implementent in both component during a short time frame, users might choose the wrong component just beacuase it has the feature (and the other not yet).

I understand the concern, but I’m not sure what we should do about that, except throw more developers at it 😄 Not sure if this is such a big concern that we can afford to put more hands implementing it for all the components at the same time.

we can follow the same logic as with selectedOptions and have separate property for multi-selection.

Yeah, that looks good. That should align with Grid and Combo Box as well.