Changes between Version 13 and Version 16 of Ticket #20690
- Timestamp:
- 06/27/16 16:03:51 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #20690
-
Property
Commit
changed from
5016cd83634381cd6be0f42154ea759744a7b272
to07035fd4b6db42b55131c19026f274e4e624f33b
-
Property
Commit
changed from
-
Ticket #20690 – Description
v13 v16 13 13 Steps: 14 14 - [X] Configure Sphinx to add the Thebe javascript library in the static page 15 - [ /] Configure Sphinx to add a small header to our html page with:15 - [X] Configure Sphinx to add a small header to our html page with: 16 16 - [X] Inclusion of the Thebe javascript 17 - [ x] Thebe configuration: which divs to make live17 - [X] Thebe configuration: which divs to make live 18 18 Currently, we include all <pre> tags that contain the "sage:" prompt 19 19 TODO: shall we change to <pre> tags that start with the "sage:" prompt ? 20 - [ ] Thebe configuration: use the Jupyter instance serving the page 21 We currently use window.location.origin; is this the right thing to do? 22 - [x] Only activate Thebe if the page is served by a Jupyter instance 20 to do? 21 - [X] Only activate Thebe if the page is served by a Jupyter instance 23 22 Currently we check that the protocol is http 24 - [ x] A button to activate live cells23 - [X] A button to activate live cells 25 24 26 25 - [X] Configure the Jupyter notebook in Sage to somehow provide the … … 29 28 - Preparse or customize/configure Thebe to support Sage's doctest syntax: 30 29 - [ ] Strip out the "sage: " prompts and "....:" and "... " continuation prompts 31 - [ 30 - [X] Strip out the outputs 32 31 Bonus: show the included outputs below the cell until the new output is computed 33 - [ 32 - [X] Support doctests with several commands by spliting into several cells 34 33 35 34 - Check what's the right way for including thebe.js in the Sage … … 38 37 39 38 Steps for later tickets: 39 40 - [ ] 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? 40 41 41 42 - [ ] Currently it takes 10s for 100 prompts while some sage files … … 54 55 - [ ] Check whether Jupyter could be configured to dynamically 55 56 negotiate incoming connections that don't fall within the 56 -NotebookApp.allow_origin pattern, by opening a user dialog such57 `-NotebookApp.allow_origin pattern`, by opening a user dialog such 57 58 as "Page xxx requests starting a new kernel on this server; do 58 59 you accept? yes/no/always for this site"