Follows the current best practices for installing extensions on Jupyter 4.x:
pip install dumps everything into the active Python path
A project specific script (extensionapp.py, bootstrapped from nbgrader, thanks @jhamrick), provides a CLI for:
installing the JS extension assets into the user defined location (--user, --symlink, --prefix, ...)
enabling the JS and server-side extensions
disabling the JS and server-side extensions
Server-side extensions are enabled/disabled in JSON files, not .py files
Fixes #19
@lbustelo @jtyberg If we adopt this here, we have to adopt it everywhere (dashboards, declarativewidgets), because the JSON config file takes precedence over the .py config file for the server extensions list. (Keep in mind, we're already incompatible with extensions like nbgrader, nbpresent, ... which will clobber our hack-to-.py file config)
Follows the current best practices for installing extensions on Jupyter 4.x:
Fixes #19
@lbustelo @jtyberg If we adopt this here, we have to adopt it everywhere (dashboards, declarativewidgets), because the JSON config file takes precedence over the .py config file for the server extensions list. (Keep in mind, we're already incompatible with extensions like nbgrader, nbpresent, ... which will clobber our hack-to-.py file config)