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.
Hoxbro on opts_convenience_functions
Add convenience function to Opts (compare)
Hoxbro on opts_convenience_functions
Add convenience function to Opts (compare)
Hoxbro on opts_convenience_functions
Add convenience function to Opts (compare)
philippjfr on propagate_sizing_mode
Mirror pane options onto Replac… Reflect HoloViews sizing_mode o… Mirror pane options onto intera… (compare)
philippjfr on main
Bump pre-commit isort hook vers… (compare)
MarcSkovMadsen on excel-like-editing-table
enable copy fix whitespace (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.