Re: JavaScript extension cheat or not?

I think the cheat is perfectly fine for now. In the next 6 months we
will be moving over to using npm packages for all of our JavaScript
code. But the cheat will continue to work.

Cheers,

Brian

On Sun, Nov 22, 2015 at 1:51 PM, Pierre Villeneuve
<[email protected]> wrote:
> In my work I rarely need to dive deep into technical details on notebook
> extensions. In fact I'd like to keep it that way since the entire Jupyter
> landscape and ecosystem is evolving so rapidly (that's great!).
>
> I wrote an extension last year under IPython 3 that worked just nicely using
> jupyter-pip. But now that I've updated to the latest Jupyter 4 something is
> broken with locating my JS file after install.
>
> Option 1 is to dig in and make it work correctly with Jupyter's current
> nbextension system. Option 2 is to programmatically read the JS file and
> then use IPython's enhanced display mechanism to pipe the JS to the browser.
>
> Option 2 worked nicely for me in the past and its so easy to manage. But
> what's the downside? Is it considered "cheating"? :)  When is that method
> not reliable?
>
> Thanks!
>
> Pierre Villeneuve
> [email protected]
>
>
> _______________________________________________
> IPython-dev mailing list
> [email protected]
> https://mail.scipy.org/mailman/listinfo/ipython-dev
>



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
[email protected] and [email protected]