upstream/ipython Files · IPython/html/services/contents/clientsidenbmanager.py

This feature was discussed in , but it doesn't look like anything was ever incorporated into the IPython Notebook....

This feature was discussed in , 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?

Matthias Bussonnier - - Load All Authors

File last commit:

r18979:ee673d8b


                r19164:17ac8ca3

Download file

             clientsidenbmanager.py
        
                    23 lines
            
             | 829 B
            
                | text/x-python
            
             |
                PythonLexer
            
             / IPython / html / services / contents / clientsidenbmanager.py
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      """A dummy contents manager for when the logic is done client side (in JavaScript)."""

      # Copyright (c) IPython Development Team.

      # Distributed under the terms of the Modified BSD License.

      from .manager import ContentsManager

      class ClientSideContentsManager(ContentsManager):

          """Dummy contents manager for use with client-side contents APIs like GDrive

          The view handlers for notebooks and directories (/tree/) check with the

          ContentsManager that their target exists so they can return 404 if not. Using

          this class as the contents manager allows those pages to render without

          checking something that the server doesn't know about.

          """

          def dir_exists(self, path):

              return True

          def is_hidden(self, path):

              return False

          def file_exists(self, name, path=''):

              return True

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				"""A dummy contents manager for when the logic is done client side (in JavaScript)."""

				# Copyright (c) IPython Development Team.
				# Distributed under the terms of the Modified BSD License.

				from .manager import ContentsManager

				class ClientSideContentsManager(ContentsManager):
				"""Dummy contents manager for use with client-side contents APIs like GDrive

				The view handlers for notebooks and directories (/tree/) check with the
				ContentsManager that their target exists so they can return 404 if not. Using
				this class as the contents manager allows those pages to render without
				checking something that the server doesn't know about.
				"""
				def dir_exists(self, path):
				return True

				def is_hidden(self, path):
				return False

				def file_exists(self, name, path=''):
				return True