Donnal Walter wrote: > Each "presenter" (instance) needs its own "view" (instance). The class > attribute references a wxPython class. The resulting instance attribute > references a wxPython object (widget or container).
This is a reasonable idea, but it would be less confusing to give the class variable a different name, such as 'view_class'. I'm not aware of any specific name for this pattern. I suppose it could be regarded as an instance of data-driven programming -- you're putting a piece of data in the class that describes what is to be done, instead of writing code to do it. -- Greg Ewing, Computer Science Dept, University of Canterbury, Christchurch, New Zealand http://www.cosc.canterbury.ac.nz/~greg -- http://mail.python.org/mailman/listinfo/python-list