Page 1 of 1
Print Differences?
Posted: Fri 23 Jan 2015 20:08
by nurbles62
When we work on projects in the nuclear industry, we are required to provide printed (or printed to PDF) listings of all changes to the software. Is there any way to do this with CodeCompare? If not, is there any chance that such a feature could be added in the near future?
PS: It would be especially handy if we could print the differences for an entire folder (or maybe even folder tree!) with one command. Thanks!
Re: Print Differences?
Posted: Wed 28 Jan 2015 13:09
by AlexeyN
We are considering to implement some kind of printable report because we regularly receive similar requests, and our UserVoice also has such
suggestion.
But you are the first who requests diff report within a context of folder comparison rather than code comparison. Could you describe your needs in more details? How such report should look like? We assume three variants:
As unified diff. But changes will be divorced from context and it will be hard to understand changes.
As unified diff with context (several lines before and after diff). Number of lines should be settable. Such approach negates the lack or previous variant.
Whole document, where changes will be somehow highlighted, or even as Code Compare shows changes - at two panels with relation lines. But in this case diffs can be very big.
If you have example of a report that you think would be the best option, please attach it to your response.
Re: Print Differences?
Posted: Tue 03 Feb 2015 20:00
by nurbles62
We were only thinking of a basic batch-type operation to automatically create a set of reports for each file that exists in both folders. It would be nice if the output report files could be created in a new location using the same folder structure as the comparison. That could result in something like this:
Code: Select all
(old root) (new root) (report root)
\Folder1 \Folder1 \Folder1
\Folder2 \Folder2 \Folder2
\Folder3 \Folder3 \Folder3
Our naming convention for our manually generated reports has been sourcename.ext.diff, where we just add ".diff" to the end of the filename being compared. That makes it quite easy to map the reports back to the originals and having the reports in separate folders allows for multiple projects that have a main.c (or other common filename). Currently, we're just using the output from the diff tool redirected to a text file as our reports. Any improvements on the readability of that would also be great, but not a critical requirement for us.
Thanks for paying attention!