All geek questions in one place

GWT Mobile Approach

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

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

The IO 2011 approach seems a lot easier to me (and not related to activities and places), but I'm 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

+4
source share
1 answer

You are mistaken in the assumption that mgwt is attached to "Activities and places", you can use it without using them. If you like working with Activity and Places mgwt, of course, very well. The approach presented by Google I / O is actually very similar to what mgwt does.

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

+5
source

Source: https://habr.com/ru/post/1529949/

More articles:


All Articles