addObject() should be deprecated and eventually removed. There isn't a use-case for its existence, and came from Dabo's earliest days when attempting to shoe-horn idioms from FoxPro into Python.
Worse, the non-addObject() version is shorter: o = self.addObject(Cls, params) -> o = Cls(self, params) If you take this on, I believe AppWizard still generates code with addObject() which would need to be fixed, too. Paul On 7/9/11 3:36 AM, Jacek Kałucki wrote: > dabo Commit > Revision 6685 > Date: 2011-07-09 03:36:08 -0700 (Sat, 09 Jul 2011) > Author: Jacekk > Trac: http://trac.dabodev.com/changeset/6685 > > Changed: > U trunk/dabo/ui/dPemMixinBase.py > > Log: > Change some capitals to correspond to the derived classes. > > Diff: > Modified: trunk/dabo/ui/dPemMixinBase.py > =================================================================== > --- trunk/dabo/ui/dPemMixinBase.py 2011-07-09 10:30:01 UTC (rev 6684) > +++ trunk/dabo/ui/dPemMixinBase.py 2011-07-09 10:36:08 UTC (rev 6685) > @@ -29,7 +29,7 @@ > getPropertyInfo = classmethod(getPropertyInfo) > > > - def addObject(self, classRef, name=None, *args, **kwargs): > + def addObject(self, classRef, Name=None, *args, **kwargs): > """ > Create an instance of classRef, and make it a child of self. > > > > [excessive quoting removed by server] _______________________________________________ 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]
