Figure widget update

[michaelbabyn]

This is the PR for updating the graphwidget documentation to plotly.py version 3's FigureWidget for this issue.

• Interactive Data Analysis with ipywidgets
• FigureWidget overview
• Interact notebook
• Create New Window with Jupyter Lab
• Slider Widget with Plotly
• Using Mouse Events with Plotly FigureWidget
• Adding Zoom Effects
• Hover Events
• Click Events
• add thumbnail gifs

[Kully]

@michaelbabyn gonna have a look now

[Kully]

Overview

You should combine this two code blocks and put the Create an empty figurewidget... markdown cell in the same markdown cell for the title:

i.e.

#### Create a Simple FigureWidget Create an empty figurewidget and then view it 

import plotly.graph_objs as go f= go.FigureWidget() f 

As a general rule, it is better to combine more code together, unless you specifically want to print multiple things in each code cell. An example of this is further down in the this doc:

[michaelbabyn]

@Kully , I'll go back through these and see what I can merge and I'll get rid of that superfluous output from updating the figureWidget but I think it makes sense to keep the updates separated to help demonstrate that each code block will instantly update the graph. See below for what I mean.

[Kully]

See below for what I mean.

no, you're absolutely right. I was a little unclear in my first comment. The second picture was demonstrating a Good use of small code chunks to show the functionality of adding different trace types.

[Kully]

there should not be this much white space between the param and arg:

figure = go.Figure( data=data, layout=layout ) 

[Kully]

Jupyter Lab with FigureWidget

you're not your

[Kully]

Interact Decorator

put a period at the end of this sentence

---

You should put an empty chart in here

---

[Kully]

Slider Widget

Important note for all docs. The structure of our imports are like this:

# import import plotly ... ... from plotly import ... # non-plotly imports import ... 

See the scatter plot doc for an example of this.

---

PEP-8 - same comment from previous section:

widgets.FloatRangeSlider( min=xmin, max=xmax, step=(xmax - xmin) / 1000.0, ... ) 

---

Same comments for the rest of this doc.

[Kully]

DashShader Case Study

period at the end of sentence:

---

Combine these 3 cells together

---

same here:

[Kully]

Click Events

separate the imports as explained above

*Short and Sweet - very good 👍

[Kully]

Selection Events

• separate the imports here too
• add a brief description after the title about what the doc is doing.

Car Exploration

The Load cars dataset should not be so big. It should be an header4 (4 #s in markdown):

#### Load cars dataset

and Cars dataset exploration with plotly.py version 3.0 should not be an empty section like that as it shows up in the sidebar like a normal section.

---

this cell needs to be run. the image is not showing up in the doc

---

same comment about collecting import lines together

there is no output under fig. Do you have an image/GIF of what the fig should look like here?

---

Notice Quantization section should not be its own section. The Notice Quantization and Apply Jitter sections should be one section. I suggest using Apply Jitter as the section title and then writing a little description underneath that says something like "Notice that the data values are quantized. We can apply jitter to the scatter points to get a better sense of how many there are..." etc

---

Again, Looking for Outliers is a blank section.

---

All headers should be h4s

eg.
### Section Title

Bringing it all together is not h4.

[michaelbabyn]

@Kully , I made the changes you mentioned in all but the "case study" docs (since those are just Jon's with GIFs to show off the widget and I think it makes sense to leave them as they are). So I think this should be good to merge. What do you think?

[Kully]

@michaelbabyn It looks like you did at least some of the grammar edits, but my comments about the headers in Car Exploration are still not addressed.

Send me a message if you are confused about what I am asking and I can clarify.

[jackparmer]

@michaelbabyn @cldougl People are still sharing the old GraphWidget-
https://twitter.com/elenamdata/status/1042148777782665216
When are these new replacement docs using FigureWidget going to be merged? We're creating a lot of confusion IMO with v3 using FigureWidget but the docs using GraphWidget which is basically deprecated

[michaelbabyn]

I think they can be merged ASAP, @Kully wasn't sure if we should keep one of Jon's docs in there as is since it is quite different stylistically from the rest of the docs but that's all that's blocking.

[jackparmer]

... wasn't sure if we should keep one of Jon's docs in there as is since it is quite different stylistically from the rest of the docs but that's all that's blocking.

Yeah, we shouldn't let that hold this up. Please merge & deploy today with either Jon's doc or a modified version that is more stylistically similar.

[cldougl]

@jackparmer I told michael to wait until this could be reviewed before merging. @michaelbabyn feel free to merge now and we can deal with the styling later

[jonmmease]

Has this been deployed yet? I'm still seeing the old GraphWidget stuff in the "Custom Controls with JavaScript" section.

Thanks for all your work on this @michaelbabyn!