Looking at the widgets in https://github.com/panel-components/panel-fast/blob/main/panel_fast/widgets.py they seem like minimum implementations supporting the basic api of the fast widget. My take is that panel-fast widgets should be able to replace the Panel widgets. I.e. there should be IntSlider, FloatSlider etc. It should have labels, hover etc.
Some kind of guidance in the README regarding the vision and design principles addressing the above would be nice.
A start would just be your vision and guiding design principles in a comment below @philippjfr . Thanks.
Looking at the widgets in https://github.com/panel-components/panel-fast/blob/main/panel_fast/widgets.py they seem like minimum implementations supporting the basic api of the fast widget. My take is that panel-fast widgets should be able to replace the Panel widgets. I.e. there should be IntSlider, FloatSlider etc. It should have labels, hover etc.
Some kind of guidance in the README regarding the vision and design principles addressing the above would be nice.
A start would just be your vision and guiding design principles in a comment below @philippjfr . Thanks.
For now I will be exploring some Fast components using ReactiveHTML here https://github.com/MarcSkovMadsen/panel-components/tree/main/src/panel_components/fast/widgets and I also have some existing bokeh extensions here https://github.com/MarcSkovMadsen/awesome-panel-extensions/tree/master/awesome_panel_extensions/frameworks/fast
For example should the
button_type
because the Panel button has this property?bar_color
anddirection
even though its not supported out of the box.show_value
adding a label withname
andvalue
.formatting
. Also using Bokeh Formatter?My take is that the priority is
1) Support Fast interface 2) Support basic Panel interface that enables use with
pn.Param
3) Support remaining Panel interface where it makes sense.My take after exploring panel-components across frameworks is that