##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

This feature was discussed in #6123, but it doesn't look like anything was ever incorporated into the IPython Notebook....
This feature was discussed in #6123, but it doesn't look like anything was ever incorporated into the IPython Notebook. Here's a brief overview of the changes: - Display of messages from other clients can be toggled on and off from within a notebook, either using the ``<M-m>e`` keyboard shortcut in the web UI, or through the option in the "Kernel" menu. - notebook.js controls whether messages are displayed through a callback that is invoked from kernel.js when no callbacks are available for a message. - The UI displays ``execute_input`` messages originating from an other clients in new cells at the end of the notebook. Output messages (``execute_result`` et al.) will only be displayed if a cell exists with a matching message ID. Pending design questions: - Should each ``execute_input`` message cause a new cell to be created? - Should new cells be placed at the end of the notebook, or elsewhere? If the latter, what criteria should be followed?
Brian E. Granger - - Load All Authors

File last commit:

r15262:24772f02
r19164:17ac8ca3
Show More
README.md
28 lines | 932 B | text/x-minidsrc | MarkdownLexer
/ IPython / html / tests / README.md
History | Source | Raw |Copy content |Copy permalink
Brian E. Granger
Updating JS tests README.md.
 r15262 # IPython Notebook JavaScript Tests
Paul Ivanov
updated js tests README, --port= now optional
 r13271
Brian E. Granger
Updating JS tests README.md.
 r15262 This directory includes regression tests for the web notebook. These tests
depend on [CasperJS](http://casperjs.org/), which in turn requires a recent
version of [PhantomJS](http://phantomjs.org/).
David Wyde
Add a README for CasperJS tests.
 r13250
Brian E. Granger
Updating JS tests README.md.
 r15262 The JavaScript tests are organized into subdirectories that match those in
`static` (`base', `notebook`, `services`, `tree`, etc.).
To run all of the JavaScript tests do:
Paul Ivanov
updated js tests README, --port= now optional
 r13271
```
iptest js
```
Brian E. Granger
Updating JS tests README.md.
 r15262 To run the JavaScript tests in a single subdirectory (`notebook` in this
case) do:
David Wyde
Add a README for CasperJS tests.
 r13250
Brian E. Granger
Updating JS tests README.md.
 r15262 ```
iptest js/notebook
David Wyde
Add a README for CasperJS tests.
 r13250 ```
Brian E. Granger
Updating JS tests README.md.
 r15262 The file `util.js` contains utility functions for tests, including a path to
a running notebook server on localhost (http://127.0.0.1) with the port
number specified as a command line argument to the test suite. Port 8888 is
used if `--port=` is not specified. When you run these tests using `iptest`
you do not, however, have to start a notebook server yourself; that is done
automatically.