Ed Leafe wrote: > On Mar 9, 2007, at 10:39 AM, Nate Lowrie wrote: > >> I agree. I found out yesterday that dGrid has 1164 >> methods/attribute/properties and even dTextBox has 783. Of course, >> 350+ are inherited from wxPython and many more are internal methods >> that users do not need to know about. >> >> If you are going to do this, you really need to find a way to just >> pull the public API. > > I would go further than that. The public API contains a lot of > rarely-used, if ever, things that aren't needed 99% of the time. I've > used my own experience, as well as feedback from others, to only > abstract out the relevant stuff to the Class Designer Prop Sheet. > Look at the _getDesProps() method of ClassDesignerControlMixin.py > (currently at line 602); this is my attempt at defining what is > relevant and what is not.
Here's a link to the section that Ed refers to: http://svn.dabodev.com/trac/daboide/browser/trunk/ClassDesignerControlMixin.py#L602 If there are unneeded items in the API, we should remove them. If the item is in the API, it should be available through the tools. At least via a "show all items" preference. I presume that what is needed or not is contextual, though, so it is possible the tools can decide what is relevant to display given the context. However, personally I'd be kind of upset if I were looking for a method that I thought should be there, and eventually finding that it is indeed there but hidden. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
