The `ipy` prefix in the `ipyvizzu` name has a story:
We tried to implement a generic python integration first. It seemed easy with cython. But a question arised: does it work with interactive widget in jupyter notebook?
The `ipywidget` showed as a solution, but the custom widget was too complex for our usecase. So we looked for examples, and we found `plotly`. `plotly` has a nice trick: in jupyter notebook they call `IPython.display.display_html` with raw option. This way a html `script` node can be displayed in jupyter notebook.
`Vizzu` has a nice javascript API so we went in this way. `ipyvizzu` basically is a javascript code generator wich works only in jupyter notebook. That's why we put the `ipy` prefix for the package name.
The generic python integration is still a good idea, and we can use the `pyvizzu` or `vizzu` package name for it in the future.
We tried to implement a generic python integration first. It seemed easy with cython. But a question arised: does it work with interactive widget in jupyter notebook?
The `ipywidget` showed as a solution, but the custom widget was too complex for our usecase. So we looked for examples, and we found `plotly`. `plotly` has a nice trick: in jupyter notebook they call `IPython.display.display_html` with raw option. This way a html `script` node can be displayed in jupyter notebook.
`Vizzu` has a nice javascript API so we went in this way. `ipyvizzu` basically is a javascript code generator wich works only in jupyter notebook. That's why we put the `ipy` prefix for the package name.
The generic python integration is still a good idea, and we can use the `pyvizzu` or `vizzu` package name for it in the future.