On Dec 16, 2007, at 10:24 PM, Paul McNett ∞ wrote:
As I recall, what we rejected was the automatic addition of a panel in
the dabo library. IOW, when you create a form a panel is created in
the
background and when you do frm.addObject(...) we actually add it to
that
hidden panel. What this would have solved is all the weird
inconsistencies, lack of tabbing, etc. completely transparent to
the app
developer.
I think your memory is correct. The problem is that these two
syntaxes, which should do the same thing, would result in two
different results:
frm.addObject(dabo.ui.dButton, ...)
--> frm.panel.button
btn = dabo.ui.dButton(frm, ...)
--> frm.button
Let's discuss that again... I may be for it this time, if I was
against
it last time.
Regarding putting this in the class designer, I don't think I have any
issue with that.
My point in adding it to the framework is that it is a wx-specific
implementation detail, and as such would belong in the ui.uiwx
module. As far as I know, this requirement for a panel in order to
have tabbing between controls is only in wxPython. A cdxml file
represents a UI-agnostic description of a class design, and thus
shouldn't contain UI-toolkit workarounds.
One thing that might be possible in the Class Designer is an option
to create a base panel when creating the form. That would require
that instead of a blank form opening initially, the user is presented
with an 'Open/New' dialog instead, so that they can choose their
initial design surface.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
