Good evening everyone,

As I¹m adding to the design document, I find myself thinking more and more
about Part I ­ Introduction to wxPerl and GUI programming. I expect this
part of the book to be quite long. I think it may also become the most
important part of the book as it¹s here where potential newcomers will
decide whether its worth their time and effort to further pursue learning
about wxPerl.

To that effect I would like to turn to the members of this list. Imagine
that you have no idea what wxPerl is all about, but you have heard others
talk about it. What would you like to see in an introduction section that
would hold your interest and want you to keep reading more?

Steve has already mentioned installation of wxPerl. This will certainly be
included in Part I and deserves a thorough and concise writing effort. I
would also like to see a chapter entitled ³A simple wxPerl program². The
wxPython book has an exquisite example on page 35 in the PDF document. I¹ve
attached the page for your reference.

Finally, in relation to my use of the term ³geometry management², yes it
refers to ³layout². I¹m just used to the former term from my programming
days with X/Motif and Perl/Tk.

I really would be very interested to hear about your views on what to
include in ³Part I - Introduction to wxPerl and GUI programming².

Cheers,

Ron.

On 18/01/16 11:19 PM, "Steve Cookson - gmail" <steveco.1...@gmail.com>
wrote:

>    Hi Ron,
>  
>  Thanks for this.
>  
>  
> On 17/01/16 12:53, Ron Grunwald wrote:
>  
>  
>>  
>> 1. Introduction to GUI programming and wxPerl
>> 2. The wxPerl widgets (currently worked on in the design doc.)
>> 3. Geometry management in wxPerl (to be worked on next in the design doc.)
>> 4. Event handling in wxPerl
>> 5. Advanced Topics
>> 6.  
>>  
>>  
>  Is Geometry Management the same as layout?  If so I had to do a double take
> to work out what it meant.
>  
>  Maybe we should also have something about platforms and installation, which
> is always a joy!  It could be an appendix if you wanted, so that the flow of
> the chapters was not disrupted.
>  
>  Regards
>  
>  Steve.
>  

Attachment: wxPython.in.Action.Page35.pdf
Description: Binary data

Reply via email to