On Jul 6, 2006, at 7:54 AM, Simen Haugen wrote:
One thing I think can be a really big annoyance is the fact that
you can
introduce bugs by using the wrong functions (wx instead of dabo).
Usually I can see the dabo methods since they use lowercase letters
if a
wx method exists. But several dabo methods starts with uppercase
letters.
Dabo uses a convention that attributes/methods all begin with
lowercase, while properties begin with uppercase. If you find places
where that is not being followed, please report it as a bug.
Also - as you just noted - dabo won't wrap everything from wx, so
sometimes you need to resolve to mixing dabo and wx. This will
compromise the cross-ui plans as you'll need to make specific calls to
the underlying library (but I guess that's a little far into the
future).
Yes, that's true, but we're trying to approach the interaction with
controls in a non-wxPython mindset. What is it that you need to do?
Many times the wxPython approach is good, and many times it reflects C
++ implementation details. If you find yourself wanting to work with
a control and feel that you have to resort to raw wxPython code to do
it, let us know. Either there is an existing Dabo way to solve the
problem, or it is something that we may need to our API.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
