Hello, thanks for your considered reply. I'm not the wxPerl expert but I've done a project or two in it. I think with all respect that you've gotten behind the wrong side of the axe. Specifically, you are reading the docs for the C++ libraries which are wrapped by wxPerl. You do not program in C, you program in Perl.

There is no ASSERT needed in Perl of course, in fact I don't remember that line at all to tell you the truth. Maybe it is needed to stay sane in C++ programming with wxwidgets, but I have no experience doing that myself. It's easy to debug wxPerl since it's perl and you have stderr output on the console too, plus a logging module. You suggest wxwidgets is immature but a glance at wxwidgets.org shows that is untrue, in fact lots of neat cross-platform C++ projects (like Xara for instance) use it.

It is true that not every single routine has been wrapped, but the critical mass has been way exceeded IMHO. There is a very active mailing list and in fact there are some extra perl functions added while some duplicate C functions are not. There are also some which were skipped as not seeming important. When people find them important, so far as I can see it gets wrapped extremely fast.

The wxwidgets C++ libraries are also a moving target and advancing/growing very quickly. This is a good thing. I do in fact use the C++ manual when seriously programming wxPerl, since it is extremely useful. There are also a lot of third party C++ modules in the contributed code section, and I wouldn't mind seeing some of those wrapped too. Perhaps lack of a wrapped video contributed module is significant I think though there is ActiveX.. anyway it is available for wrapping. The wxperl wrapping of wxwidgets is in general quite useful and has struck me as being more interesting than Tk though I would like someone with much experience in both to weightin on that. Also I wonder if sdl-perl and gtk-perl are faster, since I remember a neat game (sdl perl I think) called Frozen Bubble. I wonder if it is doable in wxPerl yet. (It uses Ogg Vorbis). I'd like to see it easy to do animation and multimedia scripting in perl, in wxPerl. And being a lazy perl programmer in a good sense (I think) I'd like to see it even easier to make apps than it is now. (It's easy but you still have to tell the computer what to do.)

As for the example you note, I just checked the manual (for wxwidgets 2.6.2) and your post appears to be already obsolete. There is no wxPerl note as you mention for the three subroutines you note. And I built a wxPerl app with custom icon and title (true I was setting not getting) nearly a year ago.

In conclusion I have to say that while I greatly respect your posts in all other areas I really think it is time to take another look at wxPerl. In particular, look at the wxPerl demo.pl application which shows you the source code for each window as you demo different functions, it is eye-opening. There are already a lot of users but I would like to see twice as many and it seems the barrier to that is impressions similar to yours.

WxPerl will of course continue to grow, I hope, and I would not mind seeing it get easier and easier. Currently I think it does a very good job of letting you override all widgets and window types to make your own custom reusable widgets and windows as packages which can be added to CPAN. Anyway, slide over to wxperl.sf.net and see what the fuss is about!

Cheers, Matt

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.