PygWalker is much more than just a thin wrapper around Graphic Walker. My understanding is that it
provides a client-server architecture which scales to larger datasets than what this solution will do, as it will be limited by Tornado, Jupyter or Kubernetes message size settings and by the Browser max memory limit. That is what I'm dreaming of and increasingly need.
Provides a python api that is nice and quick to use in a data exploration setting
Strategically PygWalker will support and upgrade the solutions in the PygWalker repository. They will also promote them. Panel will probably not be a part of that journey when building its own solution. Except if it provides unique and more powerful features.
PygWalker also supports bidirectional communication. Being able to get hold of the configuration is a key enabler for persisting the user selections.
Where Panel can really make a difference is if it scale interactively to very large datasets. Like Datashader for HoloViews/ hvPlot. Or like what we support for Tabulator. Or like I've requested for Perspective in https://github.com/holoviz/panel/issues/7359. Or like modern tools developed with a DuckDB backend - for example Marimo and Quack. Or like Vega-Fusion.
This is a great enabler 👍, but:
Please consider whether it will be a better long term solution to extend PygWalker instead like its done for Jupyter, Gradio and Streamlit https://github.com/Kanaries/pygwalker/tree/main/pygwalker/communications.
PygWalker is much more than just a thin wrapper around Graphic Walker. My understanding is that it
Strategically PygWalker will support and upgrade the solutions in the PygWalker repository. They will also promote them. Panel will probably not be a part of that journey when building its own solution. Except if it provides unique and more powerful features.
PygWalker also supports bidirectional communication. Being able to get hold of the configuration is a key enabler for persisting the user selections.
Where Panel can really make a difference is if it scale interactively to very large datasets. Like Datashader for HoloViews/ hvPlot. Or like what we support for Tabulator. Or like I've requested for Perspective in https://github.com/holoviz/panel/issues/7359. Or like modern tools developed with a DuckDB backend - for example Marimo and Quack. Or like Vega-Fusion.