Understand on Facebook – Become a fan
Wednesday, September 2nd, 2009Help us prove that not all programmers are anti-social, join our Facebook Fan page!
Help us prove that not all programmers are anti-social, join our Facebook Fan page!
One of our users, Chris Johnson, has developed a .NET sdk wrapper for the Understand API.
I have written a .NET sdk wrapper around the understand API during the early spring and last fall. I wrote it because I didn’t want to use Perl anymore, and I wanted the strong type safety of .NET along with it’s wonderful debugging tools.
The API is written in managed C++ (i.e. C++/CLI), and once compiled, can be accessed by any programming language that targets the .NET framework.
More details at http://www.scitools.com/support/forum/viewtopic.php?p=5550
Thanks, Chris!
Several users have asked for a CVS user tool similar to the one Ken created for SVN
This is easy to do, and you can create your own User Tools to do many different things.
I went and bundled some CVS commands into a User Tool. Just import it via the Tools | Configure User Tools | Import button.
I haven’t used CVS in years, so let me know if I got anything wrong
With build 476 we are adding an exciting new capability to User Tools. The ability to perform operations directly in the editor. In the the User Tool configuration menu (Tools | Configure User Tools), there are two new fields, Input and Output. As you might expect, the Input field lets you select what text you want to feed into your tool, and the output field lets you choose where you want the output redirected. (more…)
We’ve made several changes to the Understand Perl API recently. The largest change was upgrading from Perl 5.6.0 to 5.10.0 in build 473.
In addition to several cool new features like the smart match operators and switch statements, Perl 5.10 runs faster and has a smaller memory footprint. For more details on what the changes are and how to use
them, see the Perl 5.10 Release Announcement.
We are also in the process of adding Snapshot support for the Perl API for build 476. Now you can access historical versions of the code through your scripts as well. For example you can compare versions of files or write a script to compare metrics between versions. (more…)
We’ve had dependency analysis in Understand for many years. With B471 of Understand 2.0 we have consolidated it into a functional area of the tool, improved what it does and also added a few new dependency views.
The Dependency Analysis capability provides these features:
Read on to learn more about the Dependency Analysis capability and what we plan for it.
Or watch the video here.

Customers tell us frequently that they appreciate our weekly builds. They provide a constant stream of new features and bug fixes to Understand users. We like weekly builds because it means we don’t have to provide patch binaries to customers in dire need of an update and also because we hate the idea of a crash or bug existing in the wild longer than necessary.
But what do we do with new capabilities that we want feedback on, but aren’t quite “production ready”? We faced this with Understand 2.0, which had lots of new features/capabilities. Frankly, I think we took too long getting feedback and had to redo more than we would have liked once we did get user experiences.
Going foward we have big plans for Understand and the core technology it is based on. And so that we can get rapid feedback, we will be exposing features much earlier than we have in the past using a vehicle called “Scitools Labs”.
Scitools Labs isn’t some effort to make us look bigger than we are. We are still the 20 something person company we’ve always been. Instead, it is our way of asking… “this is where we are heading, what do you think?”.
Build 471, which will be released tomorrow, includes three Scitools Labs features:
I’ll write more specifically about each new Scitools Labs technology in blog postings prefixed with “Scitools Labs:“.
And remember, your input is the whole idea, so don’t be shy – let us know what you think.


Build 470, released today, introduces beta support for VHDL. E-mail support@scitools.com for instructions on how to enabble that support.