MVVM-MVC-RAD Architectures with ColumbusEgg4Delphi

Loosely coupled is good. We don’t want our business logic and data access all mixed together, that makes our code harder to maintain. But we all love RAD and being able to create our applications quickly. Drop some components on the form, set some properties and write a little code and we are done! Unfortunately we usually end up with tightly coupled code.

Most architectures I’ve seen for keeping everything separated results in needing to write all the data binding manually. You still get to design your forms with the visual designer, but missing the data binding kind of sucks.