If you use gwtquery, you can do all of your code directly in Java and GWT will be able to compile it.
If you use jQuery directly, you'll have to wrap the jQuery calls in JSNI (although you can wrap them in GWT Java functions and use those too in some cases), so GWT won't be able to optimize as well. However, jQuery has probably advanced quite a bit since the last version of gwtquery was released, plus gwtquery may not have had full feature parity at the time either. The latest version (due this weekend, October 16th) will have mobile web browser support (even for Blackberry OS 4.6) which GWT does not have built-in. So to recap: if you use gwtquery you'll get the GWT compilation, code- splitting, etc. benefits and the usual Java (e.g. debugging, etc.) benefits but you'll be missing features. If you use jQuery you'll get all of the features but will lose the compilation benefits (and won't be able to code-split the jQuery code, of course, although code-splitting should still work for everything else) and will need to make heavy use of JSNI to call the jQuery functions. On Oct 13, 5:03 am, Ignasi <murf...@gmail.com> wrote: > Hi all, > > To develop a gwt application with jquery code embeded wich is the best > option? and why? > > a) Use gwtquery-1.0-SNAPSHOT.jar lib > b) Use jquery.js directly > > Thanks a lot! > Ignasi -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
