about which approach is used in each of the frameworks or if the frameworks are approach-agnostic.
In Gwt-Platform, you can use both approach.
Is this architecture also possible with the new activity / places approach?
Yes ! And just to let everyone know, the next major version of Gwt-Platform will be focused on Gwt 2.1 mvp integration.
Don't forget that Activity and place aren't intended to replace MVP focused framework, but to have a common base architecture, there's still a lot of boiler plate to write with Gwt Activity and place that you don't have to botter with any MVP focused framework out there.
Cheers,
On Tue, Mar 1, 2011 at 12:49 PM, Erik Bens <benserik@googlemail.com> wrote:
Hi,
perfect overview - thanks! I already worked with this architecture and
have to say it is very easy to handle after some tests. Additionally
use GIN for binding Views and Presenters will makes it easier too.
One question: Is this architecture also possible with the new
activity / places approach? Does someone has a diagram / sample for
it?
Erik
On Mar 1, 6:43 pm, Brian Reilly <brian.irei...@gmail.com> wrote:
> Very good article! Thank you for contributing it!
>
> I would be interested to hear from creators/users of the MVP
> frameworks out there (gwt-mvp, gwt-platform, gwt-presenter, mvp4g,
> etc.) about which approach is used in each of the frameworks or if the
> frameworks are approach-agnostic.
>
> -Brian
>
> On Tue, Mar 1, 2011 at 10:38 AM, Geoffrey Wiseman
>
> <geoffrey.wise...@gmail.com> wrote:> >http://blog.codiform.com/2011/03/view-presenter-interaction-patterns-...
> > If you're using Model-View-Presenter with GWT (or you're thinking
> > about it), there are a number of different patterns you can use to co-
> > ordinate between your view and the corresponding presenter. Ray Ryan's
> > "Best Practices for Architecting your GWT App" at I/O 2009 showed off
> > one pattern, Daniel Danilatos refined that for his "GWT Testing Best
> > Practices" presentation during I/O 2010, and a third pattern was used
> > in the "Large-Scale Application Development and MVP" article in the
> > GWT wiki. Using these and my own experiences with these patterns,
> > I've taken a small example, demonstrated how to apply each of these
> > patterns to that example, and written up some of the advantages and
> > disadvantages.
>
>> > For more options, visit this group athttp://groups.google.com/group/google-web-toolkit?hl=en.
> > These patterns are by and large available already in the sources
> > above, but by bringing them together and talking about some of the
> > pros and cos, I hope to save some people some of the sorts of
> > experimentation that many of us will have already gone through to
> > decide which one of these patterns works best for us.
>
> > --
> > You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
Christian Goudreau
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment