bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook Messages The messaging specification section on comms Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs _target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message, which can carry data // Register handlers for later messages: comm.on_msg(function(msg) {...});

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook html#custom-messages] The messaging specification section on comms Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs registered in a registry: Jupyter.notebook.kernel.comm_manager.register_target('my_comm_target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook Messages The messaging specification section on comms 3.1 Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs _target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message, which can carry data // Register handlers for later messages: comm.on_msg(function(msg) {...});

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook html#custom-messages] The messaging specification section on comms Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs registered in a registry: Jupyter.notebook.kernel.comm_manager.register_target('my_comm_target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook html#custom-messages] The messaging specification section on comms Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs registered in a registry: Jupyter.notebook.kernel.comm_manager.register_target('my_comm_target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook Messages The messaging specification section on comms 3.1 Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs _target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message, which can carry data // Register handlers for later messages: comm.on_msg(function(msg) {...});

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook Messages The messaging specification section on comms 3.1 Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs _target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message, which can carry data // Register handlers for later messages: comm.on_msg(function(msg) {...});

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook html#custom-messages] The messaging specification section on comms Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs registered in a registry: Jupyter.notebook.kernel.comm_manager.register_target('my_comm_target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook Messages The messaging specification section on comms 3.1 Opening a comm from the kernel First, the function to accept the comm must be available on the frontend. This can either be specified in a requirejs _target', function(comm, msg) { // comm is the frontend comm instance // msg is the comm_open message, which can carry data // Register handlers for later messages: comm.on_msg(function(msg) {...});

bar: The menu bar presents different options that may be used to manipulate the way the notebook functions. Toolbar: The tool bar gives a quick way of performing the most-used operations within the notebook the output area. In [6]: print("hi, stdout") hi, stdout In [7]: from __future__ import print_function print('hi, stderr', file=sys.stderr) hi, stderr 3.3.6 Output is asynchronous All output is displayed keyboard_manager.command_shortcuts.add_shortcut('r', { help : 'run cell', help_index : 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); “By default the keypress r, while