Critical comments against form-based development
There are lots of methodologies to develop application. One of them, which I wrote about before here, is Event-Driven Development. However, many would misunderstand what the paradigm really is. The problem is this: Form-based development.
As you know, every program has its interface which interacts with users. That is the venue where events are triggered out. So what if the programmer focuses on the form itself? I'd say it's desperate. I don't intend to denounce the tool but the Embarcadero C++ Builder, which inherits Borland C++ Builder and is an IDE supporting easy disposing components on the form-base leads developers into the abyss.
[Remember MVC Model When Developing]
The output from form-based development cannot be recycled and that reduces the productivity. I know that is fine when programmer makes his code elegantly, though, the environment tempts to the stagnant solution. In my humble opinion, that is wrong. Event-driven development can be made in delicacy. The view part should be divided from the controller and the model, and the form just represents the external interface. Every event handlers can use encapsulated objects bound to the abstraction and re-usable.
It sounds like a trick. But the trap is always around us. We need to avoid it since the result can be catastrophe. Improving productivity is not on reducing wasting time but hugely on making something considerably fine flexibility and scalability.