[IPython-dev] D3js and IPython
Wed Jan 9 16:21:11 CST 2013
On Tue, Jan 8, 2013 at 11:37 PM, Matthias BUSSONNIER
>> I do appreciate the concern, and we need a solution to the issue.
>> I just don't think we have a complete one yet.
>> Right now, we have a supremely flexible (and thus insecure) situation,
>> whereas jsplugins-only is secure, but not remotely flexible from a user's perspective.
>> This is an extremely serious incapacitation of the notebook.
>> The trouble is that jsplugins is a relatively tolerable substitue
>> for the single-user notebook, but where the problem is worst
>> is when users don't actually have access to the server
>> to install jsplugins. So it's precisely the case where we
>> would not allow custom js that jsplugins fail most dramatically
>> as a substitute.
>> Is it really our intention to require *server* installation of a plugin
>> for a user to gain access to a new widget? That seems to eliminate a *huge* portion of exactly what makes the notebook interesting.
>> If we have a way that js plugins can be loaded at runtime by the user without access to the server (presumably with a 'do you trust this guy?' confirmation),
>> then that would go a long way toward preventing the total castration of the notebook.
I don't see any way that we can allow <script> tags in markdown and
HTML output. Those is the most dangerous case as they are run at
notebook load time and there is no hook for us to prevent that. All
we can do it strip them.
> But, If you design a custom plugin that deal with a specific type of json data, then you get the ability for this data to be used
> at load time as the json repr is stored.
> And I do agree that we need to give users a way to still display JS.
> which is not stored. It is nice for prototyping, but it does more harm than anything for sharing.
> Finally I suppose it will be doable and a good thing to develop the ability to plug those jsplugin to nbviewer.
Yes, I agree.
> IPython-dev mailing list
Brian E. Granger
Cal Poly State University, San Luis Obispo
email@example.com and firstname.lastname@example.org
More information about the IPython-dev