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

HelenCr:

I agree that the documentation is pretty sparse which is why I ported the wxBook examples, see the GitHub reference above. I use the pdf document "wxWidgets 2.8.10: A Portable C++ and Python GUI Toolkit" by Julian Smart, Robert Roebling, Vadim Zeitlin, Robin Dunn, et al February 2009. It's for C++ with wxPerl and Python notes sprinkled in where the usage varies. The 2381 pages is a lot to digest, but it does get easier to use as you get the hang of how things translate. Most of what I have found so far demonstrates individual widget usage. I am having trouble finding examples of a more complete application. I understand that this may be difficult as real applications will probably contain modules that any given user may not have installed.

There has been a lot of recent discussion on the mailing list - wxperl-users@perl.org - about writing a wxPerlBook to parallel the wxBook. This is also a good place to post questions. There is also some activity on StackOverflow.

There is a new resource you should check out that collects several resources together - http://www.wxperl.it.

Then there's always http://www.wxwidgets.org and http://wiki.wxwidgets.org, but these also have the problem of being C++ documentation which will require interpretation.

James

There's never enough time to do it right, but always enough time to do it over...

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

Replies are listed 'Best First'.
Re^5: "Like trying to find water in a desert" by HelenCr (Monk) on Mar 09, 2013 at 10:36 UTC
James (jmlynesjr): Thank you for your positive answer. I have downloaded the Smart, Roebling et Al. document you mentioned. It refers to samples/examples, but does not contain them. Can you refer me to the examples? Referring to the dearth and scarcity of documentation on wxPerl, I can't seem to find good wxPerl documentation on wxListCTRL, and especially on tying a database table to a list control - while there is lots of Python documentation. It's interesting to note this emotional expression of frustration: http://osdir.com/ml/lang.perl.wxperl/2006-06/msg00010.html Quote: `Trying to search for solutions in the WxPerl arena is like trying to find water in a desert, docs and good examples are slim to none.` Unquote Many thanks again - Helen	[reply] [d/l]
Re^6: "Like trying to find water in a desert" by stefbv (Priest) on Mar 09, 2013 at 12:25 UTC
There is a new site: http://www.wxperl.it/, maintained by Mark Dootson that looks promising as a reference regarding WxPerl documentation.	[reply]
Re^7: "Like trying to find water in a desert" by Anonymous Monk on Mar 09, 2013 at 12:32 UTC
no offline docs (esp chm) download -- i live on the chm	[reply]
Re^6: "Like trying to find water in a desert" by Anonymous Monk on Mar 09, 2013 at 11:05 UTC
I can't seem to find good wxPerl documentation on wxListCTRL, and especially on tying a database table to a list control - while there is lots of Python documentation. Which python documentation do you consider good, wx.ListCtrl? wxListCtrl + samples/listctrl/listtest.cpp + samples/listctrl/listtest.h worked for me and ~~`wxperl_demo --show wxTreeListCtrl`~~ currently not displaying I even remember thinking this one is too long Wx-0.27/samples/listctrl/listctrl.pl Re^5: What's wrong with this Wx::Bitmap construction? ( Wx-0.27/samples/listctrl/listctrl.pl )	[reply]
Re^6: "Like trying to find water in a desert" by jmlynesjr (Deacon) on Mar 10, 2013 at 02:15 UTC
Helen: I have seen the references to the samples/examples, but I haven't found them either. The wxBook references a CDROM that didn't come with my book. The wxPerl Demo package is pretty good, but the wrapper code added to allow the mass of widgets to be included into a unified application can add to the confusion. In addition, the questions come in multiple layers. Once you get past the "Hello World" and individual widget examples, there's finding information on the style and structure of complete applications which is maybe not just a wxPerl issue. Just post specific questions here and to the mailing list and see what comes up. Please note when you cross post to multiple forums.:) Update1: See the file "TheBridge" on the GitHub repository to see where I have gotten so far in documenting the next steps. This is a draft that I hope to keep adding to. James There's never enough time to do it right, but always enough time to do it over...	[reply]
Re^2: wxPerl fails with a cryptic message: "variable is not of type Wx::Point" by Anonymous Monk on Mar 09, 2013 at 12:13 UTC
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? Read more... (2 kB) 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>	[reply] [d/l] [select]
Re^3: wxPerl fails with a cryptic message: "variable is not of type Wx::Point" by jmlynesjr (Deacon) on Mar 10, 2013 at 02:32 UTC
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 There's never enough time to do it right, but always enough time to do it over...	[reply]