Thanks to Mike and Huub for their quick and accurate responses. The
key is that you have to use "wxperl" (shipped with OS X) instead of
"perl" as your iinterpreter: something not mentioned in any example
or other piece of documentation that I could find.
I have no idea where the Mac OS X demo copy fits into the Grand
Scheme of things but it looks very bad compared to the wxPython
example that's (literally) in the next directory over. That demo has
a "README.TXT" file that says "Don't use 'python' to run these
things: use 'wxPython'." When you do that you get an error message
that says, in plain English, "You're on a Mac: use this other command
instead." The inclusion of a README.TXT file with the one equivalent
line in it for wxPerl would raise the number of people willing to
investigate it as a viable technology ("technology" = something you
don't have to understand to use, "art" = something you have to
understand fully to use) by many orders of magnitude. Things are
about the same for the level of commenting in the source code and
provide the (given people's time constraints) insurmountable barriers
to adoption. The Python stuff is massively and beautifully commented
whereas there are almost no comments in the Perl stuff.
Don' t mean to sound critical: it's Freeware and, by definition, a
labour of love that has, no doubt, involved the clever solution of
many obtuse problems. Sadly, however, working code only gets you
about 1/3rd of the way to something that will go into general use.
/Don
------------------------------------------------------------------------
-------
Good, fast, cheap! (Pick 2)
