Hi I think GWT is a good choice, you can have both client and server side programming with it, and runs on any platform. But my oppinion is that for mobile you should choose other technology like Codename one, especially if you would like to have true native applications....I think a whole web site, that runs in a desktop browser, can be very hard navigating in a mobile phone, with same UI. I mean you should plan anyway at least 2 UI-interface, one for desktop, and one for mobiles, indifferent what technology you use.
1. Having MGWT is a good choice for mobile, but: -if you have server side communication(gwt-rpc), you must use Phonegap too with mgwt(becuase GWT version compatibiliy). It is not a problem, but it means your server side arhitecture is also will have 2 implementations, one for desktop and one for mobiles...kind of. -you will have anyway 2 UI-interface (gwt for desktop, mgwt for moible) 2. You could have SmartGwt (mobile) to implement your proiect, because it says: -their cilent side widgets is compatibile with desktop and mobile and yout don't have to write twice the UI-interface, also they a SmartGWT.mobile widgetset too -also you can use the server side programming in SmartGWT, writing just once and runnig also in desktop and mobile (even gwt-rpc, but they does not recommend, instead using their datasource soulution which is not free) -a small problem with SmartGWT what you will face, that though you will have one UI interface, does not look so good in mobiles as in desktops, and the functionlaity should be tested. And of course native access you don't have, like Camera, File, Contacts, Geolocation...in smartgwt. So my oppinion is in short, for web pages, web applications on desktop use, GWT, SmartGwt or Gxt, or even JavaFx...but for mobiles don't write a whole website or webapplication, they have smaller screen, smaller memory, cpu, and whatever. There are a plenty of technologies in other languages too, which are better to use for mobile, they are sharp-edged to every problem what you face in case of mobiles. For example Codename one has the write once and run at any mobile platofrm concept, programming in java. Codename one has a WebBrowser component what you can use to navigate to a web page, if you want. But I think when you deal with server side data, your moubile UI.interface should be simple, easly handling and good looking... For desktop applications, use java swing.... With regards, Lehel Sipos 2013. február 12., kedd 12:40:13 UTC+1 időpontban Tim Hill a következőt írta: > > Hi, > > A friend and I are about to embark on developing and web application and > from what we have read/seen, GWT appears to be the most versatile. The > requirements for the project are as follows: > > - Platform agnostic > - Both server and client side storage (database) with syncing > - Mobile support > - Write it once (very nice to have) > > Before beginning however, I want to make sure that we are choosing the > correct development platform. I have also come across things like phonegap, > GWT-mobile and MGWT and it is these that I am slightly confused about - > which one(s) should we use, for example. What is the best way to integrate > them into the main GWT application? > > If somebody would be kind enough to take the time to guide us in the right > direction, it would be greatly appreciated! > > Cheers > > Tim > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
