diff --git a/help/advancedNavigation.html b/help/advancedNavigation.html index 9ebfb32a..21cf9aae 100644 --- a/help/advancedNavigation.html +++ b/help/advancedNavigation.html @@ -1 +1 @@ -Advanced Navigation

Besides the basic navigation language, the context tree also supports some advanced operators.

Jumps bring you directly to the sender context or the current callee context of the selection. With jump to present, you can also return to the tail of the program trace.



With the spawn option, you can open a second trace debugger on the selected subtree of the trace. Both debuggers will operate on the same instance of the program trace, allowing you to view different contexts at the same time. You can also drag any context from the tree into the world to spawn another trace debugger.



By marking a context as border context, you can reduce the complexity of the tree and hide all senders of the context. You can also define multiple border contexts. As you as you step out of a border contexts, the remainder of the tree will be visible again. You can also press space on a context to toggle whether it is a border context.

\ No newline at end of file +Advanced Navigation

Besides the basic navigation language, the context tree also supports some advanced operators.

Jumps bring you directly to the sender context or the current callee context of the selection. With jump to present, you can also return to the tail of the program trace.



With the spawn option, you can open a second trace debugger on the selected subtree of the trace. Both debuggers will operate on the same instance of the program trace, allowing you to view different contexts at the same time. You can also drag any context from the tree into the world to spawn another trace debugger.



By marking a context as border context, you can reduce the complexity of the tree and hide all senders of the context. You can also define multiple border contexts. As you as you step out of a border contexts, the remainder of the tree will be visible again. You can also press space on a context to toggle whether it is a border context.

\ No newline at end of file diff --git a/help/basicNavigation.html b/help/basicNavigation.html index 4e121507..fc77577b 100644 --- a/help/basicNavigation.html +++ b/help/basicNavigation.html @@ -1 +1 @@ -Basic Navigation

You can use the stepping buttons to navigate through the program trace. The TraceDebugger uses lazy stepping, i.e., the program will be only executed up to the currently watched position. If you step forward, the program will be advanced accordingly (just like in the regular debugger). If you step back, the TraceDebugger displays the recorded historic state of the program execution. This includes the selected context and the selected expression, the variables in the inspectors, and even the result of print-its in the inspectors.

Close the debugger and proceed the program normally.
Rewind the selected context to its start. Other than in the normal debugger, the code will not be executed again, but the historic execution will be displayed again.
Step into the next message send.
Step over the next message send.
Step to the next expression in the same method, including expressions in blocks.
Step back the previous message send.
Select the expression that will be executed next.
Jump to the sender of the current context.

Alternatively to the stepping buttons, you can also navigate through the context tree: Red-click any context to jump to the time where it was active. Shift + red-click any context to select its sender at its activation time. \ No newline at end of file +Basic Navigation

You can use the stepping buttons to navigate through the program trace. The TraceDebugger uses lazy stepping, i.e., the program will be only executed up to the currently watched position. If you step forward, the program will be advanced accordingly (just like in the regular debugger). If you step back, the TraceDebugger displays the recorded historic state of the program execution. This includes the selected context and the selected expression, the variables in the inspectors, and even the result of print-its in the inspectors.

Close the debugger and proceed the program normally.
Rewind the selected context to its start. Other than in the normal debugger, the code will not be executed again, but the historic execution will be displayed again.
Step into the next message send.
Step over the next message send.
Step to the next expression in the same method, including expressions in blocks.
Step back the previous message send.
Select the expression that will be executed next.
Jump to the sender of the current context.

Alternatively to the stepping buttons, you can also navigate through the context tree: Red-click any context to jump to the time where it was active. Shift + red-click any context to select its sender at its activation time. \ No newline at end of file diff --git a/help/contextFilters.html b/help/contextFilters.html index 7f93c050..2435887a 100644 --- a/help/contextFilters.html +++ b/help/contextFilters.html @@ -1 +1 @@ -Context filters

Another option to reduce the displayed complexity of the program trace is provided by context filters that hide irrelevant portions of the trace from the tree. To add a context filter, select an undesired context in the tree, yellow-click it, and choose "add filters". You can now add a filter by example, for instance, by hiding all contexts with a selector like the selected one, hiding all contexts from the same package, or all contexts that have the same receiver.



To revise the list of contexts, or to add a context without an example, do a yellow-click on the context tree (or just hover it and press escape) and choose "edit filters". Here you can select a filter type and choose all items that should be hidden from the trace. \ No newline at end of file +Context filters

Another option to reduce the displayed complexity of the program trace is provided by context filters that hide irrelevant portions of the trace from the tree. To add a context filter, select an undesired context in the tree, yellow-click it, and choose "add filters". You can now add a filter by example, for instance, by hiding all contexts with a selector like the selected one, hiding all contexts from the same package, or all contexts that have the same receiver.



To revise the list of contexts, or to add a context without an example, do a yellow-click on the context tree (or just hover it and press escape) and choose "edit filters". Here you can select a filter type and choose all items that should be hidden from the trace. \ No newline at end of file diff --git a/help/entryPoints.html b/help/entryPoints.html index 5f820c91..5cd4e8a8 100644 --- a/help/entryPoints.html +++ b/help/entryPoints.html @@ -1 +1 @@ -Entry points

There are several ways to open a trace debugger:

1. Debug a Process or a block by sending #debugTrace to it:

[4 / 6] debugTrace.
[4 / 6] newProcess debugTrace.

You can also send #traceAndDebug to start with a complete trace (instead of tracing the program lazily as you step through it):

[4 / 6] traceAndDebug.
[4 / 6] newProcess traceAndDebug.

2. In a normal debugger, press the new Trace It button on the right. This will replace the debugger with a trace debugger and was considered the most convenient entry point by testers.



3. To trace entire world cycles in Morphic, drop a tracer button in the world and click it:

TraceDebugger exampleWorldCyclesFor: 5 seconds.

For more inspiration, browse all invocation examples. \ No newline at end of file +Entry points

There are several ways to open a trace debugger:

1. Debug a Process or a block by sending #debugTrace to it:

[4 / 6] debugTrace.
[4 / 6] newProcess debugTrace.

You can also send #traceAndDebug to start with a complete trace (instead of tracing the program lazily as you step through it):

[4 / 6] traceAndDebug.
[4 / 6] newProcess traceAndDebug.

2. In a normal debugger, press the new Trace It button on the right. This will replace the debugger with a trace debugger and was considered the most convenient entry point by testers.



3. To trace entire world cycles in Morphic, drop a tracer button in the world and click it:

TraceDebugger exampleWorldCyclesFor: 5 seconds.

For more inspiration, browse all invocation examples. \ No newline at end of file diff --git a/screenshots/HistoryExplorer.png b/screenshots/HistoryExplorer.png index 4d8ad932..792ac499 100644 Binary files a/screenshots/HistoryExplorer.png and b/screenshots/HistoryExplorer.png differ diff --git a/screenshots/TraceDebugger.png b/screenshots/TraceDebugger.png index efda3ebc..6cc07be1 100644 Binary files a/screenshots/TraceDebugger.png and b/screenshots/TraceDebugger.png differ diff --git a/screenshots/addAsField.png b/screenshots/addAsField.png index b7d4d54d..39918fe9 100644 Binary files a/screenshots/addAsField.png and b/screenshots/addAsField.png differ diff --git a/screenshots/contextToolTip.png b/screenshots/contextToolTip.png index 16047cb4..ed63ba4d 100644 Binary files a/screenshots/contextToolTip.png and b/screenshots/contextToolTip.png differ diff --git a/screenshots/exampleMorphConstruction.png b/screenshots/exampleMorphConstruction.png index 7389fc12..6c817b75 100644 Binary files a/screenshots/exampleMorphConstruction.png and b/screenshots/exampleMorphConstruction.png differ diff --git a/screenshots/exampleMorphLayout.gif b/screenshots/exampleMorphLayout.gif index bf5ad037..02f0cd8e 100644 Binary files a/screenshots/exampleMorphLayout.gif and b/screenshots/exampleMorphLayout.gif differ diff --git a/screenshots/exampleShutDown.png b/screenshots/exampleShutDown.png index 0c6d00ea..f8e09c38 100644 Binary files a/screenshots/exampleShutDown.png and b/screenshots/exampleShutDown.png differ diff --git a/screenshots/exploreFieldHistory.png b/screenshots/exploreFieldHistory.png index a4ecc147..907ff9e2 100644 Binary files a/screenshots/exploreFieldHistory.png and b/screenshots/exploreFieldHistory.png differ diff --git a/screenshots/findContext.png b/screenshots/findContext.png index c7910ea0..954ef410 100644 Binary files a/screenshots/findContext.png and b/screenshots/findContext.png differ diff --git a/screenshots/historyExplorerCompactionMenu.png b/screenshots/historyExplorerCompactionMenu.png index 88a2db32..e3b84269 100644 Binary files a/screenshots/historyExplorerCompactionMenu.png and b/screenshots/historyExplorerCompactionMenu.png differ diff --git a/screenshots/historyExplorerSmall.png b/screenshots/historyExplorerSmall.png index 4b53a9b1..0710579e 100644 Binary files a/screenshots/historyExplorerSmall.png and b/screenshots/historyExplorerSmall.png differ diff --git a/screenshots/snapshotInspectors.png b/screenshots/snapshotInspectors.png index e50ea504..d8f76f05 100644 Binary files a/screenshots/snapshotInspectors.png and b/screenshots/snapshotInspectors.png differ diff --git a/screenshots/spawnContext.png b/screenshots/spawnContext.png index fddc417f..8d6b5449 100644 Binary files a/screenshots/spawnContext.png and b/screenshots/spawnContext.png differ diff --git a/screenshots/windowMenu.png b/screenshots/windowMenu.png index 7914c010..5083ae1d 100644 Binary files a/screenshots/windowMenu.png and b/screenshots/windowMenu.png differ