Uwe Grauer wrote:
> Dabo explicitly encourages you to use afterInit() instead of __init__().
> This should make it easier to use for non-programmers but it doesn't
> help programmers to understand the class structure as easy as it is in
> pure python.
I like this, not because it hides anything or is easier for a
non-programmer,
but just because it separates the Dabo code from the wxPython code. Because
the
Dabo classes are piggybacking on wxPython classes, trying to jam everything
into
the same __init__methods could easily turn into a nightmare. A few years ago I
started trying to write a set of wxPython wrappers similar in concept to Dabo;
I
wound up creating a separate set of initialization methods too, to avoid the
complicated interactions that arose when both wxPython and my wrapper code were
calling various internal methods.
--
--Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no path,
and leave a trail."
--author unknown
_______________________________________________
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]
