Report allows you to create report in two distinct
(1) Report on a set of files.
Report on a set of baskets.
From a distant view, (1) is used to dump the names
and attributes of files found in a basket. In contrast, (2) is used to
compare the contents of two or more baskets. Example
8 makes the purpose of this feature clearer.
Report on a set of files:
Click on from Main
toolbar to Open Session toolbar as shown below.
Then click on Report
Then the following display will appear:
Alternatively, use Shift+F1 as accelerator key.
This page contains controls used to generate
report on selected files.
The items in the right hand side list, order of which
can be changed using arrow buttons, stand for file attributes. The Report
will list attributes for each file in a tabular format, if you had checked
their check boxes. You can also specify gutter amounts between two successive
Contains file attributes that are displayed in report.
These allow you to reorder the attributes. For example,
you may choose to have the order of File
name, Local directory
and Remote directory
in your report.
This allows you to specify gutter between two attributes.
For a set of files, if two attributes, say Local
directory and File
in length, then you may desire to have the attributes aligned to left.
In that case, the gutter dictates the blanks inserted between the longest
directory name and filename afterwards, and for all other cases, necessary
blanks are inserted to construct the left alignment. For example, a gutter
of 4 between Local directory
and File name
will appear like this:
A gutter of 0 no more retains the tabular form. Instead,
a concatenation takes place as shown below:
Copy report to the clip-board
If checked, the generated report is automatically
copied to the system clip-board. At this point you can simply paste the
report to wherever you want, such as the actual report you are perhaps
writing for your co-workers or supervisor. This feature basically saves
you a Ctrl+C key-stroke, if you were to copy this text.
Open Interactive Window,
If checked, the Interactive Window, where the report
is displayed, is opened automatically. Otherwise, the Interactive Window
remains closed, if it was closed, and open, if it was open. Based on your
activities, you may prefer one mode to the other.
Discards user changes made to the list and assigns
the default values.
Report on a set of baskets:
By clicking on Report button from Session
tool bar, or by hitting Ctrl+R, you open the Report
dialog. By clicking on Baskets tab on that dialog, you get the following:
Baskets tab: This page contains
controls to generate report from comparing two or more baskets.
Typically, you create a basket and drag-and-drop
a local directory into the Files
list of TextMaestro. You do the same for another directory and
thus create a second basket. Then you select these two baskets to compare
them and create a report.
The report determines:
directories are having identical files. If so, you can also ask for a
diff between corresponding files.
directories are not found identical, a matrix is constructed that shows
addition and deletion of files from version to version.
As an example, if you have three versions of a certain
package, you can create three corresponding baskets, with each basket
containing its files in flat listing, and create a report where you will
see what files were added,
deleted or modified from version
1 to version 2 and version 2 to version 3. Note, you may have up to 64
baskets/versions to perform such comparison between
i-th and i+1-st version.
(The limit of 64 comes from the size of an unsigned
__int64, used to construct the above matrix which keeps track of basket-file
association through bit fiddling.)
baskets by examining:
Local directory tree structure.
Remote directory tree structure
If you choose the former - Local
directory tree structure, you are basically investigating the directory
structure assuming that the files are in local area.
Suppose you have version 1 and version 2 of a package
residing in two different locations in the computer and created two baskets
that contain the files from these two directories. To perform basket comparison
in a case like this, you want Local
directory tree structure.
In contrast, if the baskets are listing remote files
for two different versions staged in some remote system, possibly two
different systems, then you need the latter choice - Remote
directory tree structure. Note, to perform such comparison, you
do not need to have the files available in local system. Furthermore,
since the work is done using remote directory locations, you cannot perform
diff between corresponding files.
Thus, when you select Remote
directory tree structure,
Match case while parsing:
This allows you to ignore or honor case of filenames
and file locations when the tree structure is investigated. It is sometimes
useful when you decide that on Windows C:\test\Version1\Include\File1.txt and C:\test\Version2\include\file1.txt are actually the same
files for the comparison process. The same holds for VMS, but not for
List files common to all
This allows you to list files which are found in
Consider the following case. You want to compare
two (or more) versions of a package where there are tens of thousands
of files, most of which are actually present in all versions. You do not
care as much what is present in all versions as we care what were added,
deleted and modified from version to version. In a case where your interest
about the common files varies, you can check off/on this control.
Compare files common to
This allows you to verify if a file found in basket
i has been modified in basket
i + 1. If so, the diff
output will be placed in the report. Otherwise, expect no messages, for
no news is sometimes good news.