On Tue, Aug 3, 2010 at 4:17 AM, Daniel Carrera <dcarr...@gmail.com> wrote:
>
> What is the best documentation resource to learn wxPerl? Everything I
> can find is hugely out of date, and often poorly written:
>
> * The best tutorials are those from  Mattia Barbon and Jouke Visser.
> Together they cover only a small set of features, and they were last
> updated 6 and 9 years ago respectively.
>
> * The three "tutorials" at PerlMonks, dating back to 2001, are
> basically two program, and not well written.
>
> * I can't find much on the wiki. Apparently someone managed to delete
> everything in the old wiki. Did this happen recently?
>
>
> Can anyone suggest where I can learn wxPerl?


Your assessment of the state of WxPerl documentation is sadly accurate.

I am working to document what I can about WxPerl for the wiki.  So
far, I have mostly been translating API documentation from the C++
wxWidgets site, but I plan on writing some tutorials in the near
future.

What sorts of tutorials would you like to see?  Should I just update
and modernize the old Mattia & Jouke tutorials, or is there a need for
something beyond those?

Here are some resources that I have found that may help.

http://www.pnelsoncomposer.com/FAQs/wxWidgetsFAQ.html
    An old, but still somewhat useful, collection of newbie-oriented
    FAQs.  Oriented toward C++ programmers.

http://neume.sourceforge.net/sizerdemo/
    A brief guide to using Sizers. C++, but easily applicable to Perl.

http://www.perlmonks.org/?node_id=112816
    An article on handling images in WxPerl.  Old.

http://www.wxpython.org/
    The documentation for wxPython.  It's depressingly excellent -- it
    blows anything wxPerl-oriented out of the water.  I hope that the
    wxPerl community can strive for this level of quality.
    It is a useful class reference even for Perl programmers.

http://docs.wxwidgets.org/trunk/page_class_cat.html
    Documentation for the bleeding-edge wxWidgets library.  Much nicer
    than the docs for the "stable" library.


I hope these are of some use to you (and anyone else).

-- Eric

Reply via email to