From a609e000965d862bf1274aaa2270bb7c2f53aed7 2015-02-27 20:54:18 From: Jonathan Frederic Date: 2015-02-27 20:54:18 Subject: [PATCH] Merge pull request #7895 from jdfreder/jasonsfixes @jasongrout 's changes on the widget migration doc on the wiki. --- diff --git a/docs/source/whatsnew/version3_widget_migration.rst b/docs/source/whatsnew/version3_widget_migration.rst index 5bfca7b..a87f66a 100644 --- a/docs/source/whatsnew/version3_widget_migration.rst +++ b/docs/source/whatsnew/version3_widget_migration.rst @@ -114,12 +114,12 @@ Asynchronous In the IPython 2.x series the only way to register custom widget views and models was to use the registry in the widget manager. Unfortunately, -using this method made packing custom widgets difficult. The widget +using this method made distributing and running custom widgets difficult. The widget maintainer had to either use the rich display framework to push the widget's Javascript to the notebook or instruct the users to install the Javascript by hand in a custom profile. With the first method, the maintainer would have to be careful about when the Javascript was pushed -to the font-end. If the Javascript was pushed on Python widget +to the front-end. If the Javascript was pushed on Python widget ``import``, the widgets wouldn't work after page refresh. This is because refreshing the page does not restart the kernel, and the Python ``import`` statement only runs once in a given kernel instance (unless