Best viewed in the Internet Explorer.
Contact us at info@sourceglider.com
for feedback about MetriX.
Online Manual
Persisting the Analysis
Persisting the Analysis
After the analysis was computed, it may be useful to save it for future uses, especially if the computation time was
long enough. Stored analyses are persistent across Eclipse launches and it will be much faster to load the analysis than to
compute it form the scratch.
To save the analysis you need to provide a name for it. The default name is the name of the project if all Compilation Units
of the Working Set are located inside some particular project.
During the analysis saving process SourceGlider temporary transitions to the phaseBeing
Analyzed, all views and actions will be disabled until the analysis is saved. You can stop the analysis saving process by
pressing button in Analysis Progress
View.
Note: Each saved analysis is stored in the separate file. These files have extension .analysis and are located
by default in the Eclipse workspace folder. You can change this location in SourceGlider Options
Page.
You can remove particular stored analyses in the Save Analysis Dialog if they are no longer needed.
SourceGlider treats the analysis like the contents of a text file in a text editor - each time the analysis is
modified, it becomes "dirty" and SourceGlider suggests to save it by enabling
button on the Analysis Summary View. When the analysis is computed and yet not saved, it
is also considered "dirty". If you save the analysis or load some saved analysis, it won't be "dirty". The real power of the
"dirty" property is that each time you are trying to terminate the analysis, start the new analysis or exit Eclipse workbench, if the
current analysis is "dirty", SourceGlider suggests to save it (only for
Composite Analysis).
If you press Yes, analysis will be saved
If you press No, analysis will not be saved
If you press Cancel, analysis will not be saved and the action that could terminate the unsaved analysis will be cancelled.
If you set the Do not show again option checked, the "dirty" analysis will never be saved. You can cancel this option in
SourceGlider Options Page.
Size & Time - information about the size of Working Set, memory that is required to load this analysis and
time that was spent during computing of this analysis
Modified units - the list of Compilation Units that were modified since this analysis was computed
You can remove particular stored analyses in the Load Analysis Dialog if they are no longer needed.
If you are loading the analysis that has Modified units, you will be asked to proceed an
Analysis Update after loading.
If you press Yes, the analysis will be incrementally recomputed after it is loaded. In this case all analysis dataflow
information related to the Modified units will be up-to-date. Although incremental analysis recomputing is faster than
analysis from the scratch, it will still take some time to update the analysis. If analysis size is too big (you can find it
in Size & Time) and you are not planning to use analysis outcome on Modified units, press No.
If you press No, the analysis will not be recomputed. Analysis dataflow information related to the Modified units will be
out-of-date, but maybe still useful. Information related to all other units will be up-to-date. You will still be able to
perform an Analysis Update later (see Modifying the Analysis).
If you press Cancel, the analysis will not be loaded.