Features

Analysis Report is the main and the most powerful all-in-one way of representation of analysis outcome. It is designed to display everything that SourceGlider knows about some particular Java Element. The view contains the set of dataflow queries, grouped by sections. You can find the list of all available queries in the Reference.

Intuitive UI provides the easiest way to navigate from the view directly to the source code, launch other views for concrete elements, show and hide groups of queries, mark the results of the queries in the code, etc. Powered by comprehensive precomputed analysis, this view goes far ahead of standard Eclipse code browsing views, such as Type Hierarchy, Call Hierarchy, Outline, Javadoc and others. It displays the dataflow information, that is never shown in Eclipse. For example, in one report you can watch the call graph of some particular method, its usages, dependencies, thrown exceptions, threads, monitors, actual result values, their types and many other useful information. You can even control the analysis process from this view.

Query Tree View is another way of representing the dataflow information in the form of Java Elements Queries like it is displayed in Analysis Report View. While Analysis Report View displays all the information on some Java Element, Query Tree View displays this information on demand. Here you need to select which query you want to display. You can find the list of all 145 available queries in the Reference.

Query Tree View is designed to show the history of selected Java Elements in the form of a tree. It is a kind of extension of the functionality of the standard Package Explorer. In the Package Explorer they tried to create the hierarchy that will contain all the Java Elements of the workspace: each project contains the list of packages, each package contains types, each type contains methods and fields, etc. Query Tree View can display arbitrary hierarchies of Java Elements.

Metrics View is yet another way of representing the dataflow information. Unlike Analysis Report View and Query Tree View, which represent dataflow information on the current Java Element, Metrics View displays that information on all Java Elements simultaneously, allowing to compare Java Elements by some numerical parameters (metrics) and find Java Elements with the highest/lowest metrics.

This feature is very useful in the tasks of source code quality improving. SourceGlider supports lots of different kinds of metrics (you can find the list of all 95 available metrics in the Reference). Some of these metrics could be interpreted as the measure of badness for the source code. You could quickly find the parts of code that have the most badness and refactor them.