Ed Leafe wrote: > On Aug 13, 2007, at 11:09 AM, 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. The class hierarchy gets hidden by this which feels >> unpythonic to me. > > There is no "hiding"; everything is discoverable if you choose to do > so. There is so much potential for damage due to incorrect superclass > invocation of __init__() that it makes a lot more sense to avoid the > potential for harm. Additionally, the class hierarchy for UI toolkits > is guaranteed to be different when going between wxPython and, say, > Tkinter, so programming to __init__() is poor practice, as you're > writing to an implementation instead of to the design. >
Yes, you are right. I'm more complaining about the missing hierarchy documentation here. If __init__() would be used the documentation clearly should be in the source. Your documentation style is always too sparse (at least for me). Uwe _______________________________________________ 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]
