Thanks for this great article.
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.
Any approach can be used
Hi,
so is this the correct approach for it http://tinypic.com/r/236vq0/7 ?
When the Activity is created it gets the instance of the view and
creates a new presenter. It binds these two together. When the
activity is stopped (by place change) the presenter has to be set to
null.
That seems
Gal, guit seems to be heavily dependent on uibinder. Can you help with
a full online/offline reference of uibinder?
Regards
On 3/2/11, Brian Reilly brian.irei...@gmail.com wrote:
Hi,
so is this the correct approach for it http://tinypic.com/r/236vq0/7 ?
When the Activity is created it gets
The official UiBinder docs are valid for guit, the ui.xml part is 100% valid
but the java part of the docs is not, you can easily translate it.
http://code.google.com/webtoolkit/doc/latest/DevGuideUiBinder.html
*@UiField - @ViewField*
The difference between this two is that a @UiField can be of
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
Good article. Thanks.
Alan
On 3/1/2011 7:38 AM, Geoffrey Wiseman wrote:
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
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
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
Hi,
Thanks for nice article, helps in designing best and flexible GWT apps.
Saida.
On Tue, Mar 1, 2011 at 11:19 PM, Erik Bens bense...@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.
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
hello, thanks for sharing this. I am having some challenge with its
implementation though(using the Ray Ryan's method). How do I use the
go() method to serve multiple views if its local type is of
HasWidgets?
On 3/1/11, Erik Bens bense...@googlemail.com wrote:
Hi,
perfect overview - thanks! I
hello, thanks for sharing this. I am having some challenge with its
implementation though(using the Ray Ryan's method). How do I use the
go() method to serve multiple views if its local type is of
HasWidgets?
On 3/1/11, Erik Bens bense...@googlemail.com wrote:
Hi,
perfect overview - thanks! I
Thanks a lot for the article.
Ido
--
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
Guit doesn't use any of those patterns. In guit mvp is like uiBinder (only
two files, one ui.xml and one java).
*Login.ui.xml (this is what you already know):*
!DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
It looks to me like Guit leans toward the Abstracted Control View
approach, as indicated by the @ViewField annotations on the HasText
fields.
The @ViewHandler annotated methods are a little bit of a gray area.
I'm guessing the generated code would look similar to the view
implementation of the
On Mar 1, 3:14 pm, Brian Reilly brian.irei...@gmail.com wrote:
It looks to me like Guit leans toward the Abstracted Control View
approach, as indicated by the @ViewField annotations on the HasText
fields.
That would have been my reading too, although it seems as if the
abstracted controls are
On Mar 1, 7:03 pm, Christian Goudreau goudreau.christ...@gmail.com
wrote:
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.
Hi,
so is this the
17 matches
Mail list logo
