On 2 juin, 20:43, nogridbag nogrid...@gmail.com wrote:
Mainly because of habit - I always try to avoid mixing UI related code
with client/server code. IMHO, it seems similar to doing RPC calls in
a controller or view in MVC which I think is a big no-no.
Sticking with the article example,
i think at this point we should all probably see
http://code.google.com/events/io/2010/sessions/architecting-production-gwt.html
and see what they're trying to do there. Seems like Google decided the MVP
approach is obsolete, which might muddle the issue.
On Thu, Jun 3, 2010 at 09:26, Thomas
On 3 juin, 17:15, Tristan Slominski tristan.slomin...@gmail.com
wrote:
i think at this point we should all probably see
http://code.google.com/events/io/2010/sessions/architecting-productio...
and see what they're trying to do there. Seems like Google decided the MVP
approach is obsolete,
maybe it's that I expect too much MVPness from an MVP framework? as you
pointed out, the data widgets are pretty much the MVC observer pattern that
uses Request Factory to get it's stuff. From the programmer's perspective i
would argue that a data widget has nothing to do with MVP (not as i look
I also like to see
(1) how existing MVP frameworks such as GWTP, handlebars, etc response
to the new proposal of DTO, View, Activities and ActivityManager to
EventBus. Comments from developers of the MVP frameworks would be very
helpful.
(2) how to leverage ROO generated codes for JSONP Cross
@nogridbag
What are your reasons for not having the presenter make RPC requests?
The RPC Service is not a presenter itself. Probably the MVP model
should be called MVPSE (services, event bus) because that's what it
takes to make it really work.
On Jun 1, 4:04 pm, jocke eriksson jock...@gmail.com
Mainly because of habit - I always try to avoid mixing UI related code
with client/server code. IMHO, it seems similar to doing RPC calls in
a controller or view in MVC which I think is a big no-no.
Sticking with the article example, let's say you have two places where
you want to display
I don't like having two presenters either. I'm not quite sure that's
what's required. My presenters have an adapter parameter, so one
presenter can be coupled with different views depending on what
adapter is selected. Then, depending if it's a listAdapter,
editAdapter, displayAdapter, the same
Hi, I've been reading the articles on MVP recently, specifically the
articles here:
http://code.google.com/webtoolkit/articles/mvp-architecture.html
http://code.google.com/webtoolkit/articles/mvp-architecture-2.html
I've primarily worked with MVC in the past so this is my first
exposure to MVP
There are a few things that you should keep in mind before you try to
understand the MVP pattern
1. You don't have reflection or observer/observable pattern on the client
side.
2. Views depend on DOM and GWT UI Libraries, and are difficult to
mock/emulate in a pure java test case
Thanks for your feedback Sri.
1 and 2.
In my opinion, the shared object would be DTO's - not models. I don't
think they have to be the same. You can have centralized RPC, but
somewhere the request is made - I don't think the RPC requests should
be done in presenter unless there will only ever
Am I stupid or isn't EventBus an implementation of observer/observable.
2010/6/1 Sripathi Krishnan sripathi.krish...@gmail.com
There are a few things that you should keep in mind before you try to
understand the MVP pattern
1. You don't have reflection or observer/observable pattern on
I will answer my own question here, yes I am !! Thank god for the power of
google.
2010/6/1 jocke eriksson jock...@gmail.com
Am I stupid or isn't EventBus an implementation of observer/observable.
2010/6/1 Sripathi Krishnan sripathi.krish...@gmail.com
There are a few things that you should
13 matches
Mail list logo
