Comments on: On the folly of representing a first name with a String

By: itoctopus

itoctopus — Sun, 08 Jan 2012 05:29:54 +0000

Interesting but I’m not sure if, in a company, someone writes this code others who will work on the same code will actually use it. This will probably lead to more code redundancy and will worsen the situation.

By: Uberto

Uberto — Thu, 05 Jan 2012 13:47:26 +0000

I completely agree. We did something similar on gae-gwt project and it worked like a charms. Much better than the standard annotation ridden JPA solution.

On a side note:
maybe it’s just because of gwt but we use View specific interfaces.

interface RegistrationView extends FormView {
void setUser(User aUser);
}

then in the implementation we associate the fields in User with the html elements.

Note that there is no getter because the user is not stored as field in the view but just translated in html/js and that our User is immutable, so when the presenter needs the user the View will create a new one from its fields (there could be also hidden).

By: Moreno Carullo

Moreno Carullo — Thu, 05 Jan 2012 07:16:20 +0000

Very interesting, Matteo.

On the presentYouselfOn method: I like it very much, it is indeed very similar to Seaside’s renderContentOn method that accepts an HtmlCanvas as an argument.

http://book.seaside.st/book/fundamentals/rendering-components/fun-with-canvas

— Moreno