Sorry forgot reply to all -----Original Message----- From: Eytan Heidingsfeld [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 10:02 PM To: Richard Bennett Subject: RE: [Dynapi-Dev] Fw: widgetspec
Just to clarify: >>I see Tcomponent looks quite useful, with it's added functionality, but it's just a widget isn't it? what's the difference between ButtonImage inheriting from Dynimage, that inherits from dynlayer. Or ButtonImage inheriting from Dynimage, that inherits from TComponent inheriting from TWidget, that inherits from dynLayer (or not?), which inherits from DynObject. the second half is wrong. ButtonImage would inherit from DynImage that inherited from TComponent That inherits from TWidget. But TWidget inherits from no one. TComponent has a DynLayer inside. Thus seperating the core DynAPI from the widgets entirly. That is the main idea. Currently all widgets are BASED on DynLayers. If you think of DynLayers as a base class you are basically saying that your basic object is a Canvas(in a general term). When you base things on the TWidget/TComponent pair you are saying that your basic object is the plain TWidget. TComponent is the basic structure for a visual object! That CONTAINS a canvas but is NOT BASED on one! In my OO based opinion this is more correct coding. 8an _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
