Comments on: A first glance at GWT http://blog.sommestad.net/2009/03/a-first-glance-at-gwt-2/ Web and Cocoa development through the eyes of Kristofer Sommestad, a SWAD developer. Tue, 06 Jul 2010 11:48:28 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Trying Google Web Toolkit again – and liking it | Really Aced http://blog.sommestad.net/2009/03/a-first-glance-at-gwt-2/#comment-45 Trying Google Web Toolkit again – and liking it | Really Aced Mon, 11 Jan 2010 09:26:29 +0000 http://reallyaced.wordpress.com/?p=46#comment-45 [...] it Development, JavaScript Monday, January 11th, 2010 @ 11:26 | Follow comments A while back, I tried out Google Web Toolkit to see if it was any interesting. My main concerns after that early glance was the stability of the [...] [...] it Development, JavaScript Monday, January 11th, 2010 @ 11:26 | Follow comments A while back, I tried out Google Web Toolkit to see if it was any interesting. My main concerns after that early glance was the stability of the [...]

]]> By: esset http://blog.sommestad.net/2009/03/a-first-glance-at-gwt-2/#comment-44 esset Mon, 09 Mar 2009 15:18:46 +0000 http://reallyaced.wordpress.com/?p=46#comment-44 Third-party JavaScript frameworks can be used by creating interfaces via GWT-API-Interop (http://code.google.com/p/gwt-api-interop/). There's a few community projects going on where others have already created these interfaces, so it should be OK to use jQuery or PrototypeJS for example. But using the JSNI component (i.e. using native Javascript from within the Java code) is potentially very dangerous, in terms of reliable code. Third-party JavaScript frameworks can be used by creating interfaces via GWT-API-Interop (http://code.google.com/p/gwt-api-interop/).

There’s a few community projects going on where others have already created these interfaces, so it should be OK to use jQuery or PrototypeJS for example.

But using the JSNI component (i.e. using native Javascript from within the Java code) is potentially very dangerous, in terms of reliable code.

]]>