July 25, 2003. A program, a shell extension, a scripting language. Rather all of the above, plus a lot more.

PowerPro may remotely resemble [AutoIt], which is another Windows task automator. But only because of their overall purpose. A closer look quickly shows they are very different.

The only relation between PowerPro and Tcl/Tk is this wiki, which seems to congregate all sorts of info about pretty much everything geek. But it could be interesting because PowerPro can do things that Tcl/Tk can't, like recognize key presses globally, capture text in child windows, customize your context menu and lots of other things I am too lazy to recall now. Believe me, the list is long.

PowerPro started out as a launcher bar. Configurable floating buttons that could launch programs and files or other very simple tasks. After a few years, PowerPro now has its own scripting language and even not considering its scripting capabilities, it has an absurd number of features for such a small program. It often intimidates new users, but those who get past it most often fall in love with it. Many learn to use it and dump half a dozen of those handy apps that sit in the tray, because PowerPro replaces all of them with plenty of advantage.

My own idea of it is that I can't stand using a computer without it. A vanilla Windows installation is just too insufferable for my spoiled taste. If I still use Windows instead of Linux, PowerPro is to blame for that.

PowerPro is written in C and accepts plug-ins, and has quite a few of them. The idea of making a Tk plug-in has come up and one bold programmer tried to do it, but a couple of issues made the task be left unfinished.

PowerPro is not open source, but it is freeware.

http://www.windowspowerpro.com
----
[RS]: Hm, the pages from that link show lots of praise, but I could not find details of the language. That would interest me (and others on this Wiki too, I think) most: why a new scripting language? Why not embed Tcl? How is the language different from Tcl?