-
Notifications
You must be signed in to change notification settings - Fork 2
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
Multiple selection feature #10
Comments
This has always been on the possible feature list and very likely needed. The problem is then how we handle the |
I think there is a way to do that. As |
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. |
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. |
Arrived here when looking for a Vaadin replacement for Swing JList ListSelectionModel |
Hello, +1 for the multiple selection feature |
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. 😄 |
+1 I realize this wasn't the philosophy |
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: |
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. |
@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. |
Correct me if I'm wrong, @jouni: 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. |
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 |
@jouni, we can follow the same logic as with |
Basically, yes.
Yes, that should be the target, that all components that manipulate some selection would have the same API.
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.
Yeah, that looks good. That should align with Grid and Combo Box as well. |
Created a prototype for multi selection based on the conversation at this ticket. |
Several UX/DX tests participants would like to see multiple selection functionality in
vaadin-list-box
, so it will be possible to select multiple options by just addingmultiple
attribute tovaadin-list-box
. (Selection process similar to nativeselect-option
multiple selection)The text was updated successfully, but these errors were encountered: