Eric Sessoms of Nub Games read my post about using GWT for other frameworks and decided to put the idea of exposing GWT functions as regular javascript functions to the test. He exposes the constructor of a widget through a static factory method.
While this is a good start, It’s not the final stop. To make the GWT suitable for integration with other frameworks, we can’t view it as an application framework but rather as a Java to Javascript compiler or as a generator of individual object types. Someone has to be in charge, and if our goal is to integrate GWT into some othe framework, control has to be in that other framework. My experimentation with the GWT seems to suggest that using it’s event handling code in the abscence of widgets may not be so simple.
While you’re over at Nub Games, have a look at some of their other posts, such as the one on using CSS with GWT.
I guess I really didn’t do a very good writup of the exporting technique, but GWT does in fact give up control. The GWT framework initializes and calls the application entry point which exports classes and methods as necessary before exiting. The page is then run by non-GWT JavaScript. I’ll make an effort to do a better job the next time I task switch back in that direction.
In the mean time, if there is any specific example anyone would like to see, reply on this comment thread and I’ll try to work it in.