Once you learn the few conventions for converting the C++ to Perl you're all set ...

And therein lies my problem. Being fairly familiar with Perl Tk, I find the Wx Perl examples awkward (especially the new package declaration for each widget - arrrgh). I want to like Wx, I even bought the book, but whenever I try to learn it my brain fogs up, my eyes glaze over, and I go back to Tk.

The Wx Perl documentation says, as you do, to use C++ documentation and convert to Perl. However, there are no further details and my feeble brain has not been able to get a handle on this conversion. Would you (or anyone) be so kind as to elaborate on the conversion conventions you mentioned?

In reply to Re^2: Has anyone used wxGlade or wxDesigner to generate code by hangon
in thread Has anyone used wxGlade or wxDesigner to generate code by Steve_BZ

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.