The wxPython demos are full of examples of sizers within sizers. But my
guess would be that someone else on the list will submit a very simple one
for you. However, I thought I'd offer this suggestion about how to proceed
in general since I've been using wxPython for only two or three weeks.
I got pretty far pretty fast in terms of understanding by finding one of
the demos that did part of what I wanted and then modifying it. This was
particularly useful in the case of sizers which are a bit difficult to
grasp. Note that each demo tends to be "wrapped" in a kind of
"demo-driver" that sets up the app, and one of the first instructive things
to do is to modify the particular demo so that it will run stand-alone
(watch out for some initialization actions that might be "hidden" in
unsuspected parts of the code). Once you do that, then you can start
messing with the various parts of the demo, changing some of the values of
parameters to sizers (and to the Add methods), etc. You learn a great deal
by doing this and also end up (at least in my case) with the sort of thing
you wanted in the first place. The "proceed by incremental modifications
of a demo" approach also allows you to start with something that works and
then to change it under controlled conditions, backing up when something
you've changed doesn't work.
I have a lot of sympathy for those who have difficulty with sizers. Every
GUI library has its own approach to layout, and it always takes a bit of
time to adapt to a new one. I haven't done serious (i.e., non-HTML) GUI
programming for about 8 years, and then it was at the Motif/X level and
using some of David Flanagan's XMT libraries. From that perspective, the
conceptual model of sizers in wxWindows seems a bit odd, and I miss some of
the more "classic" approaches to layout managers. But I'm getting used to
it, and using the demos as a laboratory helps a lot. Also, some good stuff
is hidden in various parts of the wxWindows documentation and just takes
time to stumble across or discover. Don't overlook the "Topic Overviews"
section of the documentation. I will grant you that it would be a great
help to have complet wxPython documentation than having to rely on the C++
doc for wxWindows -- especially since a number of methods in the Python
classes seem not to be documented and you seem to learn about them by
seeing them used in other people's code. But things could be a lot worse.
ยทยทยท
--------------------------------------
Gary H. Merrill
Director and Principal Scientist, New Applications
Data Exploration Sciences
GlaxoSmithKline Inc.
(919) 483-8456