Hi!
Let me go over your points one by one:
John Todd wrote:Hey Federico,
UI in built in code, CSS in code, layout is in code.
Simply I lost the experience of our designer not to mention if I made one single change to the UI, I had to recompile the project.
Today you could use UIBinder and define the interface (UI, CSS, layout) in XML but you'll still have to compile it.
John Todd wrote:Hey Federico,
Unit tests aren't always supposed to run due the possible time out errors.
MVP allows for faster tests. You end up using
JUnit for (very fast) functional tests, GWTTestCase (not so fast) integration tests, and Selenium (slow) for acceptance tests. (I'd suggest
Chapter 13 in my book.)
John Todd wrote:Hey Federico,
Compilation is so slow.
You can twiddle parameters so, when in development, only ONE version of the code will get built.
John Todd wrote:
Hard to run GWT hosted mode on external container.
Sorry, didn't get this. What case are you thinking about?
John Todd wrote:Hibernate integration was a dark and painful nightmare.
I've used Hibernate, but as it is a server-side-only technique, I had no particular problems because of GWT.
John Todd wrote:Hard (at least to me) to write new components but to be fair here, it was always hard to write new components not matter which framework I use, whether it is JSF, GWT or Wicket.
I have developed my own components, which work in MVP fashion, and included them in my (also MVP) forms. It's far better if you can build up your widget out of existing ones, rather than try to do the whole job in JavaScript... and in that case you'll have to deal with browsers' quirks on your own! (I'd recommend chapters 5 and 15 in
ESSENTIAL GWT.)
John Todd wrote:What about GWT 2?
Do you suggest to give it a second chance?
Obviously I may be biased, but I'm still working with (and happy with!) GWT, and where I work, we do all the client-side development... so, yes, I'd give it a chance!