Hi Alan! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Colburn ....... I've reached a stage where I'd really like to develop good coding habits, including keeping GUI code separate from the rest of an application. I'm
writing today for any tips on how to do this. So far, I've tended to just create properties in a business class corresponding to user/GUI input data, and functions returning information corresponding to GUI output displays. Are there other common ways to "bridge the gap" between the two (or more) classes? I'm told, for example, that you can create custom events in a business class that would automatically update the GUI anytime output values changed. If this is something y'all recommend, I'm very much in the dark about how this is done--I really don't understand custom events and how they are generated. If you could point me toward a good place to learn more on the topic I'd be much obliged. >>>>>>>>>>>>> Seperation of GUI code and databased code is a natural method when you use data modules and put your database code in them and refer to them in your forms. I am not sure whether more seperation than that is required. Object based code is more in the eye of the beholder. Making an application easy to maintain is the goal. No matter which methods you use, there are compromises. If you are interested, I have a Best Practises article I wrote a while ago which I can send you privately. Let me know. Tom Nesler Live long!... Code Well!... and Prosper!... V _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
