That depends on your requirements and your confidence in the compiler technology to generate correct code, always. In the end, you always have to test both the clent side and the server side, and in most cases, it doesn't really matter what language you used to build either one, so long as your infrastructure allows for effective testing. If your team has very strong client-side programmers, you probably don't require GWT. If you have a bunch of people who don't know interfaces that well, or only now desktop-style interfaces, then GWT is a nice solution, since it completely abstracts the html/javascript layer (or so I am told). To be honest, it has some real attraction for many Tapestry developers, I'd think, since we, too, create much of our interface programmatically, and the rewind cycle imposes some significant limitations on what things can be done (easily) in a responsive, client-side manner. Since GWT does entirely away with the concept of a 'page' and handles each request for dynamically generated content in isolation from the next, it doesn't suffer from the same issues. I'm sure it has its own weaknesses (not least being its closed source implementation), but different developers will choose a platform based on their own requirements.
--sam On 6/5/06, Peter Dawn <[EMAIL PROTECTED]> wrote:
hi all, i tried GWT today and i dont think its that attractive platform or technology. we have to write a whole bunch of UI code in pure java based on the GWT API to come up with a AJAX enabled web app (which is pure html and javascript). this means the the developer would need to go through the entire API, learn and understand it and then write java code based on it, to get something in HTML in the end. wouldnt it be easier to just write a front end in html or js and then write the corresponding code which processes that info (tapestry), instead of the code generating that page in html. any thoughts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
