Donnal Walter <donnalcwalter@[...].com>  writes:

>  Patrick K. O'Brien:
>  > I'm starting to think the entire sizer API is ripe for an
>  > overhaul. If ever there was a place to deviate from wxWindows,
>  > surely this is a pretty good one.
>  > 
>  > Donnal Walter:
>  > > But the second source of confusion is that if one uses nested
>  > > windows (panels) and nested sizers to any degree, one ends up
>  > > with two entirely different containment hierarchies. The way
>  > > I have handled this is to build sizers into my panels, so that
>  > > adding a component to the panel automatically adds it to the
>  > > sizer. No muss, no fuss.
>  > 
>  > I think this is worth discussing as well.  Robin?  Any thoughts?
>  > 
>  
>  While we are tossing things out on the table, how about
>  wx.StaticBox and wx.StaticBoxSizer? IMHO, these should come for
>  free: wx.Panel should have a keyword argument (text=None) such that
>  if a value is given (e.g., text='my title'), the panel should
>  automatically include the wx.StaticBox and its sizer with an
>  appropriate sizer nested inside. YMMV

We could probably implement a StaticPanel that does what you suggest
and make it part of wxPython/lib.

In fact, we could put all of these sizer suggestions into wxPython/lib
and leave the existing sizers compatible with wxWindows for those
folks who want/need compatible versions.  (Though there is something
to be said for having only one way to do sizers in wxPython, so I'm
only +0 on that last suggestion.)

-- 
Patrick K. O'Brien
Orbtech      http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@[...].org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org