On Thursday 17 May 2007 12:21, Paul McNett wrote: > Nate Lowrie wrote: > > On 5/17/07, Paul McNett <[EMAIL PROTECTED]> wrote: > >> IV.B may or may not be printed in a final book, since it'll end up > >> taking hundreds of pages if we print out every PEM for every class in a > >> repetitious manner. OTOH, it may be handy if the online API docs aren't > >> available. But some sort of guidemap through Dabo's class library should > >> be printed. > > > > I was thinking about this. An in between solution is to identify to > > the user all of the permanent properties (dPemMixin props), data > > properties (dDataControlMixin), etc. and when we identify the GUI > > class just say it has this and that set of properties. Then, we just > > need to tell what properties the GUI object has itself (like WordWrap > > for dEditBox). > > I like that idea. We can refer the reader to the pages that list the > PEM's for each superclass, even. The issue for the reader (I know because I'm one) is not finding the PEM but understanding what they do. -- John Fabiani
_______________________________________________ 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]
