Finding the method called from a UI action

[rickmcgeer]

What would you like to achieve?
When I was trying to fix engageLively/galyleo-dashboard#202, I had to figure out what routine was drawing the Halo in response to a ctrl-click. Eventually I figured it out by putting a debugger; statement in the Halo initializer and tracing the call stack, but there has to be a better way.

[linusha]

Whether or not this is better might be subjective, but what I like to do in these cases is utilizing the profiler tool of the browser dev tools. Start a recording, do what you want to learn more about, stop the recording. Lively does a lot of stuff under the hood each time the mouse is moved etc, so it pays of to be quite fast here.
Afterwards, you can see all function calls that were executed during your recording, and at least the chrome profiler also gives you a kind of "screen video" that allows you to map the timeline to visuals.
That way, you can easily find out what happened exactly when the halo appeared.

[merryman]

Agree with the solution of @linusha. Also once source maps land, this will be even more accessible. As to something that works within lively itself, we would need more powerful runtime inspection such as the one enabled by a lively debugger via nw.js