For questions, use https://discourse.holoviz.org/ instead! This chat is for informal discussions and debugging sessions with developers of the HoloViz.org tools (HoloViews, Datashader, Panel, hvPlot, GeoViews, Param, etc.), but user questions should go to the HoloViz Discourse site so that others won't have to ask them again.
philippjfr on pane_api
Fix image (compare)
philippjfr on pane_api
Small Image fixes (compare)
philippjfr on pane_api
Cleanup (compare)
philippjfr on pane_api
More cleanup Various fixes (compare)
philippjfr on pane_api
Further clean up mappings (compare)
NavigationList
. I've created an issue here holoviz/panel#1571
Question on naming conventions for alternative widgets in Panel. Should I add the name of the framework as a prefix to the widget class or just call them the same as in Panel?
For example: Button (Panel) vs MaterialButton, FastButton, WiredButton, SmartButton, UI5Button, ...?
or
For example: panel.widgets.Button, material.Button, fast.Button, wired.Button, smart.Button, ui5.Button, ...?
The reason for asking is that I would like to make it easy some day in the future to switch between the differents ones. For example if you are experimenting with the look and Feel. This includes trying out different frameworks as widgets parameter to pn.Param.
In the console I find:
Bokeh: ERROR: Unable to run BokehJS code because BokehJS library is missing