Skip to main content
Jump to: navigation, search

Difference between revisions of "VIATRA/Query/UserDocumentation/LocalSearch DebuggerTooling"

< VIATRA‎ | Query
m (Fix typo)
Line 14: Line 14:
 
# Run the local search debugger by invoking the command on the toolbar of the Local Search Debugger view. The command reads the selection from the query explorer and initiates the matching: initializes and shows the plan.
 
# Run the local search debugger by invoking the command on the toolbar of the Local Search Debugger view. The command reads the selection from the query explorer and initiates the matching: initializes and shows the plan.
 
# Step or run the matching using the designated commands on the view's toolbar. Breakpoints can also be added when needed.
 
# Step or run the matching using the designated commands on the view's toolbar. Breakpoints can also be added when needed.
# The state of the shown search plan shows the state of the execution, while the already found matches and the current variable substitutions can be seen in the view's provided Zset viewer.
+
# The state of the shown search plan shows the state of the execution, while the already found matches and the current variable substitutions can be seen in the view's provided Zest viewer.

Revision as of 07:59, 29 February 2016

Installation

The Local Search Debugger Tooling is available from the update site extra.

Integration site http://download.eclipse.org/incquery/updates/integration

Usage

  1. Open the Local Search Debugger view in Eclipse
  2. Load the model and query definitions in the Query explorer
  3. Select the the query in the Query explorer
  4. Run the local search debugger by invoking the command on the toolbar of the Local Search Debugger view. The command reads the selection from the query explorer and initiates the matching: initializes and shows the plan.
  5. Step or run the matching using the designated commands on the view's toolbar. Breakpoints can also be added when needed.
  6. The state of the shown search plan shows the state of the execution, while the already found matches and the current variable substitutions can be seen in the view's provided Zest viewer.

Back to the top