I don't if this is viable in the current UI implementation but it seems that
we have 2 optimal solutions for 2 different scenarios - fewer interfaces
lot of interfaces. Can't we have both implementations? Depending on
how many interfaces we must show we can use one approach or the other.
If it's not feasible then I vote for this one:
"IMO the default html control looks better and it delivers a better user
a dropdown. We can “destroy” Bootstrap-Select style and widget if a VEPA
is selected and customize the default html control with CSS3 to look
like other form
I believe that this scenario of having hundreds of interfaces to show is
a corner case
for Kimchi. Most of the time we'll be handling < 30 interfaces.
On 03/18/2016 06:09 PM, Samuel Henrique De Oliveira Guimaraes wrote:
I was looking into Bootstrap-Select that is already implemented on Wok
and it does allows multiple option selection, which means we can use
it to select more than one interface when creating a new Vepa network.
But instead of looking like a default multi-select input, it keeps the
default style and puts the selected items separated by comma:
In the other hand, this is what a multiple select looks like with
native HTML controls:
IMO the default html control looks better and it delivers a better
user experience than a dropdown. We can “destroy” Bootstrap-Select
style and widget if a VEPA network type is selected and customize the
default html control with CSS3 to look like other form elements.
However, what if there are hundreds of interfaces? In this case I
propose we keep Bootstrap-Select with a search/filter on top, which
would work like this jsfiddle:
Any thoughts or comments?
Kimchi-devel mailing list