[[PageOutline(1-3)]]

= !PathView =

!PathView is a single-source, round-trip engineering, and model-based code editor. In other words, it presents UML-like views of classes, methods, and their relationships that are always an up-to-date view on the source code. Each editing in model or source code will change the other representation automatically in background. For that reason, it does not matter if developers favorite code or models for programming. 

== Description ==

Our !PathView tool is a mid-level abstraction of the system under observation that helps 





Create diagrams by manually, semi-automatically,.. refine them step by step to your needs interactively
[wiki:path:tutorial:typeHarvesting Type Harvesting] provides type infromation for better generating of diagrams?

Usueful for
discussion architectural decisions (has been shown very useful in our lectures, student projects,.. present the current architecture of their system/game...)
refactoring at a higher level point of view
filtering mehtods and classes of a specific concern (program comprehension)
documentation always up to date --> otherwise issues are colored


don't forget link to type harvester
tutorial screencast

'''See also the following tutorials:''' 
[wiki:path:tutorial:modelbasedEditor Model-based Source Code Editing] and 
[wiki:path:tutorial:typeHarvesting Type Harvesting].

== Screenshot ==

[[Image(pathViewLarge.png, 800px)]]

== How to Use ==


start from browser left click menu
or start by opening pathview and drag'n'drop
or start from pathFinder now hidden feature !!! but cool :D

 * First, you need a proper Path project that is selected as current. For more information see [wiki:path:pathProject PathProject].
 * To start !PathFinder choose the tool either in the world docking bar at the top (Apps -> !PathFinder) or in the world menu (open... -> !PathFinder).
 * After that, you will see a tool as in the screenshot above with a large white space in the middle. 
 * In order to get the execution history of a specific test case, please click on the rectangle in the upper left corner and choose the corresponding test case from the list.
 * Afterwards, the executed call tree is presented in the former white area below and developers can start exploring its execution history. 

== User Interface ==


=== Control Panel ===