Hi from Brazil, Guido.
I'm a heavy user of GWT and I have the same concerns as you do. I did some stuff to prepare myself for the transition, but I don't thing you need to panic out and starting avoiding "all the GWT" just because the future is coming... some functionality will probably be ported or supported in some way (either officially or by the community).
One good thing to do, not just to prepare for the future, but to allow your business rules to be called outside the Java/GWT world, is indeed to port your RPCs to REST (on the server by using Jersey, RESTeasy or any framework you like), and at the GWT side by using RestyGWT. The feel is the same as using RPCs: type safety, compile-time checks, asynchronous calls, with the advantage of your business rules being more portable.
At the client-side I still use UiBinder, but using as much as pure HTML as possible. At the current state, not using Widgets is really painful, so I'd still use them for better productivity, but always by using declarative UI (avoiding building the UI "by hand" using imperative language).
As for GWT.create, I don't see a real way to avoid using it for now. Just try not to create a framework based on it. If you only use it to invoke services/UiBinder, chances are that in the future you just need to replace them by "new".
(By the way, if they really remove the GWT.create call, they will need to rename the GWT.create conference =P)
I think the way to the future, regarding what to use and what to avoid (and how to avoid), will be clearer at the 2.8 release.
Hope that helps.
Gilberto
On Monday, August 17, 2015 at 8:39:52 AM UTC-3, Guido Schmidt wrote:
-- I'm a heavy user of GWT and I have the same concerns as you do. I did some stuff to prepare myself for the transition, but I don't thing you need to panic out and starting avoiding "all the GWT" just because the future is coming... some functionality will probably be ported or supported in some way (either officially or by the community).
One good thing to do, not just to prepare for the future, but to allow your business rules to be called outside the Java/GWT world, is indeed to port your RPCs to REST (on the server by using Jersey, RESTeasy or any framework you like), and at the GWT side by using RestyGWT. The feel is the same as using RPCs: type safety, compile-time checks, asynchronous calls, with the advantage of your business rules being more portable.
At the client-side I still use UiBinder, but using as much as pure HTML as possible. At the current state, not using Widgets is really painful, so I'd still use them for better productivity, but always by using declarative UI (avoiding building the UI "by hand" using imperative language).
As for GWT.create, I don't see a real way to avoid using it for now. Just try not to create a framework based on it. If you only use it to invoke services/UiBinder, chances are that in the future you just need to replace them by "new".
(By the way, if they really remove the GWT.create call, they will need to rename the GWT.create conference =P)
I think the way to the future, regarding what to use and what to avoid (and how to avoid), will be clearer at the 2.8 release.
Hope that helps.
Gilberto
On Monday, August 17, 2015 at 8:39:52 AM UTC-3, Guido Schmidt wrote:
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, GermanyGuido
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