That is a good solution...
And you will have one webserver that runs your server side application, for
different type of devices? Clients using laptop, mobile, desktop or I do
not know what(application written in other languages), will achieve the
same server side implementation? In this case,
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
applicationsI think a whole
Sorry, I forget about SmartGWT
SmartGWT.mobile supports packaging with PhoneGap to create installable
native applications that have access to on-device resources such as the
user's address book or photos.
2013. február 12., kedd 12:40:13 UTC+1 időpontban Tim Hill a következőt
írta:
Hi,
Wow - thanks for all the pointers guys! :)
Regarding the offline/online/syncing, I was hoping to implement a solution
using a PHP 'bridge' on the server side between the webapp and a mysql
backend - I have read that this is possible (restygwt?).
I have also come to the conclusion that I will
At a very high-level I think you need to start with the offline data issue
and define exactly what your requirements are for supporting offline.
- I haven't had a chance to go through all of this but may help
+ http://www.youtube.com/watch?v=Oic22dQMRXQ
- Also, I think we are in a critical time
Hi,
- GWT (e.g. deferred binding, declarative UI, ...)
- GWTP (MVP, form-factor support), Gin and Guice (dependency injection)
- UI, you have several options: GWT, mgwt (mobile/tablet form-factors), GXT
(desktop form-factor), smart GWT, ...
- Restlet: it has GWT support (as does RestyGWT)
GWT +
