-
Notifications
You must be signed in to change notification settings - Fork 947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move ypywidgets to jupyter-widgets? #3777
Comments
@davidbrochart we had a brief discussion on it during the widgets meeting today, but no decision has been made as we probably want to involve move members of the widgets group before converging on a decision. It would be good if you could attend the next meeting and hopefully we can have a follow up then. @jasongrout for visibility. |
Thanks, I'll try to attend next meeting 👍 |
We decided to first try and support basic ipywidgets frontends (HTML widgets, maybe a bigger one like ipyeaflet?) in ypy/yjs-widgets, and then resume this discussion. |
How about creating the That way For reference there were some discussions about this new org during the Jupyter Widgets community workshop 2022: jupyter-widgets/team-compass#16 (comment) |
💯 Totally agree with this idea. Would be willing to move https://github.com/QuantStack/ipytree and https://github.com/martinRenou/ipycanvas into such an org. We can also discuss moving all the xwidgets/xleaflet etc that QuantStack created. |
I've been looking for such a place for ipyautoui also |
I created the https://github.com/jupyter-widgets-contrib organization, moving ipycanvas there already as a test. The website is here: https://jupyter-widgets-contrib.github.io. It is simply a fork of the JupyterLab contrib website. Feel free to open transfer requests so we can start feeding this organization! Happy to give admin rights to people as well in the process. |
Nice thanks @martinRenou! |
In https://github.com/davidbrochart/ypywidgets/issues/12 @martinRenou suggested moving ypywidgets to another organization. I think it would make sense to move it to jupyter-widgets.
It's still early days, but we already have real use cases, in JupyterCAD and Glue JupyterLab. We were also thinking about trying to leverage ipywidgets' frontend by swapping the synchronization backend with ypywidgets'. That would be the ideal solution, where people could opt in to use Ypy/Yjs for the backend when installing ipywidgets or other higher-level widgets (ipyleaflet, etc.).
I guess yjs-widgets (the browser client counterpart) would have to move to jupyter-widgets too. There is also reacttrs, which replaces traitlets for the observer pattern, but this one is more general and could be used outside Jupyter widgets.
Thoughts?
The text was updated successfully, but these errors were encountered: