Skip to main content

Need to Diagram your FoxPro programs?

I just got a news release from a company in Finland touting the latest version of Visustin, a flowcharting program that reported to work with Visual FoxPro, among other languages. I was definitely curious and for good reason - one thing I always used to love about FoxDoc, that old venerable project documenting tool, was its flow diagram. (granted it was in ASCII but it was still useful)

Here's a screen shot of Visustin with a sample VFP program:


It's very cool and I can definitely see where it would be useful in figuring out new pieces or "inherited" pieces of code. The fact that it also helps diagram VB, C#, Java, T-SQL and other code as well, definitely should make it invaluable to anyone.

You can open a program or simply cut and paste code in the screen and hit Diagram and away it goes.

It even lets you export out to Visio, Word and Powerpoint - great for code reviews! A bulk flowchart program (disabled in the demo) looks like it would let you chart out a set of files and create images based on the charts.

In my few tests, it looked like it supported the standard VFP constructs including newer ones such as TRY...CATCH, etc.

But then there are the things that caught me up:

1. While it was able to scope out a 2800 line program, it took several minutes to do so. If you were working

2. I wish it had support for other VFP components such as VCX and SCX files or perhaps more importantly, project and menu files.

3. I wish it had an open API so I could write an Addin for it - that said, it does have a command line syntax so you could do one if you needed to.

There's a free demo that you can try. It's limited but does give you a good idea on how to use it.

Press release: Visustin v4 Automates Flowcharting and UML Diagramming


Add to my del.icio.us

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...