We've found this ability to override methods and subclass components
to be invaluable. You may be able to do some of this with SmartGWT, I
have not specifically looked. Coming from a Wicket background I found
GXT to be very comfortable and 'Wicketlike' in the way thats its pure
Java and abstracts
We don't want nested grids. We don't want nested html. We want a
nested composite panel with arbitrary widgets in them. Neither
framework does well there, hence the custom solution.
Anyhow, we'll be looking on our next project and seeing how we feel
about it. Extended GXT was very simple for us
Same problem that I have here:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/df013dc962cc268e/21920de1cdf1edbc?lnk=gstq=siberian#21920de1cdf1edbc
The RPC and the JS apps are in the same path space (/siteGWT) and I
get failures. Not NPE, just inability for RPC to connect
