In general, stackoverflow question should try to only ask one question at the time. That being said, I’ll try to answer the questions as best I can:
- ipywidgets is the main way, yes. It is what people mean when they talk about notebook widgets.
- There is an issue tracking general JS in jupyterlab on the jupyterlab repo.
@jupyter-widgets/jupyterlab-manageris the widgets for jupyterlab, yes, but you will still need the python code in ipywidgets. See http://ipywidgets.readthedocs.io/en/stable/user_install.html for details.- While it is true that one is JS and the other TS, the TS one also has all the bells and whistles. It is therefore also more complex. The JS one is more bare-bones and might therefore be better for understanding the most important bits.
- I agree that both could do with better documentation! I’ve been meaning to do this for a while. The best way to make this happen is probably to open issues with specific questions on the respective repositories, and suggesting the explanation go in the README or similar. That way you can ensure that your pain-points gets addressed.
- Given the large user base of widgets, I would consider it safe. While the bus factor isn’t very high, people tend to step up if there is a drop in maintainers.
- Yes, but using widgets for jupyterlab is still slightly high maintenance both for developers and users.
- What you might want to study is
Comms(http://jupyter-notebook.readthedocs.io/en/stable/comms.html), which is what widgets use under the hood for its synchronization. This is lower level though, so you will have to judge which is most suitable for you.