Skip to content

Meta-ticket: Improve live documentation in the Jupyter notebook #20893

@videlec

Description

@videlec

Since #20690 we have access to documentation (with live execution)
within the Jupyter notebook. It was decided to keep the code simple.
There are two ongoing projects within Jupyter for having this working.
It might be wiser to wait for them...

Some of the improvements mentioned in #20690 were:

  • [ ] Configure Sphinx to add a small header to our html page with
    Thebe configuration: use the Jupyter instance serving the page.
    We currently use window.location.origin; is this the right thing?

  • Currently it takes 10s for 100 prompts while some sage files
    contain up to 1000 prompts. Profile Thebe and optimize it or use
    a separate thread to properly support large files.

  • Expand the activate button with a menu or other widgets for user customization
    of the Jupyter server. This typically would let the user choose between:

    • tmpnb (will only be useful for Sage
      when tmpnb will include a Sage kernel; there are ongoing discussions for providing an alternative sage-enabled tmpnb)
    • a local Jupyter server,
    • whichever Jupyter server the browser is currently connected to?
    • a user-specified server.
  • Check whether Jupyter could be configured to dynamically
    negotiate incoming connections that don't fall within the
    -NotebookApp.allow_origin pattern, by opening a user dialog such
    as "Page xxx requests starting a new kernel on this server; do
    you accept? yes/no/always for this site".

  • Add support in Thebe for customizable (continuation) prompts, with striping and splitting as above, and automatic setting of the kernel. The customization option could look like:

    prompts = {
        "sage: ": {continuations=["....:", "...  "], kernel="sagemath"},
        ">>>> ": {continuation="...  ", kernel="python"}
    }
    
  • Have Thebe provide good TAB-completion.

  • Let the cursor switch to the next cell after evaluation (SHIFT+ENTER).

  • Extract support for Thebe as a Sphinx extension with (see the related sage-cell extension):

    • Explicit markup to specify which code blocks are editable and with
      which kernel, or setup kernel auto-detection from the prompt.
    • The possibility for setting a default value for the above.
  • Refactor the Sage Sphinx configuration to use the above.

  • Configure sage-sample / sage-package to use it, to enable live documentation for Sage packages.

  • Add support in Thebe for basic export to Jupyter notebooks. A
    quality loss (in particular in terms of the hierarchical
    structure) is acceptable.

  • Allow to save the current state of the webpage as a .ipynb worksheet, to be able to continue working on it later, see [[/ticket/20690#comment:53]].

Tickets:

See also:

Depends on #20690

CC: @vbraun @rbeezer @nthiery @hivert @slel @sagetrac-fcayre @jdemeyer @dimpase @kwankyu

Component: documentation

Keywords: thebe, thebelab

Issue created by migration from https://trac.sagemath.org/ticket/20893

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions