01_getting_started
Opened this issue · 2 comments
- Benefits of Jupyter & JupyterLab outline
- Flesh out benefits of Jupyter
- Flesh out benefits of JupyterLab
- Change a trait that isn't
value - Draft coding parts
- Pull in answers from file
Would be nice:
- Find a way to print errors but keep executing code cells with
restart and run all
Okay, I was thinking about fleshing out the OOP traits example more to include a minimal example. Like a model calculates a square root with a view that has a slider and text. I still think this is a good idea, but I think it belongs later in the tutorial. Before we get into the OOP stuff somewhere in the second half. There's currently an empty notebook called 06_oop.ipynb. I may want to update that to 06_model_delegate_design, because I think it makes sense to introduce them together. This is issue #22.
On the other hand, I may want to introduce container widgets in getting_started. It's quick to add and I can showcase the common tuple error.
Checked off most boxes with 8b57716. Still need to add more text to motivation. And add a way to pull in answers from file.