I still haven't managed to do that, chromatic, and I've been busting hump to
learn wx. Reigning opinion dictates that Visual Basic and Lotus Notes be used
for such applications. I have a small dream of throwing down the code gauntlet
and doing a time trial for some application, but it's never going to happen at
work...
I have a chunk of a wx newsreader, but due to some issues with
fork and wx,
it's in limbo.
Most of the other things I've developed in wx apps have been to help me quickly
code other things, or as wx tutorials.
So far, there's been little cause or reason to develop a commercially viable
perl program in Windows because
- VC++ is much faster and more tightly bound to the OS.
- Visual basic offers impressive RAD that perl can't always match in terms
of gui development (caveats : GUILoft, wxDesigner, but I don't think they
measure up yet), along with Delphi and the other 'smaller' gui-oriented
languages that have stayed the course.
- Your clients will get your source code! Your efforts will be for
naught once a client has, and can alter and distribute on his own, the code you
worked so hard to market and develop. (caveat : perlexe, however, there are
reports that perlexe doesn't work well with wx apps.)
This might be similar to other development cycles in perl, though. I don't know
a lot of history when it comes to perl, but it's always been adapting to someone
that didn't like the way it did something. Maybe in time, there will be a good
GUI-development-oriented IDE (think VB) for perl. I think that there will need to
be, in order for perl to be competitive in this particular arena.
I could carp about wxWindow's lack of perl documentation and idioms, but that's
another speech for another time :-)
