We have a lot of power behind the IDE, but it is not always convenient to use.
For example, recently VSCode introduce a nice UI for adding logging statements to a running program and it was received with a lot of euphoria, the UI is simple, it is a contextual menu on top of a breakpoint:
With an inline editing experience:
We have the same capability, it is just not well known that it exists, and it is difficult to get to. By not being as easy to use, it removes the incentive to use for quick tasks:
This is a simplified version of what VS does. I think it would make a lot of sense to base our UX on that.
Short version -
There's a streamlined inline (peek) editor for breakpoint properties
A little toolbar appears when you move near a breakpoint icon in the margin that makes it super easy to open the properties
There's an "Add Tracepoint" context menu command in the editor that creates a breakpoint, configures it as a tracepoint, and opens the breakpoint editor with the focus in the train e expression field
We have a lot of power behind the IDE, but it is not always convenient to use.
For example, recently VSCode introduce a nice UI for adding logging statements to a running program and it was received with a lot of euphoria, the UI is simple, it is a contextual menu on top of a breakpoint:
With an inline editing experience:
We have the same capability, it is just not well known that it exists, and it is difficult to get to. By not being as easy to use, it removes the incentive to use for quick tasks:
We should better surface this capability.