You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking that when someone creates a new notebook, it would be nice to start it already with an empty Elixir block, and with the input focus there, so the user could start right away with writing code.
Google Colab and JupyterLab seem to agree with me on this one 😁
What do you think?
Cheers!
The text was updated successfully, but these errors were encountered:
If both Colab and Jupyter are doing it, it is likely for a good reason. And I guess it makes sense. People will use notebooks to run code first and foremost, so reducing the amount of clicks can likely help. :)
Yeah, initially we focused more on the whole flow, where the user creates a new notebook, types the title, insert a new section and puts the desired name, then inserts the desired cell. However, this is a rather idealistic path, because it's very likely that the user creates a new notebook as they would open an IEx session, in which case all of these actions get in the way.
There's always an option to fork a custom template notebook instead of starting with a blank one, but having a section and code cell in the default template sounds good to me :)
I was thinking that when someone creates a new notebook, it would be nice to start it already with an empty Elixir block, and with the input focus there, so the user could start right away with writing code.
Google Colab and JupyterLab seem to agree with me on this one 😁
What do you think?
Cheers!
The text was updated successfully, but these errors were encountered: