From: Brandon M. <bnd...@ho...> - 2000-11-30 20:07:03
|
Well said. // Brandon ----- Original Message ----- From: "Scott Andrew LePera" <sc...@sc...> To: <dyn...@li...> Sent: Thursday, November 30, 2000 1:39 PM Subject: Re: AW: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff > I hate to beat a dead horse here, but...:-) > > Pascal's WidgetX model is perfectly fine for most applications of > DynAPI2. For most apps there's really no need to go deeper than that. > Most widgets I've seen inherit directly from DynLayer and go no further > than that, anyway. It's well-documented and easy to understand. > > On the other hand, if you prefer a stricter, Java-like inheritance model > without worrying about having to preserve methods and properties, try > using the SuperClass object. It simulates OO very well, tracks class > instances, and manages super methods. But it's a little more difficult > to use. > > So there is a choice, and you're free to choose whatever suits your > task, or create an approach of your own. I myself like the > possibilities of SuperClass but more often than not WidgetX suits my > needs just fine. And I agree that bug fixing the API is more important > at this point than choosing "one true path" for a widget model. A > correct widget model is one that works. > > -- > scott andrew lepera > ----------------------------------- > web stuff: www.scottandrew.com > music stuff: www.walkingbirds.com > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |