Le 29 juil. 2013 à 23:27, Surya Kasturi a écrit :
On Mon, Jul 29, 2013 at 11:02 PM, Matthias BUSSONNIER <bussonniermatthias@gmail.com> wrote:
Le 29 juil. 2013 à 22:57, Ralf Gommers a écrit :
On Sun, Jul 28, 2013 at 9:17 PM, Surya Kasturi <suryak@ieee.org> wrote: Hi All,
Regarding ipython notebook integration in scipy central
1. should we upload ipynb files or provide an editor (or Text Area)? which one would be nice?
Uploading ipynb files and providing a link to view them via http://nbviewer.ipython.org/ would be a good solution. An editor would be a lot of work that's outside the scope of the site I'd think.
We will support custom css on nbviewer if it interests you. We can also discuss at something like api.nbviewer.ipython.org if you like to embed the html, or have more parametrized requests / custom things.
This sounds quite interesting! but have to see if we require it considering that we are not doing anything more than storing URLs of nbviewer pages
You might not want all our cell toolbar and a "back" button. I would suggest against storing only nbviewer url only as whats happened most of the time is that origin url move. So lots of nbviewer urls might be broken. Unless you make sure the url point back at a resource hosted by scipy. The advantage of Nbviewer is you are on another subdomain and so have no concern about JS injection. What I think we should do if you want to use nbviewer is in 2 step. Through the (future) api : - you send " i've got this ipynb on scipy at this url. " - i'll send you back : "I can render it at this url" So no concern about url changing etc... Will mot probably not have time to work on it soon, but I'll be happy to polish the detail with you if need later.
Agree that text editor is too much.
As for uploading, would there be a record of different versions ?
Well, we are using Hg for storing other data! hope we can use it for ipynb files too!
Great ! Just to be sure. -- M