Show More
@@ -114,12 +114,12 b' Asynchronous' | |||||
114 |
|
114 | |||
115 | In the IPython 2.x series the only way to register custom widget views |
|
115 | In the IPython 2.x series the only way to register custom widget views | |
116 | and models was to use the registry in the widget manager. Unfortunately, |
|
116 | and models was to use the registry in the widget manager. Unfortunately, | |
117 |
using this method made |
|
117 | using this method made distributing and running custom widgets difficult. The widget | |
118 | maintainer had to either use the rich display framework to push the |
|
118 | maintainer had to either use the rich display framework to push the | |
119 | widget's Javascript to the notebook or instruct the users to install the |
|
119 | widget's Javascript to the notebook or instruct the users to install the | |
120 | Javascript by hand in a custom profile. With the first method, the |
|
120 | Javascript by hand in a custom profile. With the first method, the | |
121 | maintainer would have to be careful about when the Javascript was pushed |
|
121 | maintainer would have to be careful about when the Javascript was pushed | |
122 | to the font-end. If the Javascript was pushed on Python widget |
|
122 | to the front-end. If the Javascript was pushed on Python widget | |
123 | ``import``, the widgets wouldn't work after page refresh. This is |
|
123 | ``import``, the widgets wouldn't work after page refresh. This is | |
124 | because refreshing the page does not restart the kernel, and the Python |
|
124 | because refreshing the page does not restart the kernel, and the Python | |
125 | ``import`` statement only runs once in a given kernel instance (unless |
|
125 | ``import`` statement only runs once in a given kernel instance (unless |
General Comments 0
You need to be logged in to leave comments.
Login now