Non-jquery slider

[jasongrout]

Looking at slider options, here is a simple slider that appears to satisfy our needs: http://refreshless.com/nouislider/ (basic typescript definitions here: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/nouislider/nouislider.d.ts)

@SylvainCorlay, @jdfreder, @afshin - what do you guys think of moving to use nouislider?

Another possibility is to use the browser sliders (they are pretty much standardized now, though the UI customizations vary greatly: https://css-tricks.com/styling-cross-browser-compatible-range-inputs-css/. The problem there is that we wouldn't have range sliders, which would be a regression.

[SylvainCorlay]

👎 on native browser sliders because of absence of range sliders that are used a lot.

[SylvainCorlay]

nouislider seems to only be about range sliders.

[SylvainCorlay]

Re: the current jquery ui slider, I just wanted to communicate that there is no problem with having jquery-based widgets.
It just happens that the slider is the only core widget to make use of jquery and it is the only reason why jupyter-js-widgets depends on jquery.

[jasongrout]

and jquery-ui...

[jasongrout]

nouislider has range sliders, but it's not only about range sliders...

[afshin]

noUiSlider seems reasonable enough to me. I don't have any experience with it, but it doesn't seem bloated to me, which is my main concern about external libs.

It might seem silly to ask, but are we cool with WTFPL?

[jasongrout]

I looked into the license a bit. Wikipedia has a bunch of links where the FSF acknowledges it, it seems that various people (whatever that's worth) say it is basically a public domain dedication. The license author even says you can relicense work ("The WTFPL lets you relicense the work under any other license." on http://www.wtfpl.net/faq/), so even if we're not happy with it, it seems we can change the license and maintain a fork.

[jasongrout]

This would also probably fix #655.

[dakoop]

Apparently, new HTML specs have a "multiple" attribute for range sliders, and there is a polyfill: http://leaverou.github.io/multirange/

[SylvainCorlay]

@jasongrout the one-value HTML5 sliders works well and seems to be pretty well supported across the board. I started working on this in the plane for Austin.

However this will probably require us to have a well-separated view for the range...

[gnestor]

@SylvainCorlay Do you think it makes sense for me to try out this multirange polyfill for the native HTML slider? Another thing to consider: If we are going to replace the jQuery slider with a native one, should we not do the same for Dropdowns and Progress widgets? If so, then I think it would make sense to address the

Give the widgets a facelift. Maybe material-ui? Home spun design?

roadmap item at the same time and implement a consistent style across both native and non-native elements.