<div dir="ltr">Gosh, I'd rather read foo(path:string, notebookName:string) any day, instead of having to *also* reference aliases infer based on the name itself.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 29, 2015 at 8:43 AM, Matthias Bussonnier <span dir="ltr"><<a href="mailto:bussonniermatthias@gmail.com" target="_blank">bussonniermatthias@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><blockquote type="cite"><div><div bgcolor="#FFFFFF" text="#000000"><br>
In another message on this thread, Min suggested having a 5.x branch
for further development, like the phosphor notebook. For now, I
think the phosphor notebook can proceed as a separate project - it's
totally a front-end thing at this point, and we're doing enough code
clean-up and rewriting from js to typescript that I think it's all
right to start in a fresh repo. Which brings up another point: can
we make an official Jupyter repo for the phosphor notebook work,
rather than using my personal repo? I'm happy to continue hosting <a href="https://github.com/jasongrout/phosphor-notebook/" target="_blank">https://github.com/jasongrout/phosphor-notebook/</a>
in my personal github account for the time being, or set up a
temporary organization so we can collaborate more effectively, but I
think it would make more sense to bump it up to an experimental repo
in the jupyter github organization, developed in parallel with the
current notebook.
<br></div></div></blockquote><div><br></div></span><div>Done, Jason you are admin, I **think** you can all people to the team. </div><div>I’m hopping on my plane, like in 5 min. Feeling like Linus writing a rc release not from airports as often. </div><div>(I haven’t forked your to make sure it appears as a root repo) </div><div><br></div><div><br></div><div>Quick +1 on typescript the type aliases allow you to so </div><div><br></div><div>define Path extends String {}</div><div><br></div><div>Which auto produce nice docs with meaning instead of just foo(a:string, a:string) you get foo(a:Path, b:NotebookName)</div><div>which is really good for docs.</div><div><br></div><div><br></div><div>See you Tuesday morning on dev meeting, which for once should **not** be public, as we are trying BlueJeans. </div><span class="HOEnZb"><font color="#888888"><div>-- </div><div>M</div><br></font></span><blockquote type="cite"><div><span class=""><div bgcolor="#FFFFFF" text="#000000">
<br>
Thomas, one thing to consider is that us working on a phosphor
notebook doesn't preclude interested people from enhancing the
existing notebook in the short term. We'd like the phosphor
notebook to get to a comparable state with the current notebook as
quickly as possible, but it will still take some time.
<br>
<br>
Also, I totally agree with Thomas that dogfooding the notebook (and
watching/helping others actually use it to get work done) is <b><span>*</span>extremely<span>*</span></b> important to understanding what
we want here.
And I also agree with others on this thread that documentation is
sorely lacking. We'll be working on that in the phosphor notebook
as we go along too.<br>
<br>
Thanks,
<br>
<br>
Jason
</div></span><span class="">
_______________________________________________<br>IPython-dev mailing list<br><a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br><a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br></span></div></blockquote></div><br></div><br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" rel="noreferrer" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Kyle Kelley (<a href="https://twitter.com/rgbkrk" target="_blank">@rgbkrk</a>; <a href="http://lambdaops.com/" style="color:rgb(17,85,204)" target="_blank">lambdaops.com</a>, <a href="http://developer.rackspace.com" style="font-size:12.8000001907349px" target="_blank">developer.rackspace.com</a>)</div></div></div></div>
</div>