Yea, thanks Conor, Sure, in RAD, as it is in any Delphi project, you can certainly get away with simply programming the event handlers in the components (depending on the application). That should not preclude being able to create, for example, an Application Object that handles all your globals like the logged in user, or the company name and other details needed at times (e.g.; lbCompany.Caption := oApp.CompanyName) - where perhaps the company name is extracted from the database etc. In this example, oApp knows how to extract the company name, and perhaps even format it for display.
RAD does not mean ShiteProgramming, or NoThoughtProgramming. Its hard to find a definitive definition (?) for RAD and a quick search shows various descriptions from the tool itself (Delphi or VB) to the whole spectrum of Agile methodologies. However, I do disagree with the assertion that RAD does not lend itself to larger apps (or did you mean "Rapid Prototyping"). In fact RAD is an excellent development environment for developing even enterprise level applications. Some years ago I had the pleasure of working in a team of between 3-5 developers where we used a RAD approach (using Delphi) in an iterative and incremental development methodology to produce a very large scale corporate application and can confirm the approach as excellent and the development far outperforms a team up to 10 times larger using Java/J2EE in a refined waterfall approach for a similar sized project. Steve On Wed, Jul 30, 2008 at 8:27 AM, Conor Boyd <[EMAIL PROTECTED]>wrote: > Probably because I don't put the acronym RAD and the word "programming" > together as you have done. > > From my POV, RAD is generally taken to mean what the acronym stands for, > Rapid Application Development; i.e. drop some components on to a form, wire > up a few event handlers, voila. > > Doesn't mean I don't "do" OOP in event handlers and the little amount of > code that is required in such an app, but IMHO you're comparing apples with > oranges. > > RAD does not lend itself to larger apps which are intended to be easily > maintainable and intended to be worked on by a team of developers. > > Cheers, > > C. > > ------------------------------ > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *On Behalf Of *Steve Peacocke > *Sent:* Wednesday, 30 July 2008 8:13 a.m. > *To:* NZ Borland Developers Group - Delphi List > *Subject:* Re: [DUG] OO Programming > > Just an interesting observation - why do people think that RAD > programming excludes OOP programming? > > RAD is a methodology, OOP is a programming style. > > Steve > http://stevepeacocke.blogspot.com/ > > _______________________________________________ > NZ Borland Developers Group - Delphi mailing list > Post: [email protected] > 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: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
