> >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. > > 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. > RAD works for rapid development of prototypes - going beyond that takes more thought but then encapsulating the required objects as components can work well - especially if there is some thought put into reusability. I would be in class where mostly the point is to get something that works as fast as possible and has little lifetime beyond current research project. RAD obviously is the key here but so is the library of gazillion objects from previous work. Going beyond prototype actually often also means taking it out of Delphi or making a client/server split, but I find it hard to beat Delphi for the prototyping. -- Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents. _______________________________________________ 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
