On Jan 25, 2006, at 10:36 PM, Don Taylor wrote:
A simpler alternative might be to have a context menu click item that brings up a dialog box for the sizer's properties. Maybe have a visible hot spot on each sizer slot border that would respond to a context menu click regardless of whether there was a widget in the slot or not.
Well, the LayoutPanel objects are really just dPanels, and could certainly contain more functionality...
I think that this is one case where it would help to have a bunch of people in the same room together with a whiteboard, sketching out ideas. You aren't coming to PyCon by chance, are you?
Makes a lot of sense. Maybe you should not have chosen almost the same name to mean something different from a standard wx sixer - although I guess that that only confuses folks who are thinking in wxWidgets terms. I was not going to try using a dGridSizer because I did not think that a dGridSizer/wx.GridSizer was very interesting. A dGridSizer/wx.GridBagSizer is interesting.
I agree; the base wx.GridSizer is of very limited use. One of the things we've done with the UI layer is try to name things according to what they are, not what the UI toolkit calls them. Remember, we plan on eventually wrapping Qt and Tkinter, too, so we're not bound by wx's occasional odd naming. We chose dLabel instead of dStaticText; dPageFrame instead of dNotebook; etc. This is a sizer that works in a grid pattern, so it's dGridSizer. If other toolkits offer a similar functionality, no matter what they call it, the Dabo class will use the same name for that toolkit as it does for wx.
-- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
