mirror/notebook
2
0
Fork 0
mirror of https://github.com/jupyter/notebook.git synced 2025-04-18 14:10:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

Minor wording pass

Browse Source
This commit is contained in:
Jeremy Tuloup 2020-12-22 12:48:10 +01:00
parent 61073a1bd7
commit df8386a23e
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -103,15 +103,14 @@ The goal of the `jupyterlab-classic` project is to look as close to the classic
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.
### Relation to other Jupyter frontends
## Relation to other Jupyter frontends
Jupyterlab-classic is an alternative frontend built using the latest Jupyter lab components, that is _similar_ to the classic Jupyter notebook UI. Below is a short description of where it stands when compared with other Jupyter UI projects.
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:
- Jupyter notebook - Classic frontend, classic notebook server.
- nbclassic - Classic frontend, new jupyter server.
- Jupyter lab - Jupyterlab frontend, classic notebook server. Extensions might not be compatible with 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 client side.
- Jupyterlab-classic - Classic-like frontend built with jupyterlab components, otherwise 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.
- 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).
## Prior art