" implementation outside of it by handwritten JavaScript"
not at all , gwtquery is a jquery reimplementation in gwt and enables
the developper to develop as with jquery in java. For jquerymobile, we
use the gwtquery plugin mecanism to wrap the jqm library, and we still
continue to develop in java..
transport of objects between client and server. If your mobile
> application can be built wholly in javascript( and, hence JQuery), GWT
> is probably an overkill. Please examine whether GWT is the right
> choice for your application needs.
>
> J.Ganesanwww.DataStoreGw
I agree :)
I use gwt in a minimalistic way, only to well structure my code, and
gwtrpc (even if I use more and more restlets for communicating with a
server); the benefit is also debugging, and optimization... but the
cost for a big project (it is our case) is the compilation and
deployment tasks..
Hello,
I've noticed a samplemobilewebapp in the GWT 2.4 repository, and I've
taken a glance in the code It frightened me by its complexity...
By comparison, doing an application with Jquery, JqueryMobile
(+phonegap eventually) is quite simpler and easier to do... And if you
want to do it with g
GWT is built uppon a subset of Java 1.5/1.6... but it is not
mandatory , as a java2js translator, to be only compliant with Java...
We see in many concurrent solutions like Flex, Silverlight,
Wickets, ..., that these solutions abuse of XML (mxml, xaml, ...) to
describe declaratively their interfac
