>create a basic TWidget and a document on our standard > widget coding. Meaning how constructors, destructors, methods, properties > and events should be written. Yes, this would be a real help, now everyone is learning from example, but not all from the same examples, so different styles are used. sometimes this.superClass, sometimes this.dynlayer, etc etc.
I guess you would be well placed to set a draft widget standard, as you know what and how you want to import them into the GUI. Of course, if others post the specs they find important, that would be great too. Richard. PS Don't forget to click "reply all" on sourceforge lists. ----- Original Message ----- From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]> To: "Richard Bennett" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 11:49 AM Subject: RE: [Dynapi-Dev] WYSIWYG > Actually I've had some time recently and started working on it. Some time > ago a website was supposed to go up Anati was supposed to help me with that > but he disappeared from the face of the web. > I just got a volunteer programmer. > I've actually worked a lot on the GUI and functionality and bugs but haven't > released anything yet. Hopefully soon. > Another thing is that I would really appreciate if someone would organize > all the widgets availble. I think it would be a good idea now that we have > inheritance fixed to create a basic TWidget and a document on our standard > widget coding. Meaning how constructors, destructors, methods, properties > and events should be written. > Then I can even make a tool to import widget code to my widget specification > in DynPRD. > This is all quite a mess. Hopefully in the near future I'll make a better > release with some documentation and everyone will understand better. > 8an > > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
