On Mon, Jan 31, 2011 at 3:59 AM, A.T.Hofkamp <[email protected]> wrote: >> Ok, but I'm asking if the module itself provides the same "heirarchies >> and relations" that I'm getting from the class. That is, when my > > No, you don't have inheritance with modules.
Ok. > That holds, until you add a second window, or you create custom widgets that > you use in your application GUI. > (At least, that is where I'd expect those things.) Well, the app already has many "windows". There's a preferences dialog window, an open files dialog, about dialog, quit confirmation dialog, etc. They're all quite simple and I don't see much benefit to having those be in separate classes. They're all part of "the app" and are in the app's main class. >> Well, one way that i'm attempting to make everything more readable is >> by getting rid of the term "self" that is littered throughout my >> program. > > Every Python programmer understands what self means. He/she knows instantly > what you are doing. > Don't confuse 'short code' with 'readable code'. While related, they are not > the same thing. There's a good point! Thanks for your input, it's been enlightening. -- http://exolucere.ca _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
