Widgets

[colinjbrown]

From @dakoop on June 28, 2018 20:8

After playing around with ipywidgets, I have some thoughts on making them work with dfkernel.

1. Widgets should be shown with labels like other outputs (need to redo the widget-specific output area stuff to show the tag), not sure if having them be execute_results or display_datas is a big deal
2. A widget's value should be referenced just using the the name of that widget, x not x.value as is currently done. Any needs for things like links, jslinks, etc. can be done with some type of widget() call or something.
3. Every widget should have an observer that triggers execution if necessary. Users should also be able to use an interact_manual analog so that execution is only triggered when a button is clicked
4. Downstream use of a widget's value is then as simple as y = x + 4

Copied from original issue: colinjbrown/dfkernel#42

[colinjbrown]

From @dakoop on July 3, 2018 20:15

Note that when jupyter-widgets/ipywidgets#2021 is merged into ipywidgets, we get labeled, execute_result widgets.

[colinjbrown]

Apparently we do something weird with ipywidgets now, not sure if we always did but a
h = j.value +3 seems to cause issues because we appear to be trying to look inside the IntSlider object?

[colinjbrown]

I can't confirm this is still an issue, on the most recent version this does not appear to still be occurring will leave this open in the event someone else is able to confirm.