Hi, <aside> everyone, please click "reply all" (and edit as needed) when replying to posts on this list, It's very hard to get a conversation going if we have to wait two days for our posts to show up, even harder if half of them are only sent to the original poster. </aside>
Eytan, You've really got me puzzled. Wrapping a wrapper around an object, instead of inheriting it's properties is more correct coding ? I always viewed the inheritance as the main advantage of the dynapi coding style. Your widget-spec proposal would ensue a complete re-coding and re-structuring of the DynAPI widgets. If this is done for performance reasons, or because more powerful widgets could be built this way, I understand, but if it's purely a "coding style" issue, is it worth all users having to recode their widgets? Of course the old widgets could function alongside your new proposed system, but as I see it, the whole point of a widget spec would be to decide one widget model that is used for all DynAPI's built in widgets, and eventual add-on-pack widgets. Do you already have widgets functioning in this manner? I'd be interested to see one in operation. (with the TWidget and TComponent code) Cheers, Richard. ----- Original Message ----- From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]> To: "Richard Bennett" <[EMAIL PROTECTED]> Sent: Monday, November 19, 2001 9:02 PM 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/[email protected]/
