On Wednesday, January 12, 2011 9:16:06 PM UTC+1, markM wrote:
>
> I think it's important for folks to understand that they're not
> writing in Java and to appreciate the times when it truly feels like
> they are because the GWT team has done such an excellent job.
+1
It smells like Java, it
I think it's important for folks to understand that they're not
writing in Java and to appreciate the times when it truly feels like
they are because the GWT team has done such an excellent job. When a
thread like this happens I call it "the book of Job" because the end
user often times doesn't kn
GWT had to do I18N the way it's done precisely because of the
constraints imposed by Javascript compilation and the choices made for
optimization, in particular the notion of "permutation" which requires
that every possible combination of browser and target language is
compiled separately.
Instead
Gwt didn't support java logging since recently, cause some limitations
on the compiler.
I agree with you on the uibinder + i18n, that could be much simpler. I
am using apt on guit to make that simpler
(http://code.google.com/p/guit/source/browse/trunk/GuitPlugin/src/guitplugin/I18nProcessor.java?r=
GWT translates your java source into javascript. That means that your GWT java isn't
"true" java, and there are things you just cannot do because at the end of the
day, it has to work in javascript. The use of many third party java libraries is
precluded by the javascript translation because th
First I wanna say that I love GWT. But I feel that GWT sometimes
reinvent the wheels or try to create new tools that we need to relearn
instead of relaying on Java & other Java's open source projects.
UiBinder and I18N. Java already has a Resource Bundle feature.
I think Google is confused about
