Replies: 3 comments 2 replies
-
Thanks for the feedback @isidorn. Based on our usability feedback from many users, not having a per-notebook toolbar was confusing in the least, preventing usage at worst. Every other notebook implementation in the wild that we are aware of (and there are many) has a similarly located and populated toolbar. We have had countless requests for "Table of Contents" support for notebooks, even though it's been there for a long time via "Outline". To date we still receive requests for TOC even though this button is here. Variables is indeed specific to notebooks. In fact, it's specific per notebook (actually kernel), and arguably should be part of the notebook itself (not a global VS Code window). |
Beta Was this translation helpful? Give feedback.
-
I should mention that turning off this setting will remove that toolbar from the notebook, as the "alien-ness" was something that was discussed quite a bit when notebooks were first implemented. |
Beta Was this translation helpful? Give feedback.
-
Thank you for letting me know. I was aware that a big part of the UI is customisable, I just have strong feelings towards what are the defaults. My biggest concern with the current UI is that it just does not work on smaller screens. I suggest that the Jupyter team tries self-hosting for a day on 15-inch laptops to get a feeling of what I am trying to convey. |
Beta Was this translation helpful? Give feedback.
-
Top level Jupyter toolbar feels alien in the VS Code UI imho. We do not use editor level toolbars in other places.
Why are some of the actions needed here? For example "Outline" and "Variables". Outline is nothing Notebook specific.
fyi @minsa110
Beta Was this translation helpful? Give feedback.
All reactions