Currently .interactive() assumes your pipeline is relatively fast. It will update every time you change a widget just a little bit.
But pipelines can be slow. It could be for example a machine-learning pipeline. Or a pipeline that starts with .bind() to load a lot of data from a slow database.
And if a user wants to change multiple widgets then it annoying with extra waiting time because the pipeline needs to run for each individual change.
Instead of updating on every change of one of the widgets a much better user interface in this case would be a form that only updates when the user clicks run, submit, train or similar.
An api could look like
.interactive(form=True)
And then a button would be added and the dependencies to the widgets would be changed.
Currently
.interactive()
assumes your pipeline is relatively fast. It will update every time you change a widget just a little bit.But pipelines can be slow. It could be for example a machine-learning pipeline. Or a pipeline that starts with
.bind()
to load a lot of data from a slow database.And if a user wants to change multiple widgets then it annoying with extra waiting time because the pipeline needs to run for each individual change.
Instead of updating on every change of one of the widgets a much better user interface in this case would be a form that only updates when the user clicks run, submit, train or similar.
An api could look like
And then a button would be added and the dependencies to the widgets would be changed.
Illustrative Example
Additional Info
Button
in order to later on layout his/ hers data app as he/ she wants with Panel.