Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Manolo reviewed https://gwt-review.googlesource.com/#/c/14430/, we did the requested changes. Would be great if it gets merged before GWT 2.8 is released. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Another one is about Event.BUTTON_LEFT processing. This seems to be important since to should be spec-ed somehow, it is ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it,

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

One of above is a licensing issue (a missing one). Is it important ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

+1 for https://gwt-review.googlesource.com/#/c/14430/ It's a big one! I opened a GitHub ticket for it: https://github.com/gwtproject/gwt/issues/9427 Thanks On Monday, September 19, 2016 at 7:45:43 PM UTC+10, Jakob Jarosch wrote: > > Hi, > even it is a bit late, but we where a bit surprised

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Hi, even it is a bit late, but we where a bit surprised that a merge request, opened half a year ago, was still not merged. The bug forces us to maintain our own GWT. https://gwt-review.googlesource.com/#/c/14430/ And then some not so important things (but its really sad, that no one cares

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Makes sense! So better to have a "nostrict" option for the special cases Thanks Le sam. 10 sept. 2016 14:57, Jens a écrit : > > Thank you I will try that -strict option. >> >> My suggestion is that exported @JsType (when the -generateJsExport option >> is turned on)

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

> Thank you I will try that -strict option. > > My suggestion is that exported @JsType (when the -generateJsExport option > is turned on) should be considered as entrypoints and generate compilation > errors, what do you think ? > I think that -strict should be the default everywhere. I don't

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Thank you I will try that -strict option. My suggestion is that exported @JsType (when the -generateJsExport option is turned on) should be considered as entrypoints and generate compilation errors, what do you think ? Le vendredi 9 septembre 2016 17:42:16 UTC+2, Roberto Lublinerman a écrit :

[gwt-contrib] Re: Last call for 2.8.0-RC3

As we've delayed the release a bit, let's add another documentation fix: https://gwt-review.googlesource.com/16860 On Thursday, September 8, 2016 at 4:27:36 PM UTC+2, Daniel Kurka wrote: > > Hi all, > > I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with > any outstanding

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Arnaud, have you tried using -strict? GWT ignores compilation units with errors if they are not explicitly reachable from the entry point. I assume your Toto class is only referenced from JS. So if this class has any compile error (like missing references) then GWT does not see the class, much

[gwt-contrib] Re: Last call for 2.8.0-RC3

I have one problem which is recurring, related to JsInterop. Sometimes the JsInterop JS stub is not generated because of (seemingly) an internal error in SuperDevMode (and GWTC it seems), but nothing is logged, so it's difficult to diagnose. For example, in an application (which does not

[gwt-contrib] Re: Last call for 2.8.0-RC3

This is not a fix but a request for enhancement (unless I misremember). This is not "officially" supported, but it happens to work if you suppress validation for those methods. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

This is a last call for patches, anything that is not in until tomorrow (and is not important enough to hold the release) will not get in. Is there already a patch in review for this? On Thu, Sep 8, 2016 at 5:40 PM Kay-Uwe Janssen wrote: > Is there a plan to fix the

[gwt-contrib] Re: Last call for 2.8.0-RC3

Is there a plan to fix the ValdiationTool (issue mentioned here: https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/lue7vRkkxU8 ) for default and static methods in proxy interfaces? or is it already fixed? if one it should be documented as known issue with the

[gwt-contrib] Re: Last call for 2.8.0-RC3

Hi Daniel, On Thursday, September 8, 2016 at 4:27:36 PM UTC+2, Daniel Kurka wrote: > > Hi all, > > I will be cutting rc3 tomorrow 1pm CEST, >  > please respond to this email with any outstanding reviews that you want to > see included. > https://gwt-review.googlesource.com/16760 and