Re^2: wxPerl fails with a cryptic message: "variable is not of type Wx::Point"

[Anonymous Monk]

some thoughts I wrote down

but these also have the problem of being C++ documentation which will require interpretation.

But its not a lot of interpretation :) is it?

You know :) I've read a few wxwidgets examples, and I've never needed anything more than the two rules from my wxWidgets / wxPerl / wxGlade tutorial, basically

wxWidget to Wx::Widget , wxWidget( to Wx::Widget->new(  s{wx([A-Z]\w+)(\()?}{"Wx::$1" .($2?"->new(":"")}ge; the constructor is called ->new

 wxWidget foo means a $foo which is a Wx::Widget object

That's it. There is one more that comes up if you view the c++ examples, and its dot to arrow  s{.}{->}g;

Ok, there are two more that everybody knows without trying, its ignore comments // /**/, usually taken care of by viewcvs if you're viewing online, or whatever syntax highlighting editor you're using offline

And ignore stuff in bold :) int *x, const wxPoint& pt

The only real issue I see, is that a lot of classes are stale

OTOH, take for example Wx/XS/Display.xsp its missing

    int w() 
        %code%{  RETVAL = THIS->w;
                %};
    int h() 
        %code%{  RETVAL = THIS->h;
                %};
    int bpp() 
        %code%{  RETVAL = THIS->bpp;
                %};
    int refresh() 
        %code%{  RETVAL = THIS->refresh;
                %};

Not a big deal, but this could be automated, much like the wxwidget docs are automated (now with more automation)

And there could be a wxPerlDocs distribution release, that uses File::ShareDir to package up a perl-ified version of the wxwidgets docs, that comes with a wxperldocs command that launches the docs in your favorite browser (mimeopen, openit )

update: http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk/docs/doxygen/scripts/swig_tools.py
http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk/docs/doxygen/

swigtools uses xml generated by doxygen to generate swig, swig can be used to generate perl bindings

without much work, perl-specific docs could be generated, missing member accessors could be exposed, missing methods could be exposed, missing classes could be exposed ...

<Reveal this spoiler or all spoilers in this node or all in this thread>

http://sourceforge.net/p/wxperl/code/3445/tree/dist-tools/trunk/?? Its unclear how often these beginWxPerlOnly amendments are updated in wxWidgets docs

there is module_info but it doesn't work too well with Wx but these oneliners do :)

<Reveal this spoiler>

[jmlynesjr]

AM:

Not coming from a C++ background, it took a few light-bulb moments and much reading and rereading before the C++ documentation started making sense. It gets easier to use with experience.

James