I'm currently researching for a web app we are planning to develop at German Cancer Research Center. We already started with the design process and have also build a prototype based on current GWT version (2.7). We first decided for GWT because we had some basic backend functionality written in Java existent.
After digging deeper into current GWT developments (mailing list and GWT.create 2015 videos) I started worrying because we make heavy use of technical stuff that seems to get dropped in future versions (RPCs, UIBinder, GWT.create) (We adhered to GWT In Action Second Ed. as a reference for best practices).
What do you think is a good way to prepare for future GWT versions?
After reading advise mainly on the Google groups I thought of GWT as a REST service provider as a replacement for the RP Calls and using React.js for frontend development. But I'm not sure what would be the advantages sticking with GWT compared to using Java frameworks (e.g. Jersey) for building the backend logic. However using native HTML frameworks for implementing the UI seems very promising in my opinion due to the fact that one has more control over native web rendering and therefore providing better browser support and responsiveness.
I would love to get some opinions on that and on the question on how to prepare for upcoming GWT releases.
Greetings from Heidelberg, Germany
Guido
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment