After updating, and installing websockets, the new version opened OK in
vsc. One thing I noticed is that LeoInteg uses the name "Leo" in the bar
displaying its name, and LeoJS uses "LeoJS". This makes it a little
unclear whether the "Leo" panel is another instance of LeoJS, or whether
it's
On Monday, January 22, 2024 at 5:09:27 PM UTC-5 Edward K. Ream wrote:
On Mon, Jan 22, 2024 at 3:10 PM Thomas Passin wrote:
Didn't we decide not to support Jupyter notebooks any more? If so, nbformat
can probably be omitted in the future.
Good catch. Hehe, VR3 still has some references to
On Mon, Jan 22, 2024 at 3:10 PM Thomas Passin wrote:
> Didn't we decide not to support Jupyter notebooks any more? If so,
> nbformat can probably be omitted in the future.
>
Good catch. Hehe, VR3 still has some references to nbformat!
Edward
--
You received this message because you are
On Monday, January 22, 2024 at 3:49:42 PM UTC-5 Edward K. Ream wrote:
setup.py specifies requirements in the section called << define
install_requires >>.
This section lists the following dependencies:
install_requires = [
# Other entries omitted
'nbformat', # for Jupyter
> What effort would it be to package a version of Leo providing
~everything~ but the GUI?
Thanks for this timely question.
*tl;dr:* Making things work as I am guessing you would like should be
straightforward.
*Background*
leoserver.py creates the link between LeoInteg and Leo using Leo's
Hello Edward, hello Felix,
Currently whenever I'd like to install LeoInteg on any non-Windows host I
have to install Leo with PyQt. - This is sometimes quite difficult / tricky
...
AFAIK LeoInteg is relying solely on the GUI provided through VS Code.
What effort would it be to package a
