Tue Dec 18 11:40:03 CST 2012
Le 18 déc. 2012 à 14:02, Nissim Karpenstein a écrit :
> 1) ability to change a code cell language to javascipt in the notebook frontend. I saw that there is a language field in the notebook file format for CodeCell but it is always = python.
> 3) http REST api that will return json representations of Python objects that exist in the kernel. (this may already exist, I don't really understand the kernel communication protocol yet).
> There are probably some more things like the ability to add CSS, HTML, js and image resources to the server that it can then serve back to the client. I see that there's been a lot of discussion related to this in the plugins thread, but maybe there can also be a method for accessing resources from the network and then telling the notebook server to serve them from some path.
> I'd like to implement this and I had a couple of questions:
> 1) Does this fit in with your ideas for the notebook or is editing non python code in CodeCell outside of the vision?
My answer will be short, but there are lot more too say here,
I absolutely don't want to discourage you here, I'm sure there are way to do what you want to seamlessly
for the user.
It will be optional but js will be on purpose **painfully** and opt-in.
But, that what the json handler pull request is made for.
There is a prototype on d3 graph visualization using json handler.
We already have prototype of node/ruby kernel so you might be able to do js/ruby kernel side if needed.
I don't think we have decide yet of multi-language notebook on a per-cell basis without magics.
I wouldn't recommend it as it forces user to think of the kernel where the variable are defined.
But language on a per-notebook basis is totally conceivable, we just need devs from other language...
There are also issues where kernel and server might be on different machines, which we should keep in mind so avoid server as much as possible.
I know there are plan on making ability in browser to run JS in a **safe** sandbox, which are not really ready yet I think,
when this comes to maturity the ability to execute js in browser, might be revisited, still i might not have access to the DOM directly.
> IPython-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev