* Initial WIP static files removal (it builds, but has bugs).
* del nbclassic from __init__.
* Removed unneeded CSS/JS compilation logic.
* Removed more frontend web logic.
* Added nbclassic as a proper notebook dependency.
* Updated nbclassic dependency version.
* Added nbclassic to pyproject.toml.
* Moved DEFAULT_STATIC_FILES_PATH.
* Removed JS tests.
* Added nbclassic tgo docs build.
* Adding blank pre-commit-config for CI checks.
* Edited empty pre-commit-config
* Added docs to enforce-label workflow.
* Revised workflow comments.
* Adding WIP version_spec value to check_release step.
* Changed dev version number.
* Revert "Changed dev version number."
This reverts commit e66673160f.
* Manual WIP version number update to 6.5.0.dev
* Manual (WIP) version dummy value for CI check.
* Revised version numbner (WIP).
* Reverted version number to pre-PR value.
* Pinned selenium version.
* Removed setup.py jsversion call.
* Removed webpack config.
* Removed bower/other web files.
* Disable test with modal dialog error.
* Modified pip upgrade command.
That give most of the information a user needs to write a full-fledge
extension without having to look into tornado documentation:
- Authentication: I think all handler should be authenticated by
default.
- Managing state and accessing server state from the handlers: I don't
think there is many interesting things you can do without accessing
server state and configuration.
The doc shows how to update codemirror options for the notebook cell editor, but not for the whole file editor. I have added lines 51-62 to give that information. The information comes from Stack-Overflow (and has been tested), but it has been frustratingly long to find, so I think it is worth sharing ...
On Python 3, the default source file encoding for Python files is utf-8
and because Python 2 is no longer supported, the utf8 coding cookies can
be removed
The section `Notebook front-end client` in the config overview
page was essentially a toc tree except the sub-section links
went to the top of the frontend_config page rather than the real
sub-sections in that page because they all used the same reference.
Rather than create a unique reference for each sub-section in the
frontend_config page, this simply embeds the frontend_config toctree
within the config_overview page which essentially has the same effect.
Closes#5740
* Document contents chunks
Add a documentation entry for the contents API regarding use of "chunk" in save.
Adds an `extra_requires` value in setup.py for installing documentation dependencies.
