Wow! It's great to see all that progress being made on GWT 3. That's a lot
more backwards compatibility than I was expecting.
Still, it would be nice to have J2CL released separately as soon as it is
ready to do so because
1. Based on past experience, it will take 1-2 years or more before
Well, ok. Thanks.
Just in terms of general feedback on Elemental2:
1. I'm not sure whether the conversion of JavaScript properties to Java
fields is the best choice. Sure, it "feels" more like the original
JavaScript, but a) it's inconsistent with Java semantics, b) I'd be afraid
that a Java
It's a little unfortunate that Elemental is being developed privately since
it's the one part of GWT that's self-contained enough that I am able and
willing to contribute to it. But is it possible to get an early,
unofficial, unsupported code drop of the current Elemental code generator?
I'm a
Wow, that's great! I noticed yesterday that Firefox finally added support
for stuff like clientX and pageX too. For years, they refused to implement
stuff like that.
Oh, mighty Apple web developers! Your absolute refusal to test your code on
anything except Safari has finally felled even the
It would also be nice if Elemental 2 also has an easy way to selectively
knock out certain fields/methods in the code generator. I don't know how
many times I'll be using code completion and accidentally end up writing
something like
div.setInnerText("click me")
because innerText is
Is it possible to get some hints about what's cooking for Elemental 2?
Is the code generator still going to be Python or is it going to be
rewritten in Java? I found modifying the Python code generator when I
wanted to change Elemental 1 to be annoying.
Is the output going to be a direct
