I agree. My thoughts are more towards integrating the good things from spiffyUI (spiffyui.org) into GWT. Wondering why no a great concept like SpiffyUI is not going mainstream but the same old JSF like Vaadin is getting into mainstream. The great thing about thick clients is that, they can be easily wrapped with android wrappers or IOS wrappers or even JavaFX wrappers.
On Monday, August 12, 2013 12:02:43 AM UTC+5:30, John A. Tamplin wrote: > > On Sun, Aug 11, 2013 at 2:21 PM, Rafiq Ahamed <ra...@eitworks.com<javascript:> > > wrote: > >> Dear Folks, >> Any thoughts on DropWizard framework (http://dropwizard.codahale.com/) >> as a backend for GWT. RESTFUL webservices is the way to go and I feel GWT >> RPC is an Anti-Pattern. >> > > GWT RPC was never intended to be the solution to all problems. It is easy > to use and allows you to send entire object graphs without much effort. Of > course, you get versioning issues and you can send entire object graphs > without much effort. > > You can already use JSON easily now if you prefer, and protos with a bit > more effort. REST vs other options is really more about the server anyway. > > >> And also, what about integrating ApacheCouchDB or ApacheSolr (Json >> style Schema less 4.4 version) as a backend for GWT so that the application >> can be developed rapidly. This is the approach I have taken for one of my >> new project. >> > > GWT has generally been server-agnostic, so I would expect any server-side > integration with a specific framework would be a separate project. > > -- > John A. Tamplin > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
