FWIW,
I've used wxDesigner for several years now, and its whole methodology
for layout is based on sizers, which I find infinitely better as a
design principle than absolute placement--it was sizers that
convinced my company to move from Tkinter to wxPython.
This is one of the key drawbacks in my mind to Boa; I recently
experimented with it, and found it very difficult to work with after
having first used the somewhat simpler (IMO) interface of wxDesigner.
IMO, it *sorta* supports sizers, but it isn't geared to use them as
the primary means of layout the way wxDesigner is, and I found
it very difficult to figure out how to convince it to do what
I wanted, and found all the separate windows to be a burden.
OTOH, AFAIK, wxDesigner isn't really set up for inheritance; it
supports import of "foreign controls", but it doesn't allow you to
say that it's derived from a text control, and therefore has all the
defaults and sizing characteristics of them, etc. So, to use your
own or some of the contributed classes, you have to go to manual
control sizing to see your layout "properly", because wxDesigner
assumes a large box size for every foreign control. But I haven't
found this too terrible to deal with so far...
The other thing I don't know is how wxDesigner will play with 2.5,
whereas I believe Riaan Booysen has been involved in the 2.5 effort.
(Robin, have you had any conversations with Robert re: wxPython 2.5
and wxDesigner?)
/Will Sadkin
Parlance Corporation
www.nameconnector.com