Anyone finds Contacts2 confusing?

[JosephLi]

hi all,

I am trying to follow along whats in "http://code.google.com/
webtoolkit/articles/mvp-architecture-2.html" and I am just thinking
that
it requires too many classes and generics to construct a simple CRUD
app for a single
entity? I am posting this just to see if anyone feels the same
towards
that and have a better solution.

Looking at the code generated by Spring Roo's scaffolding, it seems it
is taking a more direct
approach and cutting some layers as well. I am still trying to go thru
the docs and trying to make sense of
both the new MVP-2 architecture and the Roo's approach.

Please feel free to comment, especially with any real world app
experience using the new MVP-2 architecture, was it really worth the
trouble?

Thanks,
Joseph

[Sean]

I think in general MVP is always going to be very wordy. There's a ton
of abstraction going on so that several developers can work on the
same app all at different levels and as long as the interfaces remain
intact, they won't step on each other's toes. I'm a single developer
working on my own website so I figured MVP wasn't a good fit for me
because I won't gain anything from the benefits of MVP.

But if I was doing this kind of work with several developers I could
see the allure in having that much abstraction where coders, artists,
and layout engineers could all work together and everything will just
work at the end of the day.

I haven't seen Spring Roo's scaffolding so I can't speak to that
comparison, but with any design architecture, I think you just have to
chose what's best for you and your project.

[Thomas Broyer]

On 29 juin, 14:27, Sean <slough...@gmail.com> wrote:
> I think in general MVP is always going to be very wordy. There's a ton
> of abstraction going on so that several developers can work on the
> same app all at different levels and as long as the interfaces remain
> intact, they won't step on each other's toes. I'm a single developer
> working on my own website so I figured MVP wasn't a good fit for me
> because I won't gain anything from the benefits of MVP.

MVP allows you to unit-test the "P", which I think is worth it even
for small projects (well, if you have somewhat "complex enough"
interactions that they would benefit from being unit-tested, but
that's quickyl the case even in small projects)

[PhilBeaudoin]

Relying on a good MVP framework can dramatically cut down on
boilerplate. Personally, I'm now building all my apps with MVP
(without Roo for now) and find that the result is much more pleasing
to look at and develop than any GWT code I've written before. I would
say this is true even for single-person projects. Also, relying on a
standard framework could make your app compatible with annotation
processors like the new gwt-mvp-apt (http://www.draconianoverlord.com/
2010/06/28/gwt-mpv-apt-1.1.html), which could let you cut down even
more on boilerplate!

[JosephLi]

Thank you guys for all the insight. As Sean and Thomas pointed out, I
do believe that being able to junit test the "P" is a good idea and
thats what drawn me to look at the MVP-2. It was only after looking at
the example and realized that it took so much effort to it and make me
think it might be counter productive.... at least in the short term.
Long term though I am pretty sure it with proper architecture a big
project will ripe the benefit. Mean while, I will keep looking into
that and see what I could come out with and be more comfortable with
all the boilerplate codes...

And PhilBeaudoin, thanks for the pointer to a framework for helping
with the boilerplate, I will definitely look into that and perhaps
that might be what I am looking for in.

Thanks for all the comments and tips,
Joseph