UI support for TimeTravel Debugging

[isidorn]

microsoft/vscode-node-debug#72

[isidorn]

@roblourens I like how you implemented this in the prototpye. Would you like to create a PR with your changes + plus a small adition that you only instantitate that aciton if stepBack is supported

And the label needs to be nls.localized.
And it also needs to be registered as a global workbench action.

[roblourens]

Sure, I can do that

[weinand]

@roblourens I've added the 'step back' request and the capability to the debug protocol. It is already available in the latest VS Code.
The mock-debug extension (available on the marketplace) implements step back and can be used to verify the UI.

[roblourens]

plus a small adition that you only instantitate that aciton if stepBack is supported
@isidorn you're talking about DebugActionsWidget.getActions? I could instantiate it the first time a session starts that supports stepBack, and on subsequent calls, either include it or not in the array that's returned? Or, it is possible to just hide a debug action with a css class if it's not supported?

[isidorn]

The actions get instantiated every time the widget gets created, so just instantiate it or not every time based on the capability.
No need to hide imho

[roblourens]

If I understand correctly, it looks like the widget is created once for the lifetime of the Code instance, and the actions are created once and cached and reused for every debug session.