Re: [gwt-contrib] Re: Experimental release of Elemental2

You are probably missing the flag. In this particular situation you are implementing a native JsType and that is considered a form exporting in current compiler and hence affected by the flag. I know that is surprising and it will be fixed in https://gwt-review.googlesource.com/#/c/15193/ (which

Re: [gwt-contrib] Re: Experimental release of Elemental2

I just applied elemental2 to this simple drang and FileReader showcase (https://github.com/ibaca/dndfiles-gwt/blob/master/src/main/java/dndfiles/client/DndFiles.java). Elemental2 looks good, but I think that JsInterop still a bit... unpredictable. The project compiles correctly, but the

Re: [gwt-contrib] Re: Experimental release of Elemental2

should be able to make this a little tighter: button.addEventListener("click", (evt) -> { button.parentNode.removeChild(button); alert("Button has been removed."); }); :) On Thu, Jun 30, 2016 at 4:16 AM, Julien Dramaix wrote: > I'll try to find some time next week

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

https://gwt-review.googlesource.com/15352 Tested locally by running the integration tests from my gwt-maven-plugin, which includes GWTTestCase. Notice the followup change at https://gwt-review.googlesource.com/15353: interestingly, the jdtCompilerAdapter.jar including within gwt-dev is not

Re: [gwt-contrib] Re: Experimental release of Elemental2

I'll try to find some time next week for uploading examples on my github account. A simple example could be: package elemental.sample.simple; import static elemental2.Global.alert; import static elemental2.Global.document; import com.google.gwt.core.client.EntryPoint; import elemental2.Event;

[gwt-contrib] Re: Experimental release of Elemental2

Hi, I would be nice If you could publish simple example how to start using it. Regards, Matic On Thursday, June 30, 2016 at 2:23:51 AM UTC+2, Julien Dramaix wrote: > > A new experimental version of Elemental2 using the new JsInterop > specification has been pushed on Sonatype today. > >

Re: Questions about how the GWT obfuscation process works

On Thursday, June 30, 2016 at 11:36:19 AM UTC+2, Jens wrote: > > GWT first optimizes the Java AST, then converts it into a JavaScript AST > and optimizes it as well. Once that is done the actual obfuscation is just > a simple renaming as far as I know. > Once the optimization (aka

Re: [gwt-contrib] Experimental release of Elemental2

This is brilliant. Thanks for sharing the experimental version!!! On Thu, Jun 30, 2016 at 1:23 AM 'Julien Dramaix' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > A new experimental version of Elemental2 using the new JsInterop > specification has been pushed on

Re: Questions about how the GWT obfuscation process works

GWT first optimizes the Java AST, then converts it into a JavaScript AST and optimizes it as well. Once that is done the actual obfuscation is just a simple renaming as far as I know. Its also kind of worthless doing such a compression as you have mentioned because that is exactly what GZIP

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

Oh, BTW, please file an issue: we must not release RC1 before this is fixed. +daniel On Thursday, June 30, 2016 at 10:46:00 AM UTC+2, Thomas Broyer wrote: > > Oops? Will fix asap. > > (how about excluding HTMLUnit as a whole? only keeping JDT bundled as > we're using a patched version) > > On

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

Oops? Will fix asap. (how about excluding HTMLUnit as a whole? only keeping JDT bundled as we're using a patched version) On Wednesday, June 29, 2016 at 10:12:08 PM UTC+2, Ignacio Baca Moreno-Torres wrote: > > I'm updating the old mojo plugin and one of the IT throws this stacktrace. > I'm

Questions about how the GWT obfuscation process works

I've been vaguely aware of GWT and what it does for a few years, but learning Java is still on my todo list so I haven't yet explored GWT in too much depth. While recently poking around in my browser devtools as I tried to figure out how a particular webapp worked I noticed some obfuscated