@jupyterlab-classic/notebook-extension NPM

jupyterlab-classic

The next gen old-school Notebook UI.

Install

jupyterlab-classic can be installed with pip:

pip install jupyterlab-classic

And with conda (coming soon):

conda install -c conda-forge jupyterlab-classic

Usage

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

jupyter classic

Existing federated JupyterLab extensions listed via:

jupyter labextension list

Should also be available when starting jupyterlab-classic.

Files 📂 and Running Sessions 🏃‍♀️

tree

Notebook 📒

notebook

Open in a new Browser Tab by default

new-browser-tab

Command Palette 🎨

command-palette

Themes 🌈

Support for existing JupyterLab themes!

themes

Zen Mode 😌

compact-zen-mode

Terminals 🖥️

terminals

File Editor 🖊️

Compact View on Mobile Devices 📱

mobile

Support for prebuilt extensions 🧩

Install new extensions easily!

federated-extensions

Switch between JupyterLab and JupyterLab Classic easily ↔️

jupyterlab-switch

Contributing

If you would like to contribute to the project and set up a development environment, check out CONTRIBUTING.md.

Motivation

JupyterLab is the next-gen UI for Project Jupyter. Currently at 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 provide an alternative JupyterLab distribution with the look and feed of the classic notebook UI, 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 prebuilt (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.

Relation to other Jupyter frontends

Jupyterlab Classic is an alternative frontend built using the latest JupyterLab components, with the look and feel of the Classic Jupyter Notebook UI. Below is a short comparison to know where it stands when compared to other Jupyter UI projects:

Classic Jupyter Notebook - Classic frontend, classic notebook server.
NBClassic - Classic frontend, new Jupyter Server.
JupyterLab - Jupyterlab frontend, new Jupyter Server (or Classic Notebook Server). Extensions are not compatible with the Classic Jupyter Notebook since it is built with different components. With version 3.0 onwards, it uses the new Jupyter Server and supports federated extensions that don't need to be rebuilt on the end-user machine.
Jupyterlab Classic - JupyterLab frontend built with JupyterLab components, with the look and feel of the Classic Notebook. Consistent with the latest version of Jupyterlab. Extensions built for Jupyterlab should work as long as the components they depend on are part of this classic interface (for install JupyterLab Classic doesn't have the left, right and bottom areas).