Go to file

Jeremy Tuloup fa4246e564 Update example notebook		5 years ago
.github/workflows	Add CI	5 years ago
binder	Update example notebook	5 years ago
builder	Add command palette	5 years ago
jupyter-config	Add Binder (#2 )	5 years ago
jupyterlab_classic	Add Binder (#2 )	5 years ago
packages	Add CI	5 years ago
.eslintignore	Initial commit	5 years ago
.eslintrc.js	Initial commit	5 years ago
.gitignore	Add toolbar button to open in classic	5 years ago
.prettierignore	Add CI	5 years ago
.prettierrc	Initial commit	5 years ago
LICENSE	Initial commit	5 years ago
MANIFEST.in	Add Binder (#2 )	5 years ago
README.md	Update Binder link in README.md	5 years ago
lerna.json	Initial commit	5 years ago
lint-staged.config.js	Initial commit	5 years ago
package.json	Reuse doc manager from lab	5 years ago
pyproject.toml	Initial commit	5 years ago
setup.py	Add Binder (#2 )	5 years ago
tsconfig.eslint.json	Initial commit	5 years ago
tsconfig.test.json	Initial commit	5 years ago
tsconfigbase.json	Initial commit	5 years ago
tsconfigbase.test.json	Initial commit	5 years ago
yarn.lock	Add toolbar button to open in classic	5 years ago

README.md

jupyterlab-classic

The next gen old-school Notebook UI.

Install

With pip:

pip install jupyterlab-classic

With conda:

conda install -c conda-forge jupyterlab-classic

Usage

jupyterlab-classic can be started as a standalone app with:

python -m jupyterlab_classic

Existing federated JupyterLab extensions listed via:

jupyter labextension list

Should also be available when starting jupyterlab-classic.

Motivation

JupyterLab is the next-gen UI for Project Jupyter. Approaching version 3.0, it is becoming more mature and provides an advanced computational environment, that can sometimes be compared to what traditional IDEs offer.

However in some cases, having a leaner, simpler, and more focused interface to work on a notebook is really useful.

The single document mode as currently implemented in JupyterLab helps address this issue, but still displays a couple of visual cues that can be distracting to some users.

The goal of the jupyterlab-classic project is to look as close to the classic notebook UI as possible, while leveraging the efforts put in the development of JupyterLab itself and its extension system.

Technically speaking, jupyterlab-classic reuses many of the existing plugins for JupyterLab (notebook, toolbar), and also supports pre-built (federated) third-party extensions using the new distribution system added in 3.0. That way, extensions built for JupyterLab should also be compatible with jupyterlab-classic, as long as they can be added to the application shell provided by JupyterLab Classic.

Prior art

This project is mostly a reboot of the two previous attempts at making something similar:

These projects really expressed the need for a stripped down, minimal version of the Jupyter Notebook UI.

jupyterlab-classic contributes to that space with the added features:

Support for existing federated (prebuilt) JupyterLab extensions
Zen Mode
Repo structure, similar to JupyterLab
Reusing as much as possible from upstream JupyterLab