Can jp_proxy_widget be installed without install

[gbrault]

Hello,

@Aaron-Watters :

I see that "newer widgets" don't need to be installed, no jupyter labextension install ... is needed
Could jp_proxy_widget implement this feature?

Thanks

[AaronWatters]

Sorry for the delay. I just tested this. At present I think you only need to do a "labextension install".

Here is the history of my test just now (cleaned up a bit):

  $  conda create -n testlab python=3.9
  $  conda activate testlab
  $  conda install jupyter
  $  cd ~
  $  conda install -c conda-forge jupyterlab
  $  jupyter lab
  $   pip install jp_proxy_widget

At this point I think proxy widgets work in classic notebook but not lab.

To make them work in lab at present you need:

  $  jupyter labextension install jp_proxy_widget
  $ jupyter lab

The jupyterlab build process is mysterious and frightening to me.
Do you have any additional information on how to make the "labextension install" automatic?

I will keep looking....

[AaronWatters]

This commit from jupyter-leaflet seems relevant, but I really don't understand what it is doing. Please let me know if you find any documentation on this.

ellisonbg/ipyleaflet@31b6d8c

[gbrault]

@AaronWatters you could ask support to Martin Renou or Jérémy Tuloup, those two are working a lot on the ipywidgets. It's Martin who told me about this new capability to release widgets without install. I don't know how we can invite another Github member to a discussion, I would have done it!

Both also work at Quantstack (Sylvain Corlay company)

[gbrault]

The jupyterlab build process is mysterious and frightening to me.

@AaronWatters : you are not alone!

[gbrault]

Reason why your widget is very handy! @AaronWatters

[gbrault]

You could also go and see: widget-cookiecutter. This is a template for cookiecutter, maintained by Martin Renou to start building a new widget (ipywidgets). I would assume it is up-to-date. There is also another version for Typescript based ts based

[psychemedia]

I spent a really miserable time trying to build a jupyterlab extension, and thought I'd made sensible notes at the time, but looking back at them, I'm not convinced they're as useful as I'd hoped they'd be:-(

https://blog.ouseful.info/2022/04/12/notes-on-the-jupyterlab-notebook-html-dom-model-part-8-5-a-reproducible-development-process/
https://blog.ouseful.info/2022/04/12/notes-on-the-jupyterlab-notebook-html-dom-model-part-9-building-and-distributing-a-pre-built-extension/

[psychemedia]

Hmmm... Looking at my own automation route ( https://github.com/innovationOUtside/jupyterlab_empinken_extension/blob/main/.github/workflows/pypi-extension.yaml ) it looks like you can get away with:

python3 -m pip install build
python3 -m build

and then the wheel is in dist/ as jp_proxy_widget-1.0.10-py2.py3-none-any.whl and jp_proxy_widget-1.0.10.tar.gz ?

[psychemedia]

In passing, the Binder demo appears to be broken again; Binder now launches into JupyterLab, and somewhere along the way, jp_proxy_widget appears to have broken in Lab again.

It'd be so useful if someone with core JuptyerLab devskills could maintain this project. It's the only way most of us have any chance of wrapping js in an ipywidgets context. (It'd be really useful to be able to compare to a simple jp_proxy_widget wrapped html/js app with a "native" ipywidget version. There would then be a tutorial pathway of a sort from wrapping a pre-existing js app to creating a native one. I've tried to make sense of ipyleaflet, but really can't fathom it...)

[gbrault]

Hello @psychemedia , could you please provide a link to the binder demo you are making reference?

[psychemedia]

I clicked the link in the README to this repo... : https://mybinder.org/v2/gh/AaronWatters/jp_proxy_widget/master

[gbrault]

It works on my side @psychemedia . What is the problem you are seing?

[psychemedia]

Hmmm...

In Chrome — just getting a blank screen:

But works in Firefox...?

Okay... so... quick check: seems that Ghostery was blocking it in Chrome unless the site was trusted? My apologies for not checking that before. I seem to recall similar issues with other extensions over the years...

[gbrault]

Chrome

[gbrault]

Firefox