GWT always sounds interesting, but I am underwhelmed by the application gallery. Every app looks like a draft version of gmail, google maps or google wave. Any links to impressive interfaces (non google-built)?
I'll also plug our GWT-based product, DotSpots. I'm dogfooding it on my blog at http://grack.com - just select one of the paragraphs or click one of the blue dots to see the UI. It's an example of a non-traditional GWT application: we're running our own GWT code inside of a foreign website. Our website is more of classic GWT application, but we compile both of those targets (as well as Chrome and Firefox extensions) from subsets of the same codebase.
The download package comes with a bundled sample database, so you can take it for a spin too. Feedback welcome.
- I was totally confused how to launch this - I couldn't discern any benefit of this over phpPgAdmin minus the nicely done interface - I couldn't discern any benefit of this over Aqua Data Studio, NaviCat, et al. sans pricing.
I'm really curious why you chose to do this as a web app. If the benefit is to give "managers" and others access to the database to run reporting, where is the graphing, pivot table, etc support? If it's to give other developers access, your desktop counterparts (specifically Aqua Data Studio) provide tools you are lacking (code completion, diagramming). Granted there is a sizable price difference, which could be a selling point, but again phpPgAdmin does all that you do and is free and extensible because it's OSS.
Ditto jawngee suggestion about creating "end user" pages with standard reports (e.g. graphs using http://www.simile-widgets.org/timeplot/). Allow me to let users view them without logging in. That is what cmd line can't do.
The product is still a few features away from being ready for the public launch, the value proposition should be more apparent when we get there.
If you don't want to modify the widget appearances or behaviors, Ext-GWT is nice.
If you aren't building a large web-app, Ext-GWT is the way to go.
But if you're one of them people who prefer to do TDD, or unit-test etc, avoid Ext-GWT at all cost.
If you want to personalize your app, avoid Ext-GWT at all cost.
If you want a solid (library) Java code, avoid Ext-GWT at all cost.
I've been using their code since MyGWT 0.4 and right now we're trying to get rid of it so bad.