Linked by Thom Holwerda on Wed 4th May 2011 20:41 UTC, submitted by lemur2
Thread beginning with comment 471975
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: A Loose Loose situation
by StaubSaugerNZ on Fri 6th May 2011 03:41
in reply to "RE[3]: A Loose Loose situation"
@Pantheraleo:
Google Web Toolkit can produce layouts in code or declaratively using its 'UI Binder' technology. Plus, the overall layout is achieved using CSS.
Might be worth you checking out Google Web Toolkit again, since your info is out of date. Especially since GWT is evolving at a fast rate (it ought to be, the might of Google is developing it).
Edited 2011-05-06 03:42 UTC
RE[5]: A Loose Loose situation
by pantheraleo on Fri 6th May 2011 03:50
in reply to "RE[4]: A Loose Loose situation"
Might be worth you checking out Google Web Toolkit again, since your info is out of date. Especially since GWT is evolving at a fast rate (it ought to be, the might of Google is developing it).
I've looked it recently. Didn't realize you could develop UIs outside of code now.
But I stll have other problems with it. It's component set is very primitive for example. Granted, there are third party add-ons to solve that, such as SmartGWT.
The other problem I have with it is that for very large projects, the compile / test cycle becomes somewhat unmanageable.





Member since:
2007-03-07
That's really an issue of personal taste. A lot of people don't like marking up their UI in code. And if you have a web design team that is used to using tools like Dreamweaver, you can completely forget about GWT.