I pretty much agree with Ashton. I also like to us Gin (Guice for GWT) but learning that might be too much overhead to quickly prototype something.
On Thursday, January 17, 2013 2:27:25 PM UTC-6, Ashton Thomas wrote: > > I recommend using Activity and Places for organizing at a high level: > > https://developers.google.com/web-toolkit/doc/latest/DevGuideMvpActivitiesAndPlaces > > For a prototype, you may not need to follow the strict presenter format > (normally your Activity would act as the 'presenter') > > Again, since this is a prototype, I would recommend making the high level > views UiBinder files (For every activity have a ActViewUibidner java/xml > file). > > If you have to mix in other GWT widgets via java, it is probably fine. I > just wouldn't layout your app form java but instead have an outer shell > UiBinder and Uibinders for each activity. > > Maybe this will help > > > On Monday, January 14, 2013 4:48:33 PM UTC-5, nalin...@googlemail.comwrote: >> >> I am new to GWT... and building a prototype for a company.... >> >> 1.Should I stick to MVP pattern? Or without that pattern is also >> advisable? I feel that without that pattern is not a bad design.... as the >> project creation itself splits up into client and server code....... >> >> 2.Which method of UI build is better.. with GWT widgets with Java code or >> with GWT tags using UiBinder......? >> >> >> >> Regards, >> Nalini.K >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/EtkP6ZkslXMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
