Open
Description
- Roles: System learner (understand the entire process), system expert (find a specific bug)
- Goal: Explore the construction/toolbuilding process or the rendering/drawing process of a complex morph
- Examples:
ToolBuilder build: (Inspector on: #(1 2 3))
Project current world imageForm
- Localize the text run that causes an invalidation in a
NewParagraph
during the setting inside aTextComposer
(see Fix rendering of embedded objects inCompositionScanner
babylonian-programming-smalltalk#55).
- Problems:
- Only linear stepping possible, no back-in-time display of prior construction/rendering states, no binary search to trace back certain changes to certain stack frames.
- Irrelevant stack frames distract understanding of the relevant process (e.g., Canvas clipping, Morph iteration).
- Intermediate result is hardly accessible: Need to reevaluate
aMorph imageForm
for every (relevant) step or to navigate toaCanvas form
> "screenshot" and update the inspector manually (bug inForm >> #=
).
- Possible solutions:
- :
- display the entire trace at once
- step into details later in the context of the original event state
- filter trace by method category/class/package
- similar to printbugger:
- overview of single drawing steps of
#imageForm
(maybe sandboxed) from which the user can jump to the responsible stack frame - slider for efficient time-traveling (maybe fish-eye slider)
- overview of single drawing steps of
- :