Debugging Worlds

[rickmcgeer]

What would you like to achieve?
This issue may be specific to me, but I am having trouble figuring out how to debug errors in frozen code that don't appear in the studio, largely because they have to do with initialization of the world. See engageLively/galyleo-dashboard#201 for an example. Another is engageLively/galyleo-dashboard#202. These issues only show up on frozen worlds, where the debugging environment isn't as good as it is in Lively.

How are you trying to achieve that
I'm tracing the issue in the console debugger in the Frozen world, guessing, and playing detective. Eventually I got them fixed, but it was difficult and painful. Source maps will presumably help.
I think the real issue is that the problematic code was in a subclass of the Lively world, and of course that isn't instantiated until you get to a frozen world...

[merryman]

This could be alleviated by providing source maps for the frozen bundles. This will not be covered by #1684 since that would include migrating the freezer to babel and that would make the PR too large. I will spend time on this once #1684 is merged.