Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Remove the close command #295

Closed
jtpio opened this issue Dec 17, 2019 · 1 comment · Fixed by #298
Closed

Remove the close command #295

jtpio opened this issue Dec 17, 2019 · 1 comment · Fixed by #298
Labels
question Further information is requested ui
Milestone

Comments

@jtpio
Copy link
Member

jtpio commented Dec 17, 2019

Should the close command be removed, so the sidebar is always created and never closed?

While looking at #290, it started to feel a bit confusing to close the debugger sidebar while debugging. That also means users have to keep a mental model that consist of different states:

  • the debugger sidebar is open / closed
  • the toggle button is on / off

Removing the possibility to close the sidebar would simplify things greatly. There is only one way to turn on debugging and that is by switching the button on in a notebook, console or file.

For the users who have installed the extension but don't want to use it anymore, they could disable it from the extension manager and that would remove the sidebar.

@jtpio jtpio added question Further information is requested ui labels Dec 17, 2019
@jtpio jtpio mentioned this issue Dec 17, 2019
3 tasks
@jtpio jtpio added this to the 0.1.0 milestone Dec 17, 2019
@jtpio
Copy link
Member Author

jtpio commented Dec 17, 2019

So let's remove the ability to close the debugger sidebar for 0.1.0.

And open a new issue to reconsider that choice for 0.2.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested ui
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant