4 ms·
Just as a counter point, I was a huge fan of the changes in version two. "Wizzy and interactive" can be incredibly important for a wide range of applications. H
by PieSquared 12y ago
Just as a counter point, I was a huge fan of the changes in version two. "Wizzy and interactive" can be incredibly important for a wide range of applications. Half the reason interpreters are wonderful is that they drastically reduce the "idea to running" time, and having interactive widgets can do even more for that. (Not to mention things like animations and UIs, which are just useful sometimes.) Similarly, notebooks are a great way for me to publish content, and a very large portion of the things I write are written as IPython notebooks.
As an aside, everything in IPython 2 is available from the keyboard and all shortcuts can be viewed by pressing the Help menu or 'h'. 'Add cell above' is now just 'a' (and below is 'b') when in command-mode. I expect that learning to use the new modal interface can be a bit of a hassle, but for me it turned out to ultimately be really awesome.
- joshvm 12y agoI think it's mostly getting used to the fact there's an edit mode and a browse mode. To me it seems that if you create a cell, 99% of the time you want to jump into it and start typing code - not adding another cell or selecting whether it's in Markdown/Python/Raw format or whatever. I suppose my biggest gripe is that I had to search for what changed (rather than simply what's new), given how much is different from a UI perspective it would have saved me a lot of time to skim a document. It's probably awesome who want that kind of functionality, and it makes the IPython platform so much more powerful for content delivery, but I wish it had a simple "Code and execute" mode. I always wondered why people complained about extra keystrokes in applications and now I know why :P