Horst,
Yes, you are correct. Some things cannot be done completely in Python. After all, wxPython is almost completely a wrapper for wxWindows. There is the generic button class which are written in Python and some composite controls (but they are still built on top of wxWindows - using wxPanel as the canvas).
I have to decide the level of coverage of wxWindows. Some people don't want to deal with wxWindows at all (and from the responses I have received they are in the vast majority). Don't feel bad Horst that you are in the minority. 
I want to keep some fundamental coverage of wxWindows in the book without overwhelming the Python only programmer. It is a balancing act between both schools of thought.
Thanks for the input,
Gary
···
-----Original Message-----
From: Horst Herb [mailto:hherb@gnumed.net]
Sent: Monday, March 11, 2002 5:10 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxWindows Book
On Tue, 12 Mar 2002 03:40, dale@riverhall.co.uk wrote:
Why?
Decide on your target audience and satisfy them. If the book is aimed at
Python programmers, no reader's going to be interested in the wxWindows
stuff. Leave that to a book aimed at C programmers.
Gary,
wxPython is a wrapper around wxWindows. Even Python programmers will have
the need now and then to "touch" the C++ code, be it for debugging or
exetnsion purposes. Covering it will also help to understand a few
pitfalls in using wxPython. Last, but not least some extensions / new
widgets have to be written in C++ to be either possible and/or performing
well.
That's why.
Horst
_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users