Can you take a look at this wiki entry and comment it: http://code.google.com/p/rupy/wiki/GWT
I think that a "least common denominator"* development strategy and hacking javascript, HTML and Java (HJJ) is a better way to go. What is it that GWT can leverage quicker than a good HJJ programmer. Except making the developer replacable of course; which is the whole point for companies, I know! * To not fragment the code, but instead implement one solution that work on all major browsers. -- 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.
