I read through the docs with an eye towards porting my IPYWidget based data table to Solara. Although I built an app that extends DOMWidget, I have spent very little time linking together IPYWidget components in a jupyter notebook.
I glossed over the introduction page . Could you add some actual descriptions of the problem that reacton solves? "Here is a simple app with 3 IPYWidgets, see the way we have to wire that together?" then "with Reacton, that same app looks like this"
On this page I would expect the examples to be based on the jupyter notebook.
I would present it as "here is solara code that has a bit of extra solara stuff", now you can just run this exact same code in the solara server. Someone who uses IPYWidgets is going to want to start in the notebook because it's lower friction than saving a file and starting a server. That might be because App building with IPYWidgets is still novel to me
I missed the .element call because I just skimmed it and copy/pasted code. Probably my fault.
I also misunderstood the page. I thought it was a page for "How can I adapt my IPYWidget library to solara". Maybe you should title it "using IPYWidget libraries"
Create your own wrapper
It isn't clear what is being done here. Maybe you could write an explanatory sentence of "Regular IPYWidget libraries need a wrapper because of X" then "A simple wrapper would look like Y" then "For code maintanence reason W we instead prefer to generate code to wrap these libraries"
Could you show an example in a notebook of wrapping a DOMWidget or AnyWidget based IPYWidget so that it works in solara. If I figure it out myself first, I will make a PR.
I read through the docs with an eye towards porting my IPYWidget based data table to Solara. Although I built an app that extends DOMWidget, I have spent very little time linking together IPYWidget components in a jupyter notebook.
Here are my initial impressions and suggestions:
.element
call because I just skimmed it and copy/pasted code. Probably my fault.