Ed Leafe wrote: > On Nov 16, 2007, at 1:13 PM, Paul McNett wrote: > >>> How is that different/better than the __get/setattr__ approach? >> >> __get/setattr__ is certainly easier to implement. However, it is much >> harder to debug and to understand what is going wrong when >> something is >> going wrong. AttributeErrors raised from code called from __getattr__ >> result in loops. >> >> I initially coded lots of things using that approach, and just got >> burned too many times. I'd feel very uncomfortable relying on that. > > OK, then where is the magic happening? If I have 'txt.FontSize += > 2', how does the proxy handle this *without* a __get/setattr__? The > 'txt' object, being a proxy, has no 'FontSize' attribute.
FontSize is defined in dPemMixin, at the dabo level. These dabo-level things will be at our proxy level. wx-level things will be at the level underneath that. Perhaps proxy isn't the best name, because our 'proxy' objects will define everything that is defined in a dabo GUI class. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
