Roode, Eric wrote:
Wx::Demo is great but I always have some trouble extracting the actual
part that I need to achieve something.
Yeah, me too.
I have this same issue. IANAP but I use wxPerl to create custom
interfaces to our ERP system. The perl backend allows me to load and
process XML and I cheat majorly by using wxGlade - Which however
doesn't give me the full power of wxPerl.
I am at the point where I would like to understand better how to use
threads or something that will allow a task to complete without locking
the rest of interface and also be able to break away from the wxGlade
dependency to allow me to use the full wxPerl toolkit.
My problem with code snippets is:
- I don't know where in the code to include the sample.
- I have no idea if I'm creating memory leaks or creating some
programmatic faux paus.
- I don't understand how a wxPerl application initializes and would
love to.
I suppose if we could answer these questions in a online book or
tutorial then the not so professional users such as myself would swell
the wxPerl user base which I understand is always good for Opensource
projects.
I seem to comprehend better when I have mostly complete samples. With
"this is done like this because..." explanations. An example of the
style I favor being the Oreilly Perl Cookbook.
I would pay over $100 AUD for a Oreilly style book on wxPerl.
