On Oct 5, 3:02 pm, 007Prog <camarad250...@gmail.com> wrote: > I am also thinking about this. Google provide us with a toolkit. So, > what type of application can we create with this one that we cannot or > would be difficult with another framework. Because Now Noor must > choose a proper application that clearly shows that yes, > > THIS APPLICATION WOULD HAVE BEEN DIFFICULT OR IMPOSSIBLE WITHOUT GWT.
There cannot be a single such app; because GWT is JavaScript in the end, so anything you can do in a browser you can do in GWT, and vice versa (GWT is, before all, a Java-to-JavaScript compiler, everything else is extensible and even replaceable; yes, even the Java Runtime Emulation!) Where GWT is good is in taking advantage of the static typing of Java, to do static analysis of the code at compile time and automatically generate code based on this. The best example is GWT-RPC, but even better are, in the upcoming 2.1 release, RequestFactory and Editor. This is something that you just cannot do in "pure JS", but it doesn't make GWT able to create apps that would have been "diffucult or impossible" without it; you'd just have approached them differently (and of course have done much more work either upfront –by hand– or at runtime –using some kind of reflection–) -- 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.
