Feedback from Cool Stars 21 focus group

[gully]

I'm here at Cool Stars 21 in Toulouse France with @kelle and @Will-Cooper and we are examining gollum.

1. What to call the interactive component

We currently call the ..show_dashoard a dashboard, but @kelle points out that this is misleading. At the currently time it is mostly a widget, due to the predominence of sliders. Eventually we may add more dashboard-like interfaces, so do we want to futureproof it or rename it? Kelle notes that whatever bokeh calls it could also guide the decision.

2. How/whether to connect to simple web app

Kelle likes the dashboard/widget! Yay! She argues that it should go on to the simple web app. We are now discussing the tradeoffs and design possibilities.

[gully]

We have boiled down the key question to the following:

Is it possible to support bokeh python callbacks in the browser outside of a jupyter notebook.

[Will-Cooper]

The main issue is deploying a bokeh server in the first place (in order to allow the gollum python callbacks), as opposed to the existing JS callbacks, see Deployment Scenarios

[kelle]

Looks like we can do python callbacks by running a Bokeh Server. The example is sliders and sliders.py

[kelle]

Golum functions need to be re-written so that there would be different functions for displaying to notebooks (output_notebook) vs current doc (curdoc).

[gully]

We'd probably want to split out the create_interact_ui() into its own interact.py module. Then show_dashboard would call it and the simple database would write a custom script to load it on their end. That's straightforward.