Nice job :)

While my initial reaction to all that cut'n'pasted stuff from ActiveState's website was negative ("C'mon, just post a link"), after reading your own comments I realized that there was no other way to do it.

I spent some time playing with Komodo 1.1 and I agree with most of your negatives here (apparently not much has changed in version 2). In particular, I especially agree with the first two items (Slow and Slow :) and the default font style being variable width. Having no search and replace (much less a Perl-ish regex replace) is also a major deterrent for me.

As for the debugger itself, I think it is missing something (as did the PDK, which I purchased).

Having grown accustomed to using XEmacs' perl support on UNIXen, which provides a gui wrapper around the standard command-line debugger ('perl -d'), I've gotten used to some niceties which Komodo seems to leave out. In particular, the command-line debugger's 'x' command, which produces a Data::Dumper-like output when dumping complex structures. In contrast, Komodo (and the PDK) seem to only display the standard notation (for example, ARRAY(0x11e5c0) or HASH(0x11e5b0)), which is next to useless.

If you want to explore a structure, you're reduced to explicitly requesting every individual element (which you sometimes don't know in advance, especially with hashes). Or, of course, you can use Data::Dumper; and print a dump, but this involves changing the source code for debugging (which sometimes is mistakenly not changed back). Not every perl script needs Data::Dumper.

dmm

If you GIVE a man a fish you feed him for a day
But, TEACH him to fish and you feed him for a lifetime