As developers, our main task is to make the journey from A to B. A is you and the idea of an application, and B is the actual application, working well, a happy client and job (or flow of work) security for you.
As with any other journey, how you make it very much depends on where A and B actually are, and how they’re connected into transport options.
Recently a few people, including Troy (@troygilbert) and Paul Robertson (@probertson) have been asking about my workflow with TextMate and Sprouts.
So I screencapped an example of where I really feel like they are giving me a power-up. I’m sure you can do this level of code generation in many other IDEs, but the ease with which you can do it with Sprouts+TextMate makes it hard to resist.
or, implement the Mediator-Mini-Controller anti-pattern at your peril.
The robotlegs out-of-the-box implementation – what I like to think of as the standard issue trousers – relies on a version of the mediator pattern.
In this usage, the mediator’s job description is clear: deliver stuff from the application’s shared event dispatcher to the view, and from the view to the event dispatcher.
Like any good delivery service*, it also offers enhanced packaging for your exotic sending needs. Perhaps slipping your simple
MouseEvent into an air-mail-approved
A good delivery service also varies its delivery approach based on the type of thing being delivered. Simple letters belong in the mail box. Packages requiring a signature lead to a knock on the door. Fragile goods are handled carefully.