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?
fix some extensions like live_reveal
the .not('.cell .cell') part prevent the potential selection of DOM
elelment that would have the class cell from any output. In each branch
of the dom we thus select the first decendent node that have the class
'.cell'.
- draws error message in the same dialog,
rather than triggering a new dialog via events.
- `Notebook.rename` returns the contents Promise, rather than registering its own error handler.
Modfies the Contents class to return JavaScript Error objects instead of passing on the return values from $.ajax(). This has two advantages. First, it allows the content manager to parse errors and give more informative messages than the ajax response. Second, it makes the Contents interface more general, since other kinds of backends might generate client-side errors.
Modifies ContentManager.save_notebook() to use events, so that the Notebook instance can listen for success or failure events. Also moves some logic out of save_notebook()
Nathan Heijermans
Thomas Kluyver
Min RK
Bussonnier Matthias
v923z
Kester Tong
Jeff Hemmelgarn