On 9/6/11 2:26 AM, Jacek Kałucki wrote: > I foresee many troubles with integrating this branch with Dabo. > Many advanced controls uses properties in place of method calls, > but property names could cover Dabo names, e.g. GetFont() -> Font, > where expected type is wx.Font in place of dFont.
The property name collisions are unfortunate. In Dabo's defense, we had properties first. :) However, because of the order of inheritance in the mixin classes, Dabo's property names override wxPython's, so the only confusion is if people wanted to use the wxPython-layer properties. In wxPython 2.8.x, the property names were always *in addition to* the method getters and setters. Are they getting rid of the public methods in 2.9? If so, then we will have some trouble (not insurmountable, though) calling the wx-level properties from Dabo. Paul _______________________________________________ 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/[email protected]
