GWT approach for mobile

I need to develop a gwt app that requires support on desktop, mobile, tablet. I need to choose whether to use m-gwt or stick to the approach presented in Google IO 2011

Google IO 2011 approach seems to be -
1) create different views for different screen sizes
2) use deferred binding load only the relevant views according to the user agent 3) same presenter code

IO 2011 approach seems much simpler to me (and not tied with activities and places) but I am not sure if this approach is still popular and will work.

Can someone please let me know the pros and cons of these two approaches ?

Regards,
Sathya

---

You are mistaken in the assumption that mgwt is tied to Activities & Places, you can use it without using them. If you like using Activities and Places mgwt works of course very well. The approach presented at Google I/O is actually quite similiar on what mgwt does.

If you are looking into building one application for phone, tablet and desktop from one code base here is an interesting read: http://fahnenbruck.blogspot.de/2014/02/running-on-any-platform-using-java-with.html

链接地址: http://www.djcxy.com/p/44106.html

上一篇: smartGWT vs Mgwt（mgwt + smartgwt）

下一篇: GWT手机方式