-
-
Notifications
You must be signed in to change notification settings - Fork 43
Add life-cycle button in toolbar of notebook and console panel. #239
Conversation
258b952
to
7647a30
Compare
7647a30
to
f1bb09f
Compare
f1bb09f
to
575dad2
Compare
Thanks for posting a screencast, this looks promising! |
a1cd1cb
to
a1040cd
Compare
a1040cd
to
bfbd959
Compare
290e200
to
1e1ab77
Compare
It would be nice to rebase this PR to grab all the latest changes from |
Also @KsavinN let me know if you want to share the work on this. Otherwise I'm also happy to pick this up :) |
I start rebasing. And i think i will need today spend some time for reading all your changes which you made :) |
1e1ab77
to
0ac1955
Compare
0ac1955
to
2e136d4
Compare
The simpler option here would be to focus on nbB to look at the debug window for nbB, and focus back on nbA to look at the debug window for nbA? Switching off debugging (via the button in this PR) will stop the debugger, and the state of the debug session will be lost. Here is a screencast from a while back to illustrate the flow: Do you think there is a use case for looking at the debug state for a notebook that doesn't have the focus? |
I think that it would confuse the user experience. |
That makes me realize it may be important to indicate which kernel is being debugged in the debugger pane. |
This came out of interviews I did with some potential users who specifically said they would like to have a view on the variable state of Notebook A potentially one in a breakpoint-stopped state while they were playing around with ideas in Notebook B. The toggle was to allow for both default-on (i.e., all notebooks always have debugging) and also for occasionally turning one off so you can look at a previous notebook's state. |
Yes, we discussed that last time with @afshin and @tgeorgeux and it sounds like a good idea (but let's track that in a different issue). |
Do you think we could do this after 0.1?
Sounds good |
The toggle behavior in this PR already supports that. But we should review workflows more carefully after 0.1, yes. |
src/index.ts
Outdated
if (this.handlers[widget.id]) { | ||
if (!debug.session.debuggedClients.has(debug.session.client.path)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe the two if
could be combined then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, definitely. Sorry need make break :)
I thought it would simply make it behave like a non-debugging kernel? |
54d886d
to
8ef7ea5
Compare
@SylvainCorlay What I mean is that I'm inside non-debugging Notebook B and I just want the debugger to still show me the debugging Notebook A state. This PR supports that sort of use case. But it's not more sophisticated in terms of switching kernels in the debugger (which is an idea that came out of when Tim and Jeremy and I spoke and should wait until after 0.1). |
8ef7ea5
to
2b67962
Compare
Since this PR has been open for a quite a while and need to be rebased regularly, I would be fine merging it as is and address the remaining points in follow-up changes. @afshin what do you think? |
2b67962
to
270d887
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @KsavinN!
@jtpio Yeah, let's merge and iterate, that's better. |
related to #214 and #154
Now:
toggle should stop/start session.
toggle should appear only for the supported kernel.
user cant run debugging/ set breakpoints it toggle is off
if user set breakpoints and reload page client will be automatically turn on the toggle