Same as most of the others on the list. A bit of both. RAD, Data Bound stuff for simple edit screens and reports, but OO structure for more complex screens and processes. Even the simple edit screens are based on top of a few useful base classes that do most of the grunt work.
Stacey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alister Christie Sent: Tuesday, 29 July 2008 17:08 To: NZ Borland Developers Group - Delphi List Subject: [DUG] OO Programming Do people on this list put in the effort to write proper object oriented code, or write mostly RAD style code, using datasets with data-aware controls and stuff - operating on a customer dataset, rather than the somewhat more abstract instances of TCustomer for example? (does this question make sense?) -- Alister Christie Computers for People Ph: 04 471 1849 Fax: 04 471 1266 http://www.salespartner.co.nz PO Box 13085 Johnsonville Wellington _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
