<div>I'd like to add a vote in for the continued presence of the dashboard, and for Brian's idea for incorporating multiple directories in the dashboard. I have no need at all for a fully-fledged file manager, just a means to switch between project dirs. And only an "Open" dialog doesn't fit that idea of a project dir at all.</div>
<div><br></div><div>Also probably worth considering that an awful lot of users hate the command line, even for simple things like changing directories. With a dashboard that allows you to change dirs, the local-user use scenario doesn't require you to use the command line at all beyond the initial launch, which can be wrapped up into a shortcut, etc.</div>
<div><br></div><div>Cheers</div><div><br></div><div>Kent<br><br><div class="gmail_quote">On 14 July 2012 08:39, Brian Granger <span dir="ltr"><<a href="mailto:ellisonbg@gmail.com" target="_blank">ellisonbg@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Carl,<br>
<div class="im"><br>
On Fri, Jul 13, 2012 at 10:23 AM, Carl Smith <<a href="mailto:carl.input@gmail.com">carl.input@gmail.com</a>> wrote:<br>
> Each to their own. I never got the dashboard myself. I don't think it makes<br>
> sense to have two interfaces when one of them can already do everything the<br>
> other is meant to do.<br>
><br>
> Google docs is different because a doc can't manage other docs.<br>
<br>
</div>I want to understand your view on this. In my view, each notebook is<br>
a document, just like Google Docs. In fact much of the design on the<br>
current notebook app is a blatant rip off of Google Docs. In your<br>
mind, how does the notebook differ from Google Docs?<br>
<div class="im"><br>
> If other people like the dashboard, that's cool. There's nothing really<br>
> wrong with it. I'm just a minimalist.<br>
<br>
</div>We are pretty minimalist as well. Initially I thought about going in<br>
the direction you are talking about = having no dashboard and a more<br>
complex UI in the notebook page. What I found though is that the<br>
notebook page grew a lot of complexity that made it feel less simple.<br>
<br>
Cheers,<br>
<br>
Brian<br>
<div class="HOEnZb"><div class="h5"><br>
> On Jul 13, 2012 5:59 PM, "Junkshops" <<a href="mailto:junkshops@gmail.com">junkshops@gmail.com</a>> wrote:<br>
>><br>
>> On 7/12/2012 7:30 PM, Carl Smith wrote:<br>
>> > I would suggest just creating a magic that can open a notebook, given<br>
>> > a path to it, using a bit of JavaScript.<br>
>> ><br>
>> > If you then started new IPython Notebook sessions with a new, empty<br>
>> > notebook, instead of the dashboard, the user could do everything Brian<br>
>> > suggested regarding the file system from within that notebook, and<br>
>> > open any other notebooks whenever they wanted with the magic.<br>
>> ><br>
>> > You could add the options to open a notebook in the same tab, and<br>
>> > either save and close the current notebook, or just delete it.<br>
>> ><br>
>> > Then there's no need for the dashboard at all and the Open... option<br>
>> > in the File menu can be gotten rid of too.<br>
>> ><br>
>> > Maybe I've missed something, but I just thought I'd add my two pennies.<br>
>> > I think cluster controls and drag and drop uploads can be done from<br>
>> > within a notebook too.<br>
>> I assume this is all fine for advanced users, but my 2bits as an IPython<br>
>> newbie is that the dashboard and file menus make IPy much more<br>
>> user-friendly for new users. I'd recommend keeping the dashboard and the<br>
>> file/engine tabs as the default, but perhaps there could be a command<br>
>> line option to disable the dashboard and start instead with a bare<br>
>> notebook when connecting to the nbserver.<br>
>><br>
>> I guess I don't understand why having the File>open menuitem is a<br>
>> drawback. Again, it's friendly to new users as opposed to having to look<br>
>> up a magic command.<br>
>><br>
>> Cheers, Gavin<br>
>> _______________________________________________<br>
>> IPython-User mailing list<br>
>> <a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
>> <a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
><br>
><br>
> _______________________________________________<br>
> IPython-User mailing list<br>
> <a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
> <a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
><br>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
Brian E. Granger<br>
Cal Poly State University, San Luis Obispo<br>
<a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a> and <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
IPython-User mailing list<br>
<a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
</div></div></blockquote></div><br></div>